Still having Bad Latency

moggie said:
Once an exchange fault is recorded the process is accelerated as it reflects very poorly on the maintenance team and impacts their performance assessment. They cannot sweep it under the mat (like some guys that close personal refs). They are most probably waiting for a maintenance spare to arrive. Normally they have hot-pluggable spares on site, so I can imagine that it is a major component that they have to order from Boksburg store...
Click to expand...

Explains why they consistently report everything as a line fault.
 
Merenwenrago said:
seems its bad again today not as bad latency but still double normal latency to telkom.co.za

Axxess:

Tracing route to www.telkom.co.za [196.43.22.222]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms Billion.400G [10.0.0.2]

2 8 ms 8 ms 7 ms 196-215-42-129.dynamic.isadsl.co.za [196.215.42.129]

3 58 ms 57 ms 57 ms cdsl1-rba-vl2253.ip.isnet.net [196.38.73.181]

4 39 ms 38 ms 39 ms cdsl1-rba-vl150.ip.isnet.net [196.38.73.17]

5 58 ms 58 ms 57 ms core5a-rba-gi0-0-0.ip.isnet.net [196.26.0.42]

6 104 ms 58 ms 59 ms 168.209.1.170

7 39 ms 39 ms 39 ms rrba-ip-spe-2-wan.telkom-ipnet.co.za [196.25.127.181]

8 58 ms 57 ms 58 ms 196.43.25.137

9 58 ms 58 ms 58 ms rrba-ip-esr-1-ge-6-0-0.telkom-ipnet.co.za [196.43.11.166]

10 58 ms 58 ms 58 ms rrba-ip-bssr-1-ge-2-48.telkom-ipnet.co.za [196.43.23.6]

11 44 ms 41 ms 42 ms nbsc-ip-bssr-1-atm-5-0-0-1.telkom-ipnet.co.za [196.43.23.30]

12 42 ms 42 ms 41 ms nbsc-ip-rcache-1-vif2.telkom-ipnet.co.za [196.43.22.222]
Trace complete.


Telkom:

Tracing route to www.telkom.co.za [196.43.22.222]
over a maximum of 30 hops:
1 8 ms 7 ms 7 ms dsl-144-118-01.telkomadsl.co.za [41.144.118.1]

2 57 ms 57 ms 57 ms rrba-ip-esr-1-ge-6-0-0.telkom-ipnet.co.za [196.43.11.166]

3 39 ms 39 ms 39 ms rrba-ip-bssr-1-ge-2-48.telkom-ipnet.co.za [196.43.23.6]

4 41 ms 41 ms 43 ms nbsc-ip-bssr-1-atm-5-0-0-1.telkom-ipnet.co.za [196.43.23.30]

5 42 ms 42 ms 42 ms nbsc-ip-rcache-1-vif2.telkom-ipnet.co.za [196.43.22.222]
Trace complete.
Click to expand...

Tracing route to www.telkomsa.net [196.25.211.40]
over a maximum of 30 hops:

1 462 ms 420 ms 421 ms 41-133-112-1.dsl.mweb.co.za [41.133.112.1]
2 483 ms 499 ms 483 ms tengig-0-0-0-101.vic-ipc-1.mweb.co.za [196.22.16
9.134]
3 421 ms 436 ms 483 ms vl-92.vic-hscore-1.mweb.co.za [196.22.189.2]
4 515 ms 514 ms 499 ms tengig-0-0-0-0-11.vic-up-1.mweb.co.za [196.22.16
9.225]
5 499 ms 467 ms 499 ms rrba-ip-hsll-1-wan.telkom-ipnet.co.za [196.25.8.
249]
6 421 ms 436 ms 452 ms nbsc-ip-er-1-pos-8-0-0.telkom-ipnet.co.za [196.4
3.25.58]
7 358 ms 358 ms 358 ms 196.25.181.54
8 436 ms 468 ms 483 ms 196.25.211.40

Trace complete.

--
We should have a competition to see who has the highest pings.
 
Last edited:
ye theres something wrong with dslam/exchange they probably use the congestion card

also try ping www.telkom.co.za -t

i get timeouts and spikes sometimes and its not normal on both accounts also :P
 
Last edited:
I have had very bad latency for a week now . Telkom says that my line is fine and even said they made a new port or something. Mweb told me to lower my MTU rate. that did nothing. I did a manual reset of router, i used flushdns. and so on. Both the techs at Telkon and Mweb are saying that now my router is at fault. I have replaced utp cable on the one pc. the other pc the cable is brand new. I use dsl for games and steam updates. But recently all that I can do is read the forums. Because the latency rates dont allow for suitable gaming,
tracert www.telkom.co.za and tracert www.mtv.com give me equal results = yes i get same averages for local and international. Occassionally like for 1 hour i get cool latency.I have tried an axxess 1 GB account and still same problem. I am currently using mweb 384mb uncapped.

Can someone tell me if its possible that the router can be blocking packets or are the providers talking rubbish, I think they are talking rubbish,.
 
Changing the MTU won't affect your ping packets at all, since they're usually only 32 bytes. MTU only affects packets close to the size of the MTU (which is a default of 1492 for PPPoE on ADSL routers).

Post your line attenuation, noise margins and synchronization rates < these can be found on the router's web interface of course. If your line attenuation is lower than 50dB (which is actually quite high, but still acceptable for 4Mbps connections) and your noise margin is higher than 10dB, then you shouldn't have any issues with your router.
If the latency to the first hop after your router is already 300ms+, then there is definitely something wrong with the ADSL line, DSLAM or possibly your router. If your latencies are still above 100ms even after 00:00, then its probably not due to an oversubscribed DSLAM I suppose.

You could try to change the modulation to just G.Dmt or ADSL2+. If that doesn't improve anything, borrow someone else's router if you can, before just going out and buying another one that might not even solve your problem.

Routers can block packets, but its definitely not the default action on the routers' firewalls to block outgoing traffic. The routers usually do block incoming connections of course, otherwise you'll be vulnerable to hackers from the Internet.
 
HI

Just for interest sake, I Don't think your the only person with the problem, I live in Richards bay, and my latency has doubled since Thursday night for no apparent reason. I Spoke to a number of guys in Durban and Uvongo area and they complain of teh same thing, have a ping of 40 standing at 75+, although its stable it does not offer me satisfaction when gaming. IM gonna take a stab in the dark here, but could it be like the whole coast line of kzn with this issue ;D
 
seems my latency is normal again with slight spikes (timeouts are gone probably was everyone downloading at end of month) still wondering what causes the spikes
 
Hmm. Not sure about any of you. But seems to be back to normal now. Getting average 36 ms for telkomsa.net ping Which is wonderful for me. Hope it's all good for you guys ^^
 
Pinging www.telkomsa.net [196.25.211.40] with 32 bytes of data:

Reply from 196.25.211.40: bytes=32 time=455ms TTL=118
Reply from 196.25.211.40: bytes=32 time=447ms TTL=118
Reply from 196.25.211.40: bytes=32 time=447ms TTL=118
Reply from 196.25.211.40: bytes=32 time=505ms TTL=118

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