Exetel Sending data the long way around the world?

Connection issues, drop outs or speed related faults for ADSL and ADSL2+ services
Axiste
Posts: 25
Joined: Tue Jul 17, 2012 5:56 pm
Location: Townsville

Exetel Sending data the long way around the world?

Post by Axiste » Tue Jul 17, 2012 7:21 pm

As per a thread on Whirlpool > http://forums.whirlpool.net.au/forum-re ... -1&#bottom
It appears Exetel is currently sending data the long way?
My Connection to a German Server from Townsville:
Tracing route to d014.diamond.fastwebserver.de [83.136.86.14]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms DD-WRT [192.168.1.1]
2 * * * Request timed out.
3 34 ms 35 ms 34 ms 3.3.96.58.static.exetel.com.au [58.96.3.3]
4 56 ms 47 ms 47 ms PE-5018239.sglebinte01.gw.aapt.com.au [203.174.1
87.153]
5 46 ms 47 ms 47 ms te3-3.sglebdist02.aapt.net.au [203.131.60.40]
6 47 ms 47 ms 47 ms po7.sglebbrdr01.aapt.net.au [202.10.14.9]
7 51 ms 47 ms 47 ms xe7-0-0-420.sebr2.global-gateway.net.nz [202.50.
238.213]
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 201 ms 200 ms 201 ms te-7-4.car2.SanJose2.Level3.net [4.59.4.93]
12 206 ms 199 ms 199 ms vlan70.csw2.SanJose1.Level3.net [4.69.152.126]
13 198 ms 199 ms 197 ms ae-71-71.ebr1.SanJose1.Level3.net [4.69.153.5]
14 269 ms 269 ms 269 ms ae-2-2.ebr2.NewYork1.Level3.net [4.69.135.186]
15 273 ms 274 ms 275 ms ae-82-82.csw3.NewYork1.Level3.net [4.69.148.42]

16 269 ms 269 ms 269 ms ae-81-81.ebr1.NewYork1.Level3.net [4.69.134.73]

17 333 ms 333 ms 335 ms ae-44-44.ebr2.London1.Level3.net [4.69.137.77]
18 340 ms 340 ms 340 ms ae-48-48.ebr2.Amsterdam1.Level3.net [4.69.143.81
]
19 341 ms 341 ms 341 ms ae-1-100.ebr1.Amsterdam1.Level3.net [4.69.141.16
9]
20 344 ms 343 ms 351 ms ae-45-45.ebr2.Dusseldorf1.Level3.net [4.69.143.1
98]
21 344 ms 344 ms 343 ms ae-22-3205.car2.Dusseldorf1.Level3.net [4.69.161
.166]
22 394 ms 389 ms 389 ms 212.162.17.178
23 393 ms 393 ms 405 ms 62.141.47.162
24 388 ms 409 ms 395 ms d014.diamond.fastwebserver.de [83.136.86.14]

Trace complete.

My Mates connection to the same server from southern NSW, also an Exetel User:
Tracing route to d014.diamond.fastwebserver.de [83.136.86.14]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.137.1
2 * * * Request timed out.
3 41 ms 179 ms 21 ms 129.6.96.58.static.exetel.com.au [58.96.6.129]
4 * 21 ms 22 ms PE-5017319.sclarinte01.gw.aapt.com.au [203.174.1
85.153]
5 20 ms 18 ms 19 ms te3-3.sclardist02.aapt.net.au [203.131.60.32]
6 18 ms 18 ms 19 ms po7.sclarbrdr01.aapt.net.au [202.10.14.5]
7 30 ms 20 ms 23 ms xe-7-0-0-420.sgbr2.global-gateway.net.nz [202.50
.233.5]
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 174 ms 174 ms 174 ms te-7-4.car2.SanJose2.Level3.net [4.59.4.93]
13 171 ms 174 ms 180 ms vlan70.csw2.SanJose1.Level3.net [4.69.152.126]
14 173 ms 174 ms 183 ms ae-71-71.ebr1.SanJose1.Level3.net [4.69.153.5]
15 244 ms 241 ms 241 ms ae-2-2.ebr2.NewYork1.Level3.net [4.69.135.186]
16 244 ms 251 ms 248 ms ae-72-72.csw2.NewYork1.Level3.net [4.69.148.38]

17 241 ms 237 ms 240 ms ae-71-71.ebr1.NewYork1.Level3.net [4.69.134.69]

18 422 ms 308 ms 308 ms ae-44-44.ebr2.London1.Level3.net [4.69.137.77]
19 318 ms 327 ms 338 ms ae-45-45.ebr2.Amsterdam1.Level3.net [4.69.143.69
]
20 318 ms 319 ms 318 ms ae-1-100.ebr1.Amsterdam1.Level3.net [4.69.141.16
9]
21 329 ms 321 ms 326 ms ae-45-45.ebr2.Dusseldorf1.Level3.net [4.69.143.1
98]
22 321 ms 321 ms 324 ms ae-22-3205.car2.Dusseldorf1.Level3.net [4.69.161
.166]
23 375 ms 377 ms 373 ms 212.162.17.178
24 374 ms 376 ms 374 ms 62.141.47.162
25 372 ms 367 ms 389 ms d014.diamond.fastwebserver.de [83.136.86.14]

Trace complete.

My mates Work connection, Also from Southern NSW, however with TPG for the ISP:
Tracing route to d014.diamond.fastwebserver.de [83.136.86.14]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 192.168.0.254
2 5 ms 5 ms 3 ms 10.1.1.71
3 17 ms 17 ms 18 ms 10.20.21.182
4 31 ms 21 ms 19 ms syd-sot-ken-csw-1-tengi-4-1.tpgi.com.au [203.29.
135.121]
5 18 ms 17 ms 17 ms syd-sot-ken-crt1-ge-6-0-0.tpgi.com.au [202.7.171
.121]
6 247 ms 207 ms 210 ms ge5-0-5d0.cir1.seattle7-wa.us.xo.net [216.156.10
0.37]
7 207 ms 227 ms 208 ms sea-b1-link.telia.net [80.239.195.33]
8 252 ms 250 ms 250 ms den-b1-link.telia.net [213.155.134.208]
9 250 ms 254 ms 251 ms chi-bb1-link.telia.net [213.155.133.190]
10 303 ms 273 ms 273 ms nyk-bb1-link.telia.net [80.91.248.193]
11 351 ms 350 ms 352 ms ldn-bb1-link.telia.net [80.91.249.248]
12 377 ms 354 ms 354 ms adm-bb1-link.telia.net [80.91.253.191]
13 360 ms 360 ms 362 ms ddf-b2-link.telia.net [80.91.250.161]
14 398 ms 365 ms 404 ms myloc-ic-141049-ddf-b2.c.telia.net [213.248.81.5
8]
15 368 ms 367 ms 368 ms 62.141.47.162
16 367 ms 361 ms 363 ms d014.diamond.fastwebserver.de [83.136.86.14]

Trace complete.

stevecJ
Forum Admin
Posts: 1041
Joined: Wed Jan 06, 2010 9:48 am

Re: Exetel Sending data the long way around the world?

Post by stevecJ » Tue Jul 17, 2012 8:44 pm

Axiste wrote:As per a thread on Whirlpool > http://forums.whirlpool.net.au/forum-re ... -1&#bottom
It appears Exetel is currently sending data the long way?
My Connection to a German Server from Townsville:
Tracing route to d014.diamond.fastwebserver.de [83.136.86.14]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms DD-WRT [192.168.1.1]
2 * * * Request timed out.
3 34 ms 35 ms 34 ms 3.3.96.58.static.exetel.com.au [58.96.3.3]
4 56 ms 47 ms 47 ms PE-5018239.sglebinte01.gw.aapt.com.au [203.174.1
87.153]
5 46 ms 47 ms 47 ms te3-3.sglebdist02.aapt.net.au [203.131.60.40]
6 47 ms 47 ms 47 ms po7.sglebbrdr01.aapt.net.au [202.10.14.9]
7 51 ms 47 ms 47 ms xe7-0-0-420.sebr2.global-gateway.net.nz [202.50.
238.213]
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 201 ms 200 ms 201 ms te-7-4.car2.SanJose2.Level3.net [4.59.4.93]
12 206 ms 199 ms 199 ms vlan70.csw2.SanJose1.Level3.net [4.69.152.126]
13 198 ms 199 ms 197 ms ae-71-71.ebr1.SanJose1.Level3.net [4.69.153.5]
14 269 ms 269 ms 269 ms ae-2-2.ebr2.NewYork1.Level3.net [4.69.135.186]
15 273 ms 274 ms 275 ms ae-82-82.csw3.NewYork1.Level3.net [4.69.148.42]

16 269 ms 269 ms 269 ms ae-81-81.ebr1.NewYork1.Level3.net [4.69.134.73]

17 333 ms 333 ms 335 ms ae-44-44.ebr2.London1.Level3.net [4.69.137.77]
18 340 ms 340 ms 340 ms ae-48-48.ebr2.Amsterdam1.Level3.net [4.69.143.81
]
19 341 ms 341 ms 341 ms ae-1-100.ebr1.Amsterdam1.Level3.net [4.69.141.16
9]
20 344 ms 343 ms 351 ms ae-45-45.ebr2.Dusseldorf1.Level3.net [4.69.143.1
98]
21 344 ms 344 ms 343 ms ae-22-3205.car2.Dusseldorf1.Level3.net [4.69.161
.166]
22 394 ms 389 ms 389 ms 212.162.17.178
23 393 ms 393 ms 405 ms 62.141.47.162
24 388 ms 409 ms 395 ms d014.diamond.fastwebserver.de [83.136.86.14]

Trace complete.

My Mates connection to the same server from southern NSW, also an Exetel User:
Tracing route to d014.diamond.fastwebserver.de [83.136.86.14]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.137.1
2 * * * Request timed out.
3 41 ms 179 ms 21 ms 129.6.96.58.static.exetel.com.au [58.96.6.129]
4 * 21 ms 22 ms PE-5017319.sclarinte01.gw.aapt.com.au [203.174.1
85.153]
5 20 ms 18 ms 19 ms te3-3.sclardist02.aapt.net.au [203.131.60.32]
6 18 ms 18 ms 19 ms po7.sclarbrdr01.aapt.net.au [202.10.14.5]
7 30 ms 20 ms 23 ms xe-7-0-0-420.sgbr2.global-gateway.net.nz [202.50
.233.5]
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 174 ms 174 ms 174 ms te-7-4.car2.SanJose2.Level3.net [4.59.4.93]
13 171 ms 174 ms 180 ms vlan70.csw2.SanJose1.Level3.net [4.69.152.126]
14 173 ms 174 ms 183 ms ae-71-71.ebr1.SanJose1.Level3.net [4.69.153.5]
15 244 ms 241 ms 241 ms ae-2-2.ebr2.NewYork1.Level3.net [4.69.135.186]
16 244 ms 251 ms 248 ms ae-72-72.csw2.NewYork1.Level3.net [4.69.148.38]

17 241 ms 237 ms 240 ms ae-71-71.ebr1.NewYork1.Level3.net [4.69.134.69]

18 422 ms 308 ms 308 ms ae-44-44.ebr2.London1.Level3.net [4.69.137.77]
19 318 ms 327 ms 338 ms ae-45-45.ebr2.Amsterdam1.Level3.net [4.69.143.69
]
20 318 ms 319 ms 318 ms ae-1-100.ebr1.Amsterdam1.Level3.net [4.69.141.16
9]
21 329 ms 321 ms 326 ms ae-45-45.ebr2.Dusseldorf1.Level3.net [4.69.143.1
98]
22 321 ms 321 ms 324 ms ae-22-3205.car2.Dusseldorf1.Level3.net [4.69.161
.166]
23 375 ms 377 ms 373 ms 212.162.17.178
24 374 ms 376 ms 374 ms 62.141.47.162
25 372 ms 367 ms 389 ms d014.diamond.fastwebserver.de [83.136.86.14]

Trace complete.

My mates Work connection, Also from Southern NSW, however with TPG for the ISP:
Tracing route to d014.diamond.fastwebserver.de [83.136.86.14]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 192.168.0.254
2 5 ms 5 ms 3 ms 10.1.1.71
3 17 ms 17 ms 18 ms 10.20.21.182
4 31 ms 21 ms 19 ms syd-sot-ken-csw-1-tengi-4-1.tpgi.com.au [203.29.
135.121]
5 18 ms 17 ms 17 ms syd-sot-ken-crt1-ge-6-0-0.tpgi.com.au [202.7.171
.121]
6 247 ms 207 ms 210 ms ge5-0-5d0.cir1.seattle7-wa.us.xo.net [216.156.10
0.37]
7 207 ms 227 ms 208 ms sea-b1-link.telia.net [80.239.195.33]
8 252 ms 250 ms 250 ms den-b1-link.telia.net [213.155.134.208]
9 250 ms 254 ms 251 ms chi-bb1-link.telia.net [213.155.133.190]
10 303 ms 273 ms 273 ms nyk-bb1-link.telia.net [80.91.248.193]
11 351 ms 350 ms 352 ms ldn-bb1-link.telia.net [80.91.249.248]
12 377 ms 354 ms 354 ms adm-bb1-link.telia.net [80.91.253.191]
13 360 ms 360 ms 362 ms ddf-b2-link.telia.net [80.91.250.161]
14 398 ms 365 ms 404 ms myloc-ic-141049-ddf-b2.c.telia.net [213.248.81.5
8]
15 368 ms 367 ms 368 ms 62.141.47.162
16 367 ms 361 ms 363 ms d014.diamond.fastwebserver.de [83.136.86.14]

Trace complete.
Hi Axiste,

Well come to the forums. :)

We have received your email (5401536) and currently our support engineers are looking in to it. You will soon receive a reply.
To Log a fault ticket, please click click here or alternatively call Exetel VOIP numbers (02) 8030 1000 or 1300 788 141 (log faults 24x7)

=================
Exetel Support Portal
=================

Axiste
Posts: 25
Joined: Tue Jul 17, 2012 5:56 pm
Location: Townsville

Re: Exetel Sending data the long way around the world?

Post by Axiste » Tue Jul 17, 2012 8:53 pm

Cheers! 8)

Axiste
Posts: 25
Joined: Tue Jul 17, 2012 5:56 pm
Location: Townsville

Re: Exetel Sending data the long way around the world?

Post by Axiste » Wed Jul 18, 2012 5:15 pm

So I recieved a response to my ticket today from Level 1 support.

"We have checked the traceroute results and it appears that latency increases after it leave our network. Unfortunately we are unable to make improvements since its beyond our network and beyond our control."

Yes..as is apparent from the results, latency is pretty good in the first few hops that are the exetel network.. what I see to be the problem is that Exetel is then routing my data through 25 total hops.. as opposed to 16 for TPG..
Im yet to get some further results from other isp's, but I am chasing them as I am seeing plenty of other Australian users with latency around 310 - 340...

James
Exetel Staff
Posts: 1989
Joined: Mon May 09, 2005 10:27 pm

Re: Exetel Sending data the long way around the world?

Post by James » Wed Jul 18, 2012 5:24 pm

Axiste wrote:So I recieved a response to my ticket today from Level 1 support.

"We have checked the traceroute results and it appears that latency increases after it leave our network. Unfortunately we are unable to make improvements since its beyond our network and beyond our control."

Yes..as is apparent from the results, latency is pretty good in the first few hops that are the exetel network.. what I see to be the problem is that Exetel is then routing my data through 25 total hops.. as opposed to 16 for TPG..
Im yet to get some further results from other isp's, but I am chasing them as I am seeing plenty of other Australian users with latency around 310 - 340...
310 to Germany is not possible, the pings you have are quite good.

Also, not all hops are transparent, perhaps there are far more TPG hops than you think.

Dazzled
Volunteer Site Admin
Posts: 6003
Joined: Mon Nov 13, 2006 1:16 pm
Location: Sydney

Re: Exetel Sending data the long way around the world?

Post by Dazzled » Wed Jul 18, 2012 6:10 pm

Is it the long way? The main difference is that the TPG trace doesn't use NZ, and that's not your problem. The TPG connection crosses the US from a Seattle router, while yours starts at San Jose. Both go on to Dusseldorf via New York and London. Previously much Exetel traffic was routed via Singapore - do you have a traceroute for that?.

Axiste
Posts: 25
Joined: Tue Jul 17, 2012 5:56 pm
Location: Townsville

Re: Exetel Sending data the long way around the world?

Post by Axiste » Wed Jul 18, 2012 7:00 pm

310 isnt as far fetched as you might think.. Heres the 6 Aussies currently connected to the server, Im the first one..
http://ocau.com/pix/sk6et
Yes none of them is 310.. but they arent far from it at the minute I took that shot.. However the Exetel user (err ME) is definately far from having a Decent ping..

I can understand that not all Hops are transparent.. however that works both ways.. maybe TPG really is 30 hops and Exetel is 100... Can only go with what I can see :/

As far as being the long way around, I dont know, thats why I asked..
Unfortunately.. When Exetel were routing Via Singapore... (whenever that was..) I didnt get a trace.. Never occured to me that I should need one later... (Hindsight huh :D)
However, my problem has only appeared as a 24/7 issue for the last 6 days, it was a sporadic thing that lasted at most a few hours for a few weeks previous to that. Maybe if anyone could tell us exactly when the routing changed.. maybe it coincides with my issue?

Either way, Having talked to the other Aussies on the server, Im the only Exetel Customer Ive come across so far, and Im the only one who has the issue so far.

Dazzled
Volunteer Site Admin
Posts: 6003
Joined: Mon Nov 13, 2006 1:16 pm
Location: Sydney

Re: Exetel Sending data the long way around the world?

Post by Dazzled » Wed Jul 18, 2012 7:37 pm

I'm currently getting 327 ms from my home in Sydney.

PS Ran a few hundred packets - mean 328 ms

Axiste
Posts: 25
Joined: Tue Jul 17, 2012 5:56 pm
Location: Townsville

Re: Exetel Sending data the long way around the world?

Post by Axiste » Wed Jul 18, 2012 9:31 pm

Just did another one from my laptop, no change, still 400.

Dazzled
Volunteer Site Admin
Posts: 6003
Joined: Mon Nov 13, 2006 1:16 pm
Location: Sydney

Re: Exetel Sending data the long way around the world?

Post by Dazzled » Wed Jul 18, 2012 9:58 pm

My time hasn't changed - 328 ms now. The extra distance from Townsville shouldn't be cruelling you.

localhost
Posts: 10
Joined: Fri Jun 12, 2009 9:45 pm
Location: Sydney

Re: Exetel Sending data the long way around the world?

Post by localhost » Wed Jul 18, 2012 10:47 pm

James wrote:310 to Germany is not possible, the pings you have are quite good.

Also, not all hops are transparent, perhaps there are far more TPG hops than you think.
Just for the record, may I prove you wrong?

Code: Select all

  1    <1 ms     1 ms    <1 ms  192.168.1.254
  2     8 ms     7 ms     7 ms  193.1.233.220.static.exetel.com.au [220.233.1.193]
  3     8 ms     8 ms     8 ms  61.2.233.220.static.exetel.com.au [220.233.2.61]
  4     9 ms     9 ms     8 ms  PE-5017319.sclarinte01.gw.aapt.com.au [203.174.185.153]
  5     8 ms     9 ms     8 ms  te3-3.sclardist01.aapt.net.au [203.131.60.30]
  6     8 ms     8 ms     8 ms  po6.sclarbrdr01.aapt.net.au [202.10.14.3]
  7     9 ms     8 ms     9 ms  xe-7-0-0-420.sgbr2.global-gateway.net.nz [202.50.233.5]
  8     *        *        *     Request timed out.
  9     *        *        *     Request timed out.
 10     *        *        *     Request timed out.
 11     *        *        *     Request timed out.
 12   163 ms   178 ms   162 ms  te-7-4.car2.SanJose2.Level3.net [4.59.4.93]
 13   162 ms   171 ms   174 ms  vlan80.csw3.SanJose1.Level3.net [4.69.152.190]
 14   158 ms   158 ms   158 ms  ae-81-81.ebr1.SanJose1.Level3.net [4.69.153.9]
 15   240 ms   226 ms   227 ms  ae-2-2.ebr2.NewYork1.Level3.net [4.69.135.186]
 16   236 ms   231 ms   242 ms  ae-62-62.csw1.NewYork1.Level3.net [4.69.148.34]
 17   227 ms   226 ms   227 ms  ae-61-61.ebr1.NewYork1.Level3.net [4.69.134.65]
 18   295 ms   296 ms   295 ms  ae-43-43.ebr2.London1.Level3.net [4.69.137.73]
 19   303 ms   303 ms   302 ms  ae-48-48.ebr2.Amsterdam1.Level3.net [4.69.143.81]
 20   375 ms   303 ms   303 ms  ae-1-100.ebr1.Amsterdam1.Level3.net [4.69.141.169]
 21   312 ms   313 ms   309 ms  ae-46-46.ebr2.Dusseldorf1.Level3.net [4.69.143.202]
 22   308 ms   306 ms   357 ms  ae-22-3205.car2.Dusseldorf1.Level3.net [4.69.161.166]
 23   306 ms   305 ms   306 ms  212.162.17.178
 24   307 ms   306 ms   306 ms  62.141.47.162
 25   305 ms   305 ms   305 ms  d014.diamond.fastwebserver.de [83.136.86.14]
Ping statistics for 83.136.86.14:
Packets: Sent = 92, Received = 92, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 305ms, Maximum = 320ms, Average = 305ms

Axiste
Posts: 25
Joined: Tue Jul 17, 2012 5:56 pm
Location: Townsville

Re: Exetel Sending data the long way around the world?

Post by Axiste » Thu Jul 19, 2012 5:50 am

Thats pretty good.. 305ms!

Pains me to think.. so why does Townsville mean an extra 100ms! (I have isolated all my gear and tested multiple modems, computers, filters, phone ports etc. No noise on my line, line test comes up fine etc. Im synced at 22500/1000.

Dazzled
Volunteer Site Admin
Posts: 6003
Joined: Mon Nov 13, 2006 1:16 pm
Location: Sydney

Re: Exetel Sending data the long way around the world?

Post by Dazzled » Thu Jul 19, 2012 9:28 am

Axiste, I had a look at that game server trace again this morning (so I imagine it's peak hour in Europe), and there seem to be high standard deviations at the European servers at hops 22 and 23. (24: 62.141.47.162 is Fibre One Networks in Duesseldorf). Try rapidly repeating mtr (ICMP trace) or hping (any protocol). Your own single Windows traceroute doesn't seem to be delayed in the Exetel part of the route from Townsville.

PS I had another go, running fast pings with decreasing time intervals from 1 sec down to .2 sec, and the result was pretty steady between 327 and 332 ms. Packet loss increased as the interval got very short.

Axiste
Posts: 25
Joined: Tue Jul 17, 2012 5:56 pm
Location: Townsville

Re: Exetel Sending data the long way around the world?

Post by Axiste » Sat Jul 21, 2012 11:53 am

Dazzled.. Unofrtunately my tech knowledge isnt up to scratch anymore, as I have no idea about how to or what rapidly repeating mtr or hping is. Its been a few years since I did computer tech work, and now Im in the Military Blowing stuff up for a living.

As for my ping, I watched it spend 20 mins slowly creep down from 400 to 360's where it stayed for 30 mins.. Then suddenly Shot straight to 400 again.. now sitting on a 403 average again :(

Dazzled
Volunteer Site Admin
Posts: 6003
Joined: Mon Nov 13, 2006 1:16 pm
Location: Sydney

Re: Exetel Sending data the long way around the world?

Post by Dazzled » Sun Jul 22, 2012 8:57 pm

It's bad for you tonight - average over 400 ms from Sydney. Interestingly, the route across the USA has changed. I don't like the variance at hop 24 much either.

Code: Select all

 Host                                       Loss%   Snt   Last   Avg  Best  Wrst StDev
 1. Gate.home                                0.0%   215    0.6   0.7   0.5   3.5   0.4
 2. ???
 3. 61.2.233.220.static.exetel.com.au        0.0%   215   35.6  40.1  30.0 222.4  30.9
 4. PE-5017319.sclarinte01.gw.aapt.com.au   59.1%   215   33.0  33.3  31.1  55.2   3.0
 5. te3-3.sclardist01.aapt.net.au            0.0%   215   48.7  36.5  30.5 178.0  16.0
 6. po6.sclarbrdr01.aapt.net.au              0.0%   215   30.6  34.5  30.4 203.5  16.6
 7. xe-7-0-0-420.sgbr2.global-gateway.net.n  0.0%   215   50.3  35.7  30.9  64.9   5.8
 8. ???
 9. ???
10. ???
11. ???
12. te-7-4.car2.SanJose2.Level3.net          0.5%   215  196.0 195.1 179.7 363.2  35.8
13. vlan90.csw4.SanJose1.Level3.net          0.0%   215  202.4 201.4 185.3 227.5   9.4
14. ae-91-91.ebr1.SanJose1.Level3.net        0.0%   214  207.1 198.8 186.0 240.1   8.6
15. ae-2-2.ebr3.LosAngeles1.Level3.net       0.0%   214  202.3 197.7 184.1 225.1   8.3
16. 4.69.132.82                              0.0%   213  268.1 256.0 251.5 282.0   5.9
17. ae-71-71.csw2.Washington1.Level3.net     1.4%   213  272.8 278.3 253.7 308.7   9.7
18. ae-72-72.ebr2.Washington1.Level3.net     2.8%   212  272.0 276.8 255.2 300.0   9.2
19. ae-44-44.ebr2.Paris1.Level3.net          1.4%   212  371.3 352.0 332.5 375.3   7.6
20. ae-46-46.ebr1.Frankfurt1.Level3.net      3.3%   211  377.5 360.7 342.8 381.0   6.7
21. ae-71-71.csw2.Frankfurt1.Level3.net      4.3%   211  380.3 361.9 342.1 391.7   8.3
22. ae-73-73.ebr3.Frankfurt1.Level3.net      0.0%   210  369.1 354.1 338.4 386.4   9.3
23. ae-48-48.ebr1.Dusseldorf1.Level3.net     4.8%   210  389.3 368.7 348.7 391.6   8.4
24. ae-12-3105.car2.Dusseldorf1.Level3.net   0.0%   209  358.4 369.0 341.3 606.2  46.5
25. 212.162.17.178                           1.0%   209  472.5 422.7 399.6 642.8  32.7
26. 62.141.47.162                            1.0%   208  413.0 408.6 394.4 446.0   7.1
27. d014.diamond.fastwebserver.de            1.9%   207  410.7 405.4 388.6 443.0   8

Post Reply