International sloooow

[WAangelo]

Hi Guys,

It appears that the reason for the slow connectivity at the moment is because of a link thats down since yesterday.

Please see the WA status page for updates on the status - http://www.webafrica.co.za/alerts/


Thank you.

 

[Globetrotter]

Hi Guys,

It appears that the reason for the slow connectivity at the moment is because of a link thats down since yesterday.

Please see the WA status page for updates on the status - http://www.webafrica.co.za/alerts/

I also receive the SAIX noticeboard emails, here's the last update on that link that's down:

Notice Ref : NN0003533
Failure Type : Fault Condition
Status : New
Problem Description : Link - Link down between Rosebank LIR to Hongkong
Impact : Customers may experience slow international connectivity
Time Down : 2009-09-02 15:11
Sites : Rosebank
Affected : Leased Line users
Cause : Unkown
ETTR : 1 Hour
Progress : Faul reported to Telkom Malaysia,Busy investigating.

Only leased line users are affected by this outage, according to the message. The alert on the WA page does not mention this. Normally if ADSL users are affected, it's specifically mentioned in the full alert. According to SAIX, ADSL is fine... ? You should post the full alerts on WA's alert forum, not partial messages, to avoid confusion.

 

[boerseun]

Not just international, all my sites are farking slow!

 

[SuperAntMD]

WA and telkom claiming no issues. "have you tried turning the router on and off again?"

give me a break...

 

[Mahado]

slooooooooow going, it took about 30 seconds just to load up the WA home page so i could check on the alerts, normally it takes about 3 - 5s gah !!!!!!!

 

[Talen3]

Have a look at this post web Africa users and put your problems there. I did a test with ping plotter and there is a problem with a server well im getting 100% packet loss. Maybe telkom doing something?

http://forums.webafrica.co.za/showthread.php?p=12691&posted=1#post12691

 

[gryster]

I have also been looking into this problem in-depth (not only for playing EVE but also other european based MMO's).

The problem is only currently with SAIX based accounts. This is the problem:
========================================================
C:\Users\Home>ping -t -l 1024 94.75.194.4

Pinging 94.75.194.4 with 1024 bytes of data:
Reply from 94.75.194.4: bytes=1024 time=538ms TTL=114
Reply from 94.75.194.4: bytes=1024 time=540ms TTL=114
Reply from 94.75.194.4: bytes=1024 time=540ms TTL=114
Reply from 94.75.194.4: bytes=1024 time=544ms TTL=114
Reply from 94.75.194.4: bytes=1024 time=534ms TTL=114
Request timed out.
Reply from 94.75.194.4: bytes=1024 time=543ms TTL=114
Reply from 94.75.194.4: bytes=1024 time=544ms TTL=114
Reply from 94.75.194.4: bytes=1024 time=537ms TTL=114
Reply from 94.75.194.4: bytes=1024 time=533ms TTL=114
Reply from 94.75.194.4: bytes=1024 time=537ms TTL=114
Request timed out.
Reply from 94.75.194.4: bytes=1024 time=542ms TTL=114
Reply from 94.75.194.4: bytes=1024 time=543ms TTL=114
Reply from 94.75.194.4: bytes=1024 time=537ms TTL=114
Reply from 94.75.194.4: bytes=1024 time=537ms TTL=114
Reply from 94.75.194.4: bytes=1024 time=537ms TTL=114
Reply from 94.75.194.4: bytes=1024 time=539ms TTL=114
Reply from 94.75.194.4: bytes=1024 time=541ms TTL=114
Reply from 94.75.194.4: bytes=1024 time=537ms TTL=114
Reply from 94.75.194.4: bytes=1024 time=537ms TTL=114
...
Reply from 94.75.194.4: bytes=1024 time=538ms TTL=114
Request timed out.
Reply from 94.75.194.4: bytes=1024 time=535ms TTL=114
Reply from 94.75.194.4: bytes=1024 time=537ms TTL=114
Reply from 94.75.194.4: bytes=1024 time=533ms TTL=114
Reply from 94.75.194.4: bytes=1024 time=534ms TTL=114
Reply from 94.75.194.4: bytes=1024 time=544ms TTL=114
Reply from 94.75.194.4: bytes=1024 time=542ms TTL=114
Reply from 94.75.194.4: bytes=1024 time=534ms TTL=114
Reply from 94.75.194.4: bytes=1024 time=532ms TTL=114
Reply from 94.75.194.4: bytes=1024 time=537ms TTL=114
Reply from 94.75.194.4: bytes=1024 time=540ms TTL=114
Reply from 94.75.194.4: bytes=1024 time=540ms TTL=114
Reply from 94.75.194.4: bytes=1024 time=541ms TTL=114
Reply from 94.75.194.4: bytes=1024 time=543ms TTL=114
Reply from 94.75.194.4: bytes=1024 time=535ms TTL=114
Request timed out.
Reply from 94.75.194.4: bytes=1024 time=530ms TTL=114
Reply from 94.75.194.4: bytes=1024 time=541ms TTL=114
Reply from 94.75.194.4: bytes=1024 time=539ms TTL=114
Reply from 94.75.194.4: bytes=1024 time=535ms TTL=114
...
Reply from 94.75.194.4: bytes=1024 time=539ms TTL=114
Reply from 94.75.194.4: bytes=1024 time=541ms TTL=114
Request timed out.
Reply from 94.75.194.4: bytes=1024 time=529ms TTL=114
Reply from 94.75.194.4: bytes=1024 time=537ms TTL=114
Reply from 94.75.194.4: bytes=1024 time=539ms TTL=114
Reply from 94.75.194.4: bytes=1024 time=469ms TTL=114
Reply from 94.75.194.4: bytes=1024 time=467ms TTL=114
Reply from 94.75.194.4: bytes=1024 time=472ms TTL=114
Reply from 94.75.194.4: bytes=1024 time=472ms TTL=114
Reply from 94.75.194.4: bytes=1024 time=464ms TTL=114
Reply from 94.75.194.4: bytes=1024 time=474ms TTL=114
Reply from 94.75.194.4: bytes=1024 time=460ms TTL=114
Reply from 94.75.194.4: bytes=1024 time=470ms TTL=114
Reply from 94.75.194.4: bytes=1024 time=472ms TTL=114
Reply from 94.75.194.4: bytes=1024 time=473ms TTL=114
Reply from 94.75.194.4: bytes=1024 time=459ms TTL=114
Reply from 94.75.194.4: bytes=1024 time=461ms TTL=114
Reply from 94.75.194.4: bytes=1024 time=463ms TTL=114
Reply from 94.75.194.4: bytes=1024 time=469ms TTL=114
Reply from 94.75.194.4: bytes=1024 time=464ms TTL=114
Reply from 94.75.194.4: bytes=1024 time=461ms TTL=114
....
Reply from 94.75.194.4: bytes=1024 time=467ms TTL=114
Reply from 94.75.194.4: bytes=1024 time=478ms TTL=114
Reply from 94.75.194.4: bytes=1024 time=468ms TTL=114
Reply from 94.75.194.4: bytes=1024 time=466ms TTL=114
Reply from 94.75.194.4: bytes=1024 time=468ms TTL=114
Reply from 94.75.194.4: bytes=1024 time=464ms TTL=114
Reply from 94.75.194.4: bytes=1024 time=465ms TTL=114
Reply from 94.75.194.4: bytes=1024 time=469ms TTL=114
Reply from 94.75.194.4: bytes=1024 time=472ms TTL=114
Reply from 94.75.194.4: bytes=1024 time=464ms TTL=114
Reply from 94.75.194.4: bytes=1024 time=466ms TTL=114
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 94.75.194.4: bytes=1024 time=539ms TTL=114
Reply from 94.75.194.4: bytes=1024 time=540ms TTL=114
Reply from 94.75.194.4: bytes=1024 time=543ms TTL=114
Reply from 94.75.194.4: bytes=1024 time=543ms TTL=114
Reply from 94.75.194.4: bytes=1024 time=534ms TTL=114
Reply from 94.75.194.4: bytes=1024 time=534ms TTL=114

Ping statistics for 94.75.194.4:
Packets: Sent = 146, Received = 136, Lost = 10 (6% loss),
Approximate round trip times in milli-seconds:
Minimum = 459ms, Maximum = 548ms, Average = 513ms
Control-C
^C
C:\Users\Home>
========================================================
As you can see 6% packet loss. Upon doing a traceroute while its reachable vs while its timing out the following is visible:

========================================================
C:\Users\Home>tracert 94.75.194.4

Tracing route to 94.75.194.4 over a maximum of 30 hops

1 26 ms 18 ms 19 ms dsl-243-192-01.telkomadsl.co.za [41.243.192.1]
2 43 ms 49 ms 39 ms wblv-ip-lir-1-gig-4-0-0.telkom-ipnet.co.za [196.43.8.190]
3 349 ms 350 ms 349 ms ash-ip-dir-equinix-pos-4-0.telkom-ipnet.co.za [196.43.18.30]
4 481 ms 424 ms 400 ms so-3-0-1.ar1.DCA3.gblx.net [208.49.224.161]
5 454 ms 452 ms 448 ms 64.213.76.150
6 442 ms 454 ms 448 ms po100.sr1.evo.leaseweb.net [85.17.100.226]
7 452 ms 461 ms 450 ms 85.17.163.226
8 443 ms 451 ms 497 ms 94.75.194.4

Trace complete.

C:\Users\Home>tracert 94.75.194.4

Tracing route to 94.75.194.4 over a maximum of 30 hops

1 24 ms 29 ms 30 ms dsl-243-192-01.telkomadsl.co.za [41.243.192.1]
2 wblv-ip-lir-1-gig-4-0-0.telkom-ipnet.co.za [196.43.8.190] reports: Destina
tion host unreachable.

Trace complete.
======================================================

As is clear above [wblv-ip-lir-1-gig-4-0-0.telkom-ipnet.co.za [196.43.8.190]] cannot reach its outbound route [ash-ip-dir-equinix-pos-4-0.telkom-ipnet.co.za [196.43.18.30]].

However this problem is intermittent, hence the packets go through fine sometimes and sometimes it times out. (When its timing out that is when the second hop cannot reach its outbound)

I've logged this problem through my ISP MWEB but in the meantime I've purchased a Prepaid IS account through Axxess and I'm using that to play games while I pray this gets resolved by some miracle or freak accident of nature because SAIX sure as HELL arnt competant enough to fix this issue by doing anything constructive that's for sure. Viva BEE, Viva! Let's all get flushed down the banana republic toilet asap.

Thank you.

 

[Talen3]

Do you have to go threw axxess ?

 

[thedoc!]

My lantency and packet loss is equally bad on an IS fiber account with Afrihost - Absolutely shocking...latency is up and down like a working girl's knickers on a Friday night on a busy street corner!!

 

[thedoc!]

/\/\ Oh and before I get flamed for it - I know nothing about the knicker movements of working girls!!

 

[gryster]

Latency and packet loss are not the same thing and once you understand the difference, you'll realise why you can "live" with latency, but packet loss is a very serious network failure that needs to be addressed asap.

And no you dont have to go through Axxess, you may choose any "isp" that resells IS ISP bandwidth.

 

[thedoc!]

Latency and packet loss are not the same thing and once you understand the difference, you'll realise why you can "live" with latency, but packet loss is a very serious network failure that needs to be addressed asap.

You dont say :erm:

Voice suffers when the latency changes suddenly (jitter) equally bad as when there is packet loss. But yes you can live with latency to a point - but packet loss is a big no no.

 

[defsoul]

Hi,
I've been having the same problem with IS fibre for almost 2 weeks. IS even swapped my billion router but the problem still persists.IS or telkom both can't give me any explanation.They both claim everything is fine. I've run out of ideas and don't know who to call anymore. Is anyone still experiencing problems with IS fibre?