IS International really bad?

T

trancehead

Active Member
Joined
Aug 2, 2005
Messages
97
Reaction score
0
Location
Cape Town
Hello,

The last week or two have been absolute hell when it comes to accessing International sites. We currently go through a wireless provider who then sends traffic through some IS ADSL lines. Local sites are a fast as normal but as soon as it goes international it degrades significantly.

Anyone else having this problem or know what is going on?

Code: 
Ping: www.yahoo.com

Pinging www.yahoo.akadns.net [68.142.197.89] with 32 bytes of data:

Reply from 68.142.197.89: bytes=32 time=1160ms TTL=45
Request timed out.
Reply from 68.142.197.89: bytes=32 time=1361ms TTL=45
Request timed out.

Ping statistics for 68.142.197.89:
    Packets: Sent = 4, Received = 2, Lost = 2 (50% loss),
Approximate round trip times in milli-seconds:
    Minimum = 1160ms, Maximum = 1361ms, Average = 1260ms

Code: 
Traceroute : www.yahoo.com
Tracing route to www.yahoo.akadns.net[68.142.226.52]
over a maximum of 30 hops:

  1    <1 ms     1 ms    <1 ms     192.168.11.225
  2     6 ms      3 ms     3 ms     172.16.0.137
  3    10 ms     9 ms      8 ms     wan.paarlonline.co.za [172.31.0.1]
  4     8 ms      11 ms    8 ms     196.211.2.129
  5     *           *         474 ms  196.211.128.245
  6   578 ms     *         412 ms   196.36.80.209
  7   394 ms     515 ms     *       196.26.96.198
  8     *           *            *       Request timed out.
  9   987 ms    1058 ms     *      168.210.250.80
 10  1168 ms   879 ms     *       168.209.244.7
 11     *         1103 ms  1179 ms  nyiix.bas1-m.nyc.yahoo.com [198.32.160.121]
 12   845 ms    *          1027 ms  ge-0-0-9.p812.pat1.dce.yahoo.com [216.115.98.105
]
 13  1092 ms    1104 ms     *     ge-3-1-0.p440-msr1.re1.yahoo.com [216.115.96.189
]
 14  1043 ms    1133 ms     *     t-2-1.bas2.re2.yahoo.com [206.190.33.93]
 15  1111 ms    1023 ms  1036 ms  p21.www.re2.yahoo.com [68.142.226.52]

Trace complete.
 
Tracing route to www.yahoo.akadns.net [68.142.197.88]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms home.gateway [192.168.1.254]
2 293 ms 358 ms 290 ms dsl-146-0-01.telkomadsl.co.za [165.146.0.1]
3 362 ms 359 ms 289 ms rndf-ip-er-2-fe-12-0-1-610.telkom-ipnet.co.za [1
96.43.10.181]
4 * * * Request timed out.
5 734 ms 716 ms 714 ms ash-ip-dir-equinix-pos-6-1.telkom-ipnet.co.za [1
96.43.9.146]
6 713 ms 713 ms 716 ms so-3-0-1.ar1.DCA3.gblx.net [208.49.224.161]
7 708 ms 716 ms 715 ms so1-3-0-2488M.ar1.DCA3.gblx.net [67.17.79.85]
8 721 ms 715 ms 719 ms yahoo-2.ar1.DCA3.gblx.net [208.51.74.182]
9 730 ms 715 ms * so-0-0-0.pat1.dax.yahoo.com [216.115.101.145]
10 716 ms 721 ms * ge-0-1-0-p221.msr2.mud.yahoo.com [216.115.104.10
3]
11 * 770 ms 715 ms ten-9-1.bas1.mud.yahoo.com [68.142.193.29]
12 707 ms 718 ms 716 ms p25.www.mud.yahoo.com [68.142.197.88]

Trace complete.
Click to expand...

Well, that was certainly an interesting result - the 2nd hop pings are MAD, they're normally 30ms.

Anyway, an hour ago I was getting similar packet loss towards www.google.com . IS might be having problems, but Telkom is having the same problems it seems (Or your IS tracert went through Telkom somehow).
 
Tracing route to www.l.google.com [66.102.9.104]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms home.gateway [192.168.1.254]
2 36 ms 36 ms 37 ms dsl-146-0-01.telkomadsl.co.za [165.146.0.1]
3 34 ms 35 ms 36 ms rndf-ip-er-2-fe-12-0-1-610.telkom-ipnet.co.za [1
96.43.10.181]
4 * * * Request timed out.
5 420 ms * 423 ms lon-ip-dir-telecity-pos-7-1.telkom-ipnet.co.za [
196.43.9.157]
6 423 ms 430 ms * ldn-tch-i1-link.telia.net [213.155.141.153]
7 418 ms 419 ms * ldn-b1-geth4-0.telia.net [213.248.100.217]
8 434 ms 442 ms * google-104716-ldn-b1.c.telia.net [213.248.74.194
]
9 430 ms 425 ms 422 ms 72.14.238.242
10 440 ms 447 ms 438 ms 216.239.49.254
11 456 ms 442 ms 440 ms 216.239.48.158
12 444 ms 435 ms 435 ms 64.233.174.186
13 462 ms * 443 ms 64.233.174.14
14 449 ms 447 ms 437 ms 66.102.9.104

Trace complete.
Click to expand...
This is more in line with what I've been getting recently.
 
A site like yahoo is still reasonable probably becuase of their huge data centres. But for most other, smaller international sites (it seems mostly USA hosted sites) it is like treacle. CNN.com won't load at all.

I am pulling my hair out as I am a developer and the sites I work on are hosted in the USA and I am barely able to FTP and it takes forever just to see a change that I made.

The problem appears to be variable bandwidth. One minute I can't load cnn.com and the next it comes up (almost) normally.
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X