International Internet Problems

p3rs0n

Member
Joined
May 1, 2010
Messages
20
Reaction score
0
Hi, I need some help analyzing the following trace route to a WoW Server is the USA. (US-Stormrage/Texas Data center). I have a 4mb Telkom line and a 10GB Shaped SAOL account.

I have asked Telkom to test my line and I have asked SAOL to help, but they just refer me to each other. It has been like this for approx. 3 weeks, and I didn't change anything on my side. Any ping/speed test to any international server has similar results of pings north of 800. Pings to JHB/CPT are only 30-40ms. In-game ping is between 1000 and 5000 for WoW, so it is useless trying to play.

Tracing route to 206.16.23.74 over a maximum of 30 hops
1 <1 ms 1 ms <1 ms 192.168.0.2
2 * * * Request timed out.
3 9 ms 9 ms 8 ms 196.6.121.38-backbone.cybersmart.co.za [196.6.121.38]
4 9 ms 9 ms 10 ms gw-ctn-servers.cybersmart.co.za [196.41.124.1]
5 749 ms 743 ms 747 ms if-3-3-0.core4.LDN-London.as6453.net [195.219.195.225]
6 817 ms 812 ms 817 ms if-13-0-0-1772.core2.NTO-NewYork.as6453.net [216.6.97.105]
7 811 ms 819 ms * Vlan1260.icore1.NTO-NewYork.as6453.net [209.58.26.66]
8 813 ms 817 ms 814 ms 192.205.35.13
9 853 ms 856 ms 862 ms cr2.n54ny.ip.att.net [12.122.86.10]
10 856 ms * 862 ms cr2.wswdc.ip.att.net [12.122.3.38]
11 877 ms 855 ms 854 ms cr1.attga.ip.att.net [12.122.1.173]
12 855 ms 862 ms 856 ms cr2.dlstx.ip.att.net [12.122.28.174]
13 855 ms 870 ms 845 ms gar23.dlstx.ip.att.net [12.122.138.157]
14 * 843 ms 835 ms 12-122-254-154.attens.net [12.122.254.154]
15 829 ms 849 ms 852 ms mdf002c7613r0002-tge-10-1.dal1.attens.net [63.241.193.38]

Edit: Trace was run @ 10:33 AM Today (01/05/2010)

Thanks
 
Last edited:
That is a very congested route between SA and London (AS6453 is Tata Communications, Mumbai).

It is likely that traffic to that site has been allocated this routing for some reason. (If it was only recently I would say SEACOM).

Your ISP should regularly update their routing to avoid congestion like this.

I don't think its a Telkom problem, since there are no delays on any circuit that belongs to them, and if it was your DSLAM your local pings would be affected.

For the record: I get 360ms to the server via MWeb (SEACOM and CogentCo).

4 9 ms 9 ms 10 ms gw-ctn-servers.cybersmart.co.za [196.41.124.1]
5 749 ms 743 ms 747 ms if-3-3-0.core4.LDN-London.as6453.net [195.219.195.225]
 
Found this tracert from 27/4/2010 @ 01:40 AM. Can my shaped account cause this massive difference between day and night? PS: Previous posted trace was @ 10:33 AM Today (01/05/2010)

Tracing route to 206.16.23.74 over a maximum of 30 hops
1 1 ms 1 ms 1 ms 192.168.0.2
2 * * * Request timed out.
3 9 ms 10 ms 8 ms 196.6.121.38-backbone.cybersmart.co.za [196.6.121.38]
4 8 ms 9 ms 9 ms gw-ctn-servers.cybersmart.co.za [196.41.124.1]
5 164 ms 166 ms 168 ms if-3-3-0.core4.LDN-London.as6453.net [195.219.195.225]
 
Last edited:
Found this tracert from 27/4/2010 @ 01:40 AM. Can my shaped account cause this massive difference between day and night? PS: Previous posted trace was @ 10:33 AM Today (01/05/2010)

4 8 ms 9 ms 9 ms gw-ctn-servers.cybersmart.co.za [196.41.124.1]
5 164 ms 166 ms 168 ms if-3-3-0.core4.LDN-London.as6453.net [195.219.195.225]

Different ISP's can (and do) use different routing for high and low-priority traffic. As I said, AS6453 (Tata Communications) is heavily congested, since it carries a lot of traffic from India via the Middle East.

The congestion may also be a spillover from the SEACOM outage, and re-routing has not yet taken place to this site. I am not familiar enough to comment on your ISP, but 160ms is the latency you SHOULD be getting on the London hop (all other things being equal).

Edit: There is also a thread saying Cybersmart is very slow on the London route, which may be related:
http://mybroadband.co.za/vb/showthread.php?229044-Cybersmart-slow-international-access-high-latency
 
Last edited:
Top
Sign up to the MyBroadband newsletter
X