[Drunken F00l]

They have implemented a temporary workaround for the ATT problem.

Tomy D. - Tuesday January 29th, 2008; 8:38 PM CST
Our networking group has taken some measures which should alleviate the effects of this issue. Can you provide a new trace and ping?

The traceroute shows that they cut ATT out of it.
Tracing route to xx.xx.xx.xx
over a maximum of 30 hops:

1 5 ms 1 ms <1 ms c1.18.364a.static.theplanet.com [74.54.24.193]
2 <1 ms <1 ms <1 ms vl1.dsr01.dllstx2.theplanet.com [12.96.160.9]
3 <1 ms <1 ms <1 ms 75.fd.5746.static.theplanet.com [70.87.253.117]

4 3 ms <1 ms <1 ms et5-1.ibr04.dllstx3.theplanet.com [70.87.253.13]

5 <1 ms <1 ms <1 ms GigabitEthernet7-3.ar2.DAL2.gblx.net [64.208.170
.197]
6 <1 ms <1 ms <1 ms te2-1-10G.ar3.DAL2.gblx.net [67.16.129.118]
7 <1 ms <1 ms <1 ms 151.164.251.161
8 13 ms 13 ms 13 ms bb2-p5-2.ksc2mo.sbcglobal.net [151.164.92.62]
...

Ping statistics for xx.xx.xx.xx:
Packets: Sent = 100, Received = 100, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 25ms, Maximum = 308ms, Average = 53ms


I think the problem may have gone away now because of this.