ADSL Latency Issue

[pictograph]

I got 4mb/s ADSL installed about 2 months ago and ever since I got it there have been latency issues. I have phoned Telkom multiple times and created faults but these faults are always resolved the next day automatically and I think that all they are doing each time is resetting the ports (which I told them does not help).

Basically the latency is roughly 200-300ms above what is should be for most of the day, it seems to settle down by like 2-3am which is quite useless and even when it does settle down to an acceptable level most of the time it will spike periodically to 150-250ms then back down making playing any online game a nightmare.

I am posting here to find out what could be the cause of this because Telkom isn't helping at all in resolving the matter. They have been to the box near me to check it up and have phoned and said that everything is fine on their side.

Here is my tracert to www.telkom.co.za:

1 289 ms 294 ms 281 ms 41-132-44-1.dsl.mweb.co.za [41.132.44.1]
2 336 ms 353 ms 350 ms tengig-0-0-0-104.vic-ipc-2.mweb.co.za [196.22.163.218]
3 201 ms 178 ms 198 ms vl-92.vic-hscore-1.mweb.co.za [196.22.189.2]
4 171 ms 155 ms 176 ms tengig-0-0-0-0-11.vic-up-1.mweb.co.za [196.22.169.225]
5 240 ms 236 ms 239 ms rrba-ip-hsll-1-wan.telkom-ipnet.co.za [196.25.8.249]
6 190 ms 178 ms 188 ms rrba-ip-esr-1-ge-6-0-0.telkom-ipnet.co.za [196.43.11.166]
7 227 ms 226 ms 238 ms rrba-ip-bssr-1-ge-2-48.telkom-ipnet.co.za [196.43.23.6]
8 317 ms 320 ms 312 ms nbsc-ip-bssr-1-atm-5-0-0-1.telkom-ipnet.co.za [196.43.23.30]
9 270 ms 250 ms 239 ms nbsc-ip-rcache-1-vif2.telkom-ipnet.co.za [196.43.22.222]

Trace complete.

Here is a speedtest and pingtest:



I have netlimiter installed and no downloads or uploads happening whilst doing these tests, my ping to the router is >1ms and althouh I am currently using an mweb uncapped account, I have tested with a SAIX unshaped 1GB account and it yielded the same results. I have also tested with a different router and a different computer and the latency is still high.

I have heard that the exchange/DSLAM I am connected to could not have enough bandwidth allocated to it and thus could be overloaded and causing this issue for everyone using this exhange/DSLAM. Is there any way of finding out which you are plugged into and if there is any way of changing the one you are currently using? I am in the Pinelands area of Cape town if anyone is having similar issues at this location.

I'm not sure if one would require additional information about my connection or something else in order to help out but any help would be greatly appreciated.

Rob

 

[bleh69]

here's my tracert. Mweb 4Meg uncapped.

Since your first hop is 200+ ms... it must be the DSLAM... or your router.


1 OSIRIS (192.168.1.1) 5.358 ms 5.389 ms 5.432 ms
2 ROUTER (192.168.0.1) 12.341 ms 13.341 ms 14.560 ms
3 41-133-92-1.dsl.mweb.co.za (41.133.92.1) 25.565 ms 26.559 ms 30.507 ms
4 tengig-0-0-0-104.vic-ipc-1.mweb.co.za (196.22.169.146) 40.770 ms 49.918 ms 51.198 ms
5 vl-92.vic-hscore-2.mweb.co.za (196.22.189.3) 51.240 ms vl-92.vic-hscore-1.mweb.co.za (196.22.189.2) 52.203 ms 53.178 ms
6 tengig-0-0-0-0-11.vic-up-1.mweb.co.za (196.22.169.225) 54.946 ms 52.841 ms 54.475 ms
7 rrba-ip-hsll-1-wan.telkom-ipnet.co.za (196.25.8.249) 55.442 ms 50.570 ms 50.672 ms
8 rrba-ip-esr-1-ge-6-0-0.telkom-ipnet.co.za (196.43.11.166) 54.996 ms 16.854 ms 21.298 ms
9 rrba-ip-bssr-1-ge-2-48.telkom-ipnet.co.za (196.43.23.6) 26.583 ms 30.035 ms 38.843 ms
10 nbsc-ip-bssr-1-atm-5-0-0-1.telkom-ipnet.co.za (196.43.23.30) 39.817 ms 56.510 ms 57.801 ms
11 nbsc-ip-rcache-1-vif2.telkom-ipnet.co.za (196.43.22.222) 57.843 ms 58.979 ms 59.022 ms

 

[fragtion]

Like many others who have complained about this problem, your Telkom exchange/DSLAM is overcontended, and therefore the cause for this fault. This is Telkom's responsibility to fix, and I find it ironic how they assert that their network is 10Mbps-ready when clearly many exchanges are heavily overloaded with the current maximum customer line speed being not even half of that.