North American Network Operators Group|
Date Prev | Date Next |
Date Index |
Thread Index |
Author Index |
RE: UUNet / ATT peering meltdown?
- From: Travis Pugh
- Date: Tue Mar 13 14:44:53 2001
That may be a little extreme ... I generally get good support from all of
my upstreams. However, there's a certain amount of static to be expected
when you start raising inter-provider issues, especially when all the
latency seems be caused by the provider you aren't a customer of.
On Tue, 13 Mar 2001, Tom Thomas wrote:
> Bad attitudes to a customer are a clear indication you should take your
> money elsewhere.
> Personally I like NetRail, they are courteous and responsive.
> -----Original Message-----
> From: email@example.com [mailto:firstname.lastname@example.org]On Behalf Of
> Travis Pugh
> Sent: Tuesday, March 13, 2001 1:13 PM
> To: email@example.com
> Subject: 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 (22.214.171.124) 9.212 ms 9.633 ms 10.363
> 7 126.96.36.199 (188.8.131.52) 9.642 ms 12.967 ms 12.137 ms
> 8 gbr3-p50.n54ny.ip.att.net (184.108.40.206) 418.555 ms 416.419 ms
> 419.819 ms
> ATT --> UUNet
> 8 ggr1-p370.attga.ip.att.net (220.127.116.11) [AS 7018] 20 msec 24 msec
> 20 msec
> 9 att-gw.atl.uu.net (18.104.22.168) [AS 7018] 396 msec 396 msec 392
> 10 179.at-6-0-0.XR1.ATL5.ALTER.NET (22.214.171.124) [AS 701] 388 msec 388
> msec 388 msec