UUNet / ATT peering meltdown?

Not to open up any potential disputes, but has anyone heard what is going
on between UUNet and AT&T on the east coast? We've been seeing this kind
of performance for a week ... standard UUNet NOC response was "it's ATT's
problem, call them" which doesn't do me a whole lot of good since we're
not an ATT customer.

UUNet --> ATT

6 POS6-0.BR3.NYC9.ALTER.NET (152.63.24.97) 9.212 ms 9.633 ms 10.363
ms
7 137.39.52.74 (137.39.52.74) 9.642 ms 12.967 ms 12.137 ms
8 gbr3-p50.n54ny.ip.att.net (12.123.1.122) 418.555 ms 416.419 ms
419.819 ms

ATT --> UUNet

  8 ggr1-p370.attga.ip.att.net (12.123.20.253) [AS 7018] 20 msec 24 msec
20 msec
  9 att-gw.atl.uu.net (192.205.32.130) [AS 7018] 396 msec 396 msec 392
msec
10 179.at-6-0-0.XR1.ATL5.ALTER.NET (152.63.82.190) [AS 701] 388 msec 388
msec 388 msec

Thanks.

-travis

Travis Pugh wrote:

Not to open up any potential disputes, but has anyone heard what is going
on between UUNet and AT&T on the east coast? We've been seeing this kind
of performance for a week ... standard UUNet NOC response was "it's ATT's
problem, call them" which doesn't do me a whole lot of good since we're
not an ATT customer.

I've reported a few problems as an ATT Broadband customer, and gotten
nowhere. From the cable modem at my house, a traceroute to www.uu.net
goes through a router that introduces a 400ms minimum delay. Traces to
ftp.uu.net, in a different netblock, don't incur that delay. It appears
there's a problem between these two, and it affects only some netblocks
and not others.

Does anyone know if this is still and issue?

Joe Marr