somethings a-fixin' to blow

[unclehobart]

,;

 

[whoreable]

 

[Luis G]

hmmm, i get a destination net unreacheable at gar1-p3103.dlstx.ip.att.net (hop 8, 50ms)

I just hate it when they won't allow me to trace

 

[Luis G]

it won't do ping either

must be some sort of ICMP blocking in there

 

[Justintime]

.edited myself.. i went too far there i think

 

[Shadowfax]

yeah, you did


funny as hell though

 

[A.B.Normal]

Even I,on the Westcoast, go through DFW .

Tracing route to otcentral.com [64.5.44.31]
over a maximum of 30 hops:

1 24 ms 22 ms 24 ms 24.69.168.1
2 24 ms 24 ms 23 ms rd2cv-ge3-2.gv.shawcable.net [24.69.50.8]
3 28 ms 30 ms 30 ms rc2wt-atm7-0-1.wa.shawcable.net [66.163.77.41]
4 31 ms 29 ms 30 ms rx0wt-abovenet.wa.shawcable.net [66.163.68.22]
5 26 ms 29 ms 33 ms so-2-0-0.cr1.sea1.us.mfnx.net [208.185.175.178]

6 46 ms 48 ms 47 ms so-3-1-0.mpr3.sjc2.us.mfnx.net [216.200.127.117]

7 88 ms 83 ms 84 ms pos2-0.mpr1.dfw2.us.mfnx.net [208.184.232.81]
8 85 ms 84 ms 84 ms so-3-0-0.cr1.dfw2.us.mfnx.net [216.200.127.213]

9 87 ms 84 ms 84 ms 209.249.20.5.available.above.net [209.249.20.5]

10 95 ms 89 ms 89 ms ge-0-1-1.cr1.dfw1.nlayer.net [69.31.63.197]
11 90 ms 89 ms 89 ms theplanet.ge-1-2-0.cr1.dfw1.nlayer.net [69.31.63
.2]
12 93 ms 90 ms 90 ms car1-1-v1.dllstx2.theplanet.com [12.96.160.11]
13 90 ms 89 ms 89 ms otcentral.com [64.5.44.31]


Pinging otcentral.com [64.5.44.31] with 32 bytes of data:

Reply from 64.5.44.31: bytes=32 time=88ms TTL=53
Reply from 64.5.44.31: bytes=32 time=84ms TTL=53
Reply from 64.5.44.31: bytes=32 time=86ms TTL=53
Reply from 64.5.44.31: bytes=32 time=87ms TTL=53

Ping statistics for 64.5.44.31:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 84ms, Maximum = 88ms, Average = 86ms