Long awaited traceroutes

[Mangoman20]

So here goes:
Tracing route to www.l.google.com [209.85.135.103]
over a maximum of 30 hops:

1 * * * Request timed out.
2 * * * Request timed out.
3 568 ms 164 ms 242 ms 41.174.0.1
4 281 ms 229 ms 156 ms 41.160.2.33
5 144 ms 897 ms 224 ms if-11-2.bb1.JSO-Johannesburg.teleglobe.net [216.6.55.33]
6 1154 ms 550 ms 1104 ms if-4-1.core1.LHX-London.teleglobe.net [195.219.5.21]
7 669 ms 358 ms 621 ms if-10-0.core2.LHX-London.teleglobe.net [195.219.5.34]
8 456 ms 374 ms 340 ms if-3-0.mcore3.LDN-London.Teleglobe.net [195.219.96.121]
9 374 ms 419 ms 426 ms sl-gw10-lon-2-12.sprintlink.net [82.195.189.129]
10 395 ms 374 ms 764 ms sl-bb23-lon-9-0.Unknowndomain [213.206.128.105]
11 395 ms 379 ms 420 ms 213.206.128.63
12 337 ms 347 ms 317 ms sle-eurogoogle-1-0.sprintlink.net [82.195.189.186]
13 339 ms 347 ms 344 ms 209.85.252.42
14 330 ms 468 ms 374 ms 209.85.252.4
15 339 ms 339 ms 475 ms 72.14.233.106
16 743 ms 342 ms 399 ms 66.249.94.85
17 415 ms 353 ms 404 ms 72.14.239.58
18 445 ms 370 ms 344 ms mu-in-f103.google.com [209.85.135.103]

Trace complete.

Tracing route to www.iol.co.za [196.30.168.79]
over a maximum of 30 hops:

1 * * * Request timed out.
2 * * * Request timed out.
3 131 ms 161 ms 134 ms 41.174.0.1
4 286 ms 132 ms 159 ms 41.160.2.33
5 376 ms 297 ms 164 ms 41.160.2.65
6 161 ms 189 ms 182 ms vlan10.hr1.cpt1.alter.net [196.30.176.36]
7 229 ms 199 ms 179 ms likitung.iol.co.za [196.30.168.79]

Trace complete.

Tracing route to www.saix.net [196.25.1.200]
over a maximum of 30 hops:

1 * * * Request timed out.
2 * * * Request timed out.
3 158 ms 159 ms 152 ms 41.174.0.1
4 135 ms 134 ms 269 ms 41.160.2.33
5 164 ms 134 ms 159 ms 41.160.2.69
6 239 ms 167 ms 154 ms 196.43.25.137
7 236 ms 182 ms 183 ms wblv-ip-essr-1-atm-2-0-0-2.telkom-ipnet.co.za [196.43.11.30]
8 204 ms 179 ms 185 ms wblv-ip-www-1.saix.net [196.25.1.200]

Trace complete.

Tracing route to www.verizonbusiness.co.za [196.30.245.20]
over a maximum of 30 hops:

1 * * * Request timed out.
2 * * * Request timed out.
3 160 ms 156 ms 179 ms 41.174.0.1
4 243 ms 310 ms 295 ms 41.160.2.33
5 182 ms 152 ms 134 ms 41.160.2.65
6 163 ms 162 ms 156 ms vlan9.or1.jnb6.alter.net [196.30.156.65]
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 ^C

Tracing route to www.bbc.net.uk [212.58.253.67]
over a maximum of 30 hops:

1 * * * Request timed out.
2 * * * Request timed out.
3 132 ms 157 ms 157 ms 41.174.0.1
4 120 ms 167 ms 158 ms 41.160.2.33
5 133 ms 262 ms 168 ms if-11-2.bb1.JSO-Johannesburg.teleglobe.net [216.6.55.33]
6 341 ms 429 ms 336 ms if-4-1.core1.LHX-London.teleglobe.net [195.219.5.21]
7 338 ms 342 ms 310 ms if-13-1-1.mcore3.L78-London.teleglobe.net [195.2
19.144.29]
8 405 ms 399 ms 425 ms if-7-0.mcore4.NJY-Newark.teleglobe.net [195.219.144.10]
9 399 ms 399 ms 397 ms if-15-0-0-765.core2.NTO-NewYork.teleglobe.net [216.6.97.57]
10 402 ms 369 ms 459 ms nyk-b1-link.telia.net [213.248.83.149]
11 372 ms 404 ms 422 ms nyk-bb1-link.telia.net [80.91.250.162]
12 356 ms 410 ms 399 ms ldn-bb2-link.telia.net [80.91.248.253]
13 403 ms 408 ms 422 ms ldn-b3-link.telia.net [80.91.251.237]
14 400 ms 394 ms 402 ms siemens-ic-119241-ldn-b2.c.telia.net [213.248.10
4.70]
15 386 ms * 412 ms 212.58.238.133
16 380 ms 359 ms 494 ms te12-1.hsw0.cwwtf.bbc.co.uk [212.58.239.222]
17 381 ms 399 ms 401 ms www-vip.cwwtf.bbc.co.uk [212.58.253.67]

Trace complete.

Tracing route to www.is.co.za [196.34.149.154]
over a maximum of 30 hops:

1 * * * Request timed out.
2 * * * Request timed out.
3 152 ms 161 ms 148 ms 41.174.0.1
4 158 ms 133 ms 157 ms 41.160.2.33
5 151 ms 159 ms 157 ms is.jinx.net.za [198.32.142.10]
6 139 ms 194 ms 365 ms core2a-rba-gi0-2.ip.isnet.net [168.209.1.142]
7 162 ms 210 ms 164 ms core2a-bry-gi0-3-216.ip.isnet.net [168.209.100.201]
8 514 ms 162 ms 231 ms 168.209.217.250
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 ^C

[fragtion]

Ouch, Hahahahaha.
I understand it's still early in Neotel's servicing to the public, but they're going to have to roll out DSL or some other type of non-wireless last-mile service (such as FiOS, but what are the odds) in that case, because no chance in hell will that work for me. Imagine FPS gaming with 150 (FLUCTUATING by >20ms!) ping. I get that ping to the UK with my telkom unshaped DSL package.
Sorry Neotel - maybe this kind of package will do well for casual 'e-mail'/'browse' or business users, or heavy-usage users where latency is not really a consideration, but for most home users this is unfortunately not at an acceptable standard. It's a pity, because the packages/pricing are pretty competitive otherwise.

[plenty]

I would say rather disappointing on the whole with international terrible! :(
Considering they don't (AFAIK) make use of Satellite intl - the shaping and routing going on for that intl link is truly awful.

I don't really expect the Neotel product to be competing but...
Here are mine from the office - IS Business DSL over Fibre.

clarity.jolt.co.uk
traceroute to clarity.jolt.co.uk (195.149.21.11), 30 hops max, 40 byte packets
1 192.168.0.1 (192.168.0.1) 0.605 ms 1.078 ms 1.310 ms
2 196.212.x.x (196.212.x.x) 5.792 ms 6.028 ms 6.018 ms
3 196.212.224.97 (196.212.224.97) 42.981 ms 47.456 ms 50.445 ms
4 cdsl1-rba-gi4-1-47.ip.isnet.net (196.36.80.217) 54.681 ms 58.918 ms 66.900 ms
5 196.26.96.195 (196.26.96.195) 68.889 ms 72.376 ms 78.612 ms
6 core1b-rba-7600-gi1-0-5.ip.isnet.net (196.26.0.181) 81.849 ms 59.653 ms 40.927 ms
7 168.209.161.202 (168.209.161.202) 220.049 ms 222.282 ms 226.014 ms
8 168.209.160.209 (168.209.160.209) 230.498 ms 216.320 ms 220.301 ms
9 core1a-dock-gi1-0-19-22.ip.isnet.net (168.209.161.161) 223.533 ms 227.520 ms 231.256 ms
10 cp1-dock-gi0-1.ip.isnet.net (168.209.246.8) 546.548 ms 547.536 ms 547.027 ms
11 te1-3.cr05.tn5.bb.gxn.net (195.66.224.29) 229.052 ms 233.283 ms 236.267 ms
12 gi1-1-6.ar01.tn5.bb.gxn.net (62.72.140.142) 240.499 ms 225.808 ms gi2-48-5.ar01.tn5.bb.gxn.net (62.72.140.14) 213.575 ms
13 ge-0-0-0-3801.jolt-gw.cust.pipex.net (212.241.241.14) 217.058 ms 220.792 ms 212.581 ms
14 clarity.jolt.co.uk (195.149.21.11) 226.822 ms 222.815 ms 229.754 ms


Google - Same ip as above
traceroute to 209.85.135.103 (209.85.135.103), 30 hops max, 40 byte packets
1 192.168.0.1 (192.168.0.1) 0.708 ms 0.923 ms 1.406 ms
2 196.212.x.x (196.212.x.x) 6.135 ms 6.124 ms 6.359 ms
3 196.212.224.97 (196.212.224.97) 44.824 ms 48.559 ms 52.546 ms
4 cdsl1-rba-gi4-1-47.ip.isnet.net (196.36.80.217) 56.532 ms 61.514 ms 65.750 ms
5 196.26.96.195 (196.26.96.195) 70.987 ms 76.972 ms 79.461 ms
6 core1b-rba-7600-gi1-0-10.ip.isnet.net (168.209.1.181) 84.196 ms 75.362 ms 50.417 ms
7 168.209.161.204 (168.209.161.204) 223.792 ms 228.273 ms 232.009 ms
8 168.209.161.91 (168.209.161.91) 239.743 ms 211.078 ms 219.057 ms
9 core1a-dock-gi1-0-19-24.ip.isnet.net (168.209.161.163) 218.292 ms 223.526 ms 227.513 ms
10 cp1-dock-gi0-2.ip.isnet.net (168.209.246.69) 230.999 ms 233.988 ms 209.314 ms
11 195.66.224.125 (195.66.224.125) 229.285 ms 229.769 ms 231.254 ms
12 209.85.252.42 (209.85.252.42) 229.990 ms 220.071 ms 209.823 ms
13 209.85.252.4 (209.85.252.4) 229.544 ms 233.528 ms 225.069 ms
14 72.14.233.106 (72.14.233.106) 234.078 ms 232.310 ms 235.551 ms
15 66.249.94.85 (66.249.94.85) 239.532 ms 243.016 ms 257.492 ms
16 72.14.239.58 (72.14.239.58) 252.480 ms 209.85.253.26 (209.85.253.26) 252.305 ms 72.14.239.54 (72.14.239.54) 261.283 ms
17 mu-in-f103.google.com (209.85.135.103) 254.273 ms 259.505 ms 258.801 ms

www.is.co.za
1 192.168.0.1 (192.168.0.1) 0.610 ms 1.084 ms 1.317 ms
2 196.212.x.x (196.212.x.x) 5.549 ms 6.033 ms 6.025 ms
3 196.212.224.97 (196.212.224.97) 56.229 ms 56.456 ms 56.695 ms
4 cdsl1-rba-gi4-1-47.ip.isnet.net (196.36.80.217) 54.185 ms 58.672 ms 62.407 ms
5 196.26.96.195 (196.26.96.195) 67.644 ms 72.380 ms 76.618 ms
6 core1a-rba-gi0-2.ip.isnet.net (168.209.1.141) 81.854 ms 65.650 ms 50.920 ms
7 core1a-bry-gi0-3-215.ip.isnet.net (168.209.0.98) 55.400 ms 59.132 ms 64.615 ms
8 168.209.218.251 (168.209.218.251) 68.847 ms 58.667 ms 63.649 ms
9 * * *
10 * * *
11 ^C


www.iol.co.za - smooth all the way until we hit Verizon...
traceroute to www.iol.co.za (196.30.168.79), 30 hops max, 40 byte packets
1 192.168.0.1 (192.168.0.1) 0.856 ms 1.083 ms 1.312 ms
2 196.212.x.x (196.212.x.x) 6.043 ms 6.278 ms 6.268 ms
3 196.212.224.97 (196.212.224.97) 41.982 ms 47.457 ms 51.194 ms
4 cdsl1-rba-gi4-1-47.ip.isnet.net (196.36.80.217) 55.930 ms 60.417 ms 64.153 ms
5 196.26.96.195 (196.26.96.195) 81.882 ms 81.874 ms 82.110 ms
6 cp1-jinx-gi0-3.ip.isnet.net (168.209.1.135) 84.847 ms 68.147 ms 42.424 ms
7 ge0-3.br1.jnb7.alter.net (196.30.228.241) 46.405 ms 51.387 ms 55.619 ms
8 ge0-1.cr1.jnb7.alter.net (196.30.228.122) 60.851 ms 41.665 ms 45.395 ms
9 srp1-0-0.gw2.cpt1.alter.net (196.31.249.67) 202.032 ms 205.014 ms 209.746 ms
10 vlan10.hr1.cpt1.alter.net (196.30.176.36) 205.489 ms 179.593 ms 179.832 ms
11 likitung.iol.co.za (196.30.168.79) 213.289 ms 216.274 ms 221.261 ms

Guess it's all about who you peer with :o

[fragtion]

Guess it's all about who you peer with :o
Well, yeah, and obviously the type of product...

It's pretty simple really, 'first-hop latency' should be less than 50ms for an adequate service. If given the choice, i'd settle for nothing more than 15ms first-hop.
My DSL connection gives a stable 8ms to exchange, which is really perfect. Anything lower than that would be awesome, but once it starts going above 20ms it's already too much. iBurst is around 50-100ms... crap for latency-sensitive consumers. The only other viable wireless option in terms of latency at this point seems to be WIMAX, and even that's pretty borderline...

[InsaniacZA]

lol @ those pings... unfortunately Neotel has nothing on Telkom until they start using proper lines and stop worrying about giving people coverage through wireless... wireless is useless for gaming, and for R1000 pm for less then 1mbps.. blah!

[SUPERMAN89]

WOW ..pings of that nature?

[ambo]

Guess it's all about who you peer with :o5 hops to JINX - thats not bad... and you can get everyone there...

Oh no wait... sorry... except for SAIX :p :D

[Zyzzyva]

Cdma is not a low latency product. We will have to wait for wimax for this.

I wont sign up for cdma at any point, but i will when wimax lands.

[ambo]

Cdma is not a low latency product. We will have to wait for wimax for this.I'm interested in where you get your info from. Low latency WiMAX is not something that is likely to be affordable to the consumer sector of the market.

[Daniedj]

It seems that Neotel has fewer hops than IS I'm using.