LATENCY!!!

ajules said:
I logged a fault both on-line and telephonically.
Received a call from a Telkom agent this morning telling me rather proudly that my fault had been resolved.....they decided to downgrade me from 8mb to 4mb.
Gee thanks!!
Click to expand...

Eish that sucks. This is just typical Telkom work-avoidance strategy. I've had this happen too - you dare mention the words "line fault" and they instantly drop your speed and pretend everything is fixed, even though your line is syncing fine and stable. I live less than 1.5km from the exchange and my router has shown attainable rates of up to 22Mbps on ADSL2+. They dropped me from 4 to 3 Mbps and said it was fixed. I demanded to be put back on 4Mbps, and guess what, it made the square root of ****all difference. This was during the WC so just about the time they were doing upgrades. After the upgrades everything went to ****, as we all know. I'm now on 7Mbps. What I also don't understand is why the modulation randomly changes between G.Dmt and ADSL2+, with attainable rates of >10Mbps and >20Mbps respectively - yet they could only upgrade me to 7Mbps.
 
Well I just got off the phone with them ... they say the fault has been fixed.

Pinging games.saix.net [196.43.22.222] with 32 bytes of data:
Reply from 196.43.22.222: bytes=32 time=156ms TTL=243
Reply from 196.43.22.222: bytes=32 time=167ms TTL=243
Reply from 196.43.22.222: bytes=32 time=179ms TTL=243
Reply from 196.43.22.222: bytes=32 time=189ms TTL=243

Ping statistics for 196.43.22.222:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 156ms, Maximum = 189ms, Average = 172ms

:(
 
Surv0 said:
Im very annoyed with the situation atm, apologies for my little rant directed at you but this thread has been filled with useless additions from people who arent effected by this issue. Sometimes i struggle in curbing my outbursts :p

But these are the facts at hand. The southern suburbs has one of the highest adsl access per region in the country. We also have a number of datacentres which rely on the local exchanges, WA, Datapro etc.. The Wynberg, Claremont, kenilworth and rondebosch areas are quite populated with over 10 different private and public schools. We have about 7 just on one road, its crazy. Anyway, alot of business's here rely heavily on low latency connectivity, something weve come to enjoy and expect through previous experience. Its also been one of the most stable ADSL areas in the country, ive been paying telkom for 6 years and ive never had a problem really, up until recently. And its not just me, its everyone. Telkom spent a fortune prepping the exchanges for this upgrade, without thinking they didnt look at other areas for possible congestion points. Techies even confirmed verbally to me that this upgrade shouldnt have happened, and management pushed it through regardless. That being said, telkom is going to have alot of heat under their b@lls to get this resolved. I just the big players, MWEB, WA etc push hard to sort this out, afterall they are taking flack from their clients about this issue.

Anyway - enough is enough... time to fix the issue.
Click to expand...

+10

I've also lived in the Southern Subs for the last few years and the ADSL service has been exceptionally stable/reliable in comparison to other areas I've lived in. Like you said, ever since the WC/Upgrades everything has gone to ****. How Telkom don't realise this by themselves is beyond me. Online games are impossible with pings between 200-300 to local servers.
 
Has been reliable

NB: Last week friday pings were low in the evening and the day and then Sunday/Monday it went back to how it was.
 
zombie said:
Eish that sucks. This is just typical Telkom work-avoidance strategy. I've had this happen too - you dare mention the words "line fault" and they instantly drop your speed and pretend everything is fixed, even though your line is syncing fine and stable. I live less than 1.5km from the exchange and my router has shown attainable rates of up to 22Mbps on ADSL2+. They dropped me from 4 to 3 Mbps and said it was fixed. I demanded to be put back on 4Mbps, and guess what, it made the square root of ****all difference. This was during the WC so just about the time they were doing upgrades. After the upgrades everything went to ****, as we all know. I'm now on 7Mbps. What I also don't understand is why the modulation randomly changes between G.Dmt and ADSL2+, with attainable rates of >10Mbps and >20Mbps respectively - yet they could only upgrade me to 7Mbps.
Click to expand...

I was pushed to 10 and lost all connectivity to the ESR - after about a week without adsl access, a techie finally came to confirm the modulation was set correctly, but i couldnt get any connectivity past 5mb. I synch at 10mb perfectly... SNR and ATT are all hundreds, except couldnt make a connection. Eventually they had to bring me to 5 just to get a connection working.. weird issue, but thats what ive been on since.
 
Hey guys,

I'll be posting an official update on the latency and speed issues here shortly.
 
Surv0 said:
My pings are way down:

Pinging www.saix.net [196.25.1.200] with 32 bytes of data:
Reply from 196.25.1.200: bytes=32 time=11ms TTL=250
Reply from 196.25.1.200: bytes=32 time=9ms TTL=250
Reply from 196.25.1.200: bytes=32 time=8ms TTL=250
Reply from 196.25.1.200: bytes=32 time=8ms TTL=250
Reply from 196.25.1.200: bytes=32 time=13ms TTL=250
Reply from 196.25.1.200: bytes=32 time=14ms TTL=250
Reply from 196.25.1.200: bytes=32 time=11ms TTL=250
Reply from 196.25.1.200: bytes=32 time=7ms TTL=250
Reply from 196.25.1.200: bytes=32 time=9ms TTL=250
Reply from 196.25.1.200: bytes=32 time=10ms TTL=250
Reply from 196.25.1.200: bytes=32 time=10ms TTL=250
Reply from 196.25.1.200: bytes=32 time=13ms TTL=250
Reply from 196.25.1.200: bytes=32 time=10ms TTL=250
Reply from 196.25.1.200: bytes=32 time=14ms TTL=250

Ping statistics for 196.25.1.200:
Packets: Sent = 14, Received = 14, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 7ms, Maximum = 14ms, Average = 10ms
Click to expand...

LOL I noticed in my log that there was a huge dip at that time. That was probably due to everyone leaving work early on a Friday then arriving home and cranking it up again.
 
@WAJeff I'm glad to see you guys are running with this as well - please feel free to drop me a PM if you'd like to swap notes - we're all on the same side on this one :)
 
Tracing route to www.saix.net [196.25.1.200]
over a maximum of 30 hops:

1 8 ms 8 ms 8 ms dsl-144-160-01.telkomadsl.co.za [41.144.160.1]
2 9 ms 9 ms 9 ms wblv-ip-essr-1-atm-2-0-0-2.telkom-ipnet.co.za [196.43.11.30]
3 34 ms 34 ms 32 ms wblv-ip-www-1.saix.net [196.25.1.200]

Trace complete.

Pinging www.saix.net [196.25.1.200] with 32 bytes of data:
Reply from 196.25.1.200: bytes=32 time=42ms TTL=251
Reply from 196.25.1.200: bytes=32 time=32ms TTL=251
Reply from 196.25.1.200: bytes=32 time=19ms TTL=251
Reply from 196.25.1.200: bytes=32 time=15ms TTL=251
Reply from 196.25.1.200: bytes=32 time=10ms TTL=251
Reply from 196.25.1.200: bytes=32 time=11ms TTL=251
Reply from 196.25.1.200: bytes=32 time=13ms TTL=251
Reply from 196.25.1.200: bytes=32 time=10ms TTL=251
Reply from 196.25.1.200: bytes=32 time=10ms TTL=251
Reply from 196.25.1.200: bytes=32 time=19ms TTL=251

Ping statistics for 196.25.1.200:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 10ms, Maximum = 42ms, Average = 18ms

=====================

Tracing route to www.telkom.co.za [196.43.22.222]
over a maximum of 30 hops:

1 8 ms 8 ms 8 ms dsl-144-160-01.telkomadsl.co.za [41.144.160.1]
2 78 ms 79 ms 76 ms rrba-ip-esr-1-pos-8-0-0.telkom-ipnet.co.za [196.43.8.146]
3 30 ms 31 ms 31 ms rrba-ip-bssr-1-ge-2-48.telkom-ipnet.co.za [196.43.23.6]
4 33 ms 34 ms 33 ms nbsc-ip-bssr-1-atm-5-0-0-1.telkom-ipnet.co.za [196.43.23.30]
5 117 ms 110 ms 104 ms nbsc-ip-rcache-1-vif2.telkom-ipnet.co.za [196.43.22.222]

Trace complete.

Pinging telkom.co.za [196.43.22.222] with 32 bytes of data:
Reply from 196.43.22.222: bytes=32 time=33ms TTL=250
Reply from 196.43.22.222: bytes=32 time=38ms TTL=250
Reply from 196.43.22.222: bytes=32 time=37ms TTL=250
Reply from 196.43.22.222: bytes=32 time=39ms TTL=250
Reply from 196.43.22.222: bytes=32 time=35ms TTL=250
Reply from 196.43.22.222: bytes=32 time=35ms TTL=250
Reply from 196.43.22.222: bytes=32 time=38ms TTL=250
Reply from 196.43.22.222: bytes=32 time=37ms TTL=250
Reply from 196.43.22.222: bytes=32 time=41ms TTL=250
Reply from 196.43.22.222: bytes=32 time=42ms TTL=250
Reply from 196.43.22.222: bytes=32 time=37ms TTL=250
Reply from 196.43.22.222: bytes=32 time=36ms TTL=250

Ping statistics for 196.43.22.222:
Packets: Sent = 12, Received = 12, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 33ms, Maximum = 42ms, Average = 37ms

=======

Something is going on....
 
Last edited:
is it just me... or does it seem like its stabalising? *touch wood*

Ping statistics for 196.43.22.222:
Packets: Sent = 90, Received = 90, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 33ms, Maximum = 64ms, Average = 38ms
 
Gordon_R said:
Keeping watching the CINX traffic graph, it starts to dip after 4pm on Fridays:
http://stats.cinx.net.za/
Latency has improved temporarily, but nothing has been fixed yet IMO.
Click to expand...

I know optimism is the last thing we should be feeling but sheesh.. these stats havent looked like this in ages...

Pinging telkom.co.za [196.43.22.222] with 32 bytes of data:
Reply from 196.43.22.222: bytes=32 time=34ms TTL=250
Reply from 196.43.22.222: bytes=32 time=36ms TTL=250
Reply from 196.43.22.222: bytes=32 time=33ms TTL=250
Reply from 196.43.22.222: bytes=32 time=34ms TTL=250
Reply from 196.43.22.222: bytes=32 time=67ms TTL=250
Reply from 196.43.22.222: bytes=32 time=33ms TTL=250
Reply from 196.43.22.222: bytes=32 time=33ms TTL=250
Reply from 196.43.22.222: bytes=32 time=35ms TTL=250
Reply from 196.43.22.222: bytes=32 time=34ms TTL=250
Reply from 196.43.22.222: bytes=32 time=33ms TTL=250
Reply from 196.43.22.222: bytes=32 time=34ms TTL=250
Reply from 196.43.22.222: bytes=32 time=35ms TTL=250
Reply from 196.43.22.222: bytes=32 time=33ms TTL=250
Reply from 196.43.22.222: bytes=32 time=34ms TTL=250
Reply from 196.43.22.222: bytes=32 time=32ms TTL=250
Reply from 196.43.22.222: bytes=32 time=34ms TTL=250
Reply from 196.43.22.222: bytes=32 time=33ms TTL=250
Reply from 196.43.22.222: bytes=32 time=34ms TTL=250
Reply from 196.43.22.222: bytes=32 time=34ms TTL=250
Reply from 196.43.22.222: bytes=32 time=40ms TTL=250
Reply from 196.43.22.222: bytes=32 time=34ms TTL=250

Ping statistics for 196.43.22.222:
Packets: Sent = 21, Received = 21, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 32ms, Maximum = 67ms, Average = 35ms
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X