DSL latency issues

to0kenZA

Expert Member
Joined
Jan 14, 2010
Messages
2,351
Reaction score
7
Location
Somerset West
Recently my ADSL line started giving me major ****.

Look at this BS:

Pinging 196.41.0.11 with 32 bytes of data:
Reply from 196.41.0.11: bytes=32 time=1155ms TTL=59
Reply from 196.41.0.11: bytes=32 time=1192ms TTL=59
Reply from 196.41.0.11: bytes=32 time=1232ms TTL=59
Reply from 196.41.0.11: bytes=32 time=1230ms TTL=59
Reply from 196.41.0.11: bytes=32 time=973ms TTL=59
Reply from 196.41.0.11: bytes=32 time=781ms TTL=59
Reply from 196.41.0.11: bytes=32 time=625ms TTL=59
Reply from 196.41.0.11: bytes=32 time=558ms TTL=59
Reply from 196.41.0.11: bytes=32 time=622ms TTL=59
Reply from 196.41.0.11: bytes=32 time=695ms TTL=59
Reply from 196.41.0.11: bytes=32 time=702ms TTL=59
Reply from 196.41.0.11: bytes=32 time=745ms TTL=59
Reply from 196.41.0.11: bytes=32 time=718ms TTL=59
Reply from 196.41.0.11: bytes=32 time=730ms TTL=59
Reply from 196.41.0.11: bytes=32 time=833ms TTL=59
Reply from 196.41.0.11: bytes=32 time=844ms TTL=59
Reply from 196.41.0.11: bytes=32 time=790ms TTL=59
Reply from 196.41.0.11: bytes=32 time=749ms TTL=59
Reply from 196.41.0.11: bytes=32 time=763ms TTL=59
Reply from 196.41.0.11: bytes=32 time=694ms TTL=59
Reply from 196.41.0.11: bytes=32 time=613ms TTL=59
Reply from 196.41.0.11: bytes=32 time=674ms TTL=59
Reply from 196.41.0.11: bytes=32 time=730ms TTL=59
Reply from 196.41.0.11: bytes=32 time=743ms TTL=59
Reply from 196.41.0.11: bytes=32 time=688ms TTL=59
Reply from 196.41.0.11: bytes=32 time=678ms TTL=59
Reply from 196.41.0.11: bytes=32 time=630ms TTL=59
Reply from 196.41.0.11: bytes=32 time=595ms TTL=59
Reply from 196.41.0.11: bytes=32 time=634ms TTL=59
Reply from 196.41.0.11: bytes=32 time=698ms TTL=59
Reply from 196.41.0.11: bytes=32 time=598ms TTL=59
Reply from 196.41.0.11: bytes=32 time=448ms TTL=59
Reply from 196.41.0.11: bytes=32 time=375ms TTL=59
Reply from 196.41.0.11: bytes=32 time=453ms TTL=59
Reply from 196.41.0.11: bytes=32 time=508ms TTL=59
Reply from 196.41.0.11: bytes=32 time=476ms TTL=59
Reply from 196.41.0.11: bytes=32 time=477ms TTL=59
Reply from 196.41.0.11: bytes=32 time=461ms TTL=59
Reply from 196.41.0.11: bytes=32 time=444ms TTL=59
Reply from 196.41.0.11: bytes=32 time=388ms TTL=59
Reply from 196.41.0.11: bytes=32 time=435ms TTL=59
Reply from 196.41.0.11: bytes=32 time=352ms TTL=59
Reply from 196.41.0.11: bytes=32 time=285ms TTL=59
Reply from 196.41.0.11: bytes=32 time=338ms TTL=59
Reply from 196.41.0.11: bytes=32 time=332ms TTL=59
Reply from 196.41.0.11: bytes=32 time=429ms TTL=59
Reply from 196.41.0.11: bytes=32 time=492ms TTL=59
Reply from 196.41.0.11: bytes=32 time=559ms TTL=59
Reply from 196.41.0.11: bytes=32 time=616ms TTL=59
Reply from 196.41.0.11: bytes=32 time=667ms TTL=59
Reply from 196.41.0.11: bytes=32 time=705ms TTL=59
Reply from 196.41.0.11: bytes=32 time=688ms TTL=59
Reply from 196.41.0.11: bytes=32 time=625ms TTL=59
Reply from 196.41.0.11: bytes=32 time=576ms TTL=59
Reply from 196.41.0.11: bytes=32 time=546ms TTL=59

Ping statistics for 196.41.0.11:
Packets: Sent = 55, Received = 55, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 285ms, Maximum = 1232ms, Average = 647ms



I've called the called the Telkom call centre about 50 now about this, some of the agents being helpful, some being utterly useless. This usually happens during peak times, but also randomly during the day. I have replaced all my hardware. Modem, filter, RJ11 and my Cat5 cable and the issue still persists. I've also used multiple DSL accounts with different ISPs. They keep insisting that the line looks fine.

I've spoken to some more senior people there (I think) and they sent a tech out to check the line, during the morning, when there was nothing wrong and then concluded that there's nothing wrong with my line and didn't need to go check the exchange. Some lady even mentioned that they need to check the exchange because the wires might be crossing or there might be some other underlying layer 3 problem or what not. But they still haven't fixed it and I'm paying for a 4mb line that's pretty much fscking unusable at the moment and I can't even play my online games.

I just don't know WTF to do anymore. Does anyone have any suggestions? I really feel like pulling this damn cable out of the ground and have them come install a new one. :mad::mad::mad:
 
Congested exchange. Nothing you can do except whine about it & hope they upgraded it.

Post some line & error stats anyway for good measure.

Also what ip is that? First hop? Rather post a trace to your ISP homepage.
 
Last edited:
Congested exchange. Nothing you can do except whine about it & hope they upgraded it.

Post some line & error stats anyway for good measure.

Also what ip is that? First hop? Rather post a trace to your ISP homepage.

That's a Vox DNS server. I'm using a Vox account. Normal response times to this server for me is no more than 30ms.

My line stats look good, I've checked that in the very beginning. Looks to me like a congested exchange as well, but upon asking them about it, they just deny it as expected. I'm hoping to get hold of their accounting department to refuse paying the full amout because I can hardly use this line when I want to.
 
Top
Sign up to the MyBroadband newsletter
X