trace route look good.






Tracing route to 8.9.4.77 over a maximum of 30 hops

1 1 ms 1 ms 1 ms *.*.*.*
2 9 ms 7 ms 13 ms 73.12.24.1
3 12 ms 15 ms 12 ms 68.86.180.33
4 29 ms 27 ms 36 ms 68.86.180.54
5 28 ms 31 ms 34 ms 12.118.120.5
6 50 ms 48 ms 48 ms tbr1-p012201.attga.ip.att.net [12.123.20.178]
7 61 ms 46 ms 55 ms tbr2-cl17.wswdc.ip.att.net [12.122.10.69]
8 47 ms 51 ms 53 ms sar1-a360s3.wswdc.ip.att.net [12.123.8.117]
9 50 ms 53 ms 52 ms so-9-0-0.car3.Washington1.Level3.net [209.244.21
9.141]
10 48 ms 54 ms 52 ms ae-2-56.bbr2.Washington1.Level3.net [4.68.121.16
1]
11 60 ms 60 ms 62 ms ae-0-0.bbr1.Chicago1.Level3.net [64.159.1.33]
12 65 ms * 64 ms ae-14-55.car4.Chicago1.Level3.net [4.68.101.136]

13 * 62 ms 71 ms 4.79.66.146
14 59 ms 65 ms 58 ms 8.9.4.77


Ping Plotter

I have problem to. Look at my trace




Target Name: N/A

IP: 8.9.4.80

Date/Time: 31.10.2006 22:51:18



2 8 ms 7 ms [10.138.0.1]

3 10 ms 8 ms tromso-stalheim.alfanett.no [62.16.253.65]

4 31 ms 29 ms [195.134.55.21]

5 36 ms 38 ms [195.134.55.5]

6 48 ms 37 ms ti0001b300-ge1-1-3.ti.telenor.net [148.122.8.65]

7 38 ms 38 ms nb01b12-ge0-0.nb.telenor.net [217.70.229.65]

8 37 ms 38 ms te3-1.ar1.OSL2.gblx.net [64.210.28.221]

9 104 ms 93 ms ge-6-17.car1.Amsterdam1.Level3.net [213.244.165.237]

10 183 ms 124 ms ge-1-2.core2.Amsterdam1.Level3.net [4.68.120.132]

11 198 ms 128 ms so-4-0-0.mp2.Amsterdam1.Level3.net [4.68.113.82]

12 -32764 ms 188 ms ae-0-0.bbr2.Chicago1.Level3.net [64.159.1.34]

13 -32764 ms 186 ms ae-14-51.car4.Chicago1.Level3.net [4.68.101.8]

14 229 ms 198 ms [4.79.66.146]

15 230 ms 187 ms [8.9.4.80]

Seems like they have been smoking some heavy stuff in Amsterdam - lol

Hopefully it will get fixed or we will have trouble to join the scrim on Saturday.