This does not make sense!!!

[bboy]

Doing a tracer

Tracing route to google.com [74.125.233.4]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 192.168.2.11
2 10 ms 9 ms 9 ms npmb-ip-bb-1.ipnet.wa.co.za [41.185.170.1]
3 35 ms 38 ms 33 ms 196.220.59.222
4 35 ms 34 ms 34 ms wnls-cr2-vl-801.wa.co.za [41.185.0.66]
5 312 ms 304 ms 302 ms wbrs-csw1-vl-140.wa.co.za [41.185.1.5]
6 331 ms 330 ms 330 ms google.cinx.net.za [196.223.22.41]
7 303 ms 302 ms 300 ms 64.233.174.105
8 345 ms 331 ms 311 ms cpt01s01-in-f4.1e100.net [74.125.233.4]

As you can see the 4th hop is still a lovely 35ms

BUT IF I DO A TRACER TO THAT IP

Tracing route to wnls-cr2-vl-801.wa.co.za [41.185.0.66]
over a maximum of 30 hops:

1 1 ms 2 ms 1 ms 192.168.2.11
2 9 ms 9 ms 9 ms npmb-ip-bb-1.ipnet.wa.co.za [41.185.170.1]
3 39 ms 36 ms 34 ms 196.220.59.222
4 334 ms 335 ms 331 ms wnls-cr2-vl-801.wa.co.za [41.185.0.66]


WTF its now 300+

 

[Anthro]

You are suffering from a crowded exchange. Not much you can do - you can try and complain and punch Telkom in the kidney

 

[grim]

You are suffering from a crowded exchange. Not much you can do - you can try and complain and punch Telkom in the kidney

No he isn't, the 2nd hop is the exchange, that's already on the WA network where the latency shoots up. Post in the WA thread and ask them to investigate. Don't expect much though.

 

[bboy]

What I don't understand is, a direct ping for that ip results in 300ms , however doing a tracert to that ip only gives 35ms

 

[Hummercellc]

Mweb is the same... Might be problem on Telkom's IPC I think...

 

[WAJeff]

Hi bboy

Can you drop me a PM with your account details so I can follow this up for you.