Yes it looks like Qwest wasn't having problems. The issues we were seeing appear to be related to AT&T.
Funny, I saw nothing on Qwest's stat site, either:
http://stat.qwest.net/statqwest/perfRptIndex.jsp
http://stat.qwest.net/index_flash.html
Frank
-----Original Message-----
From: owner-nanog@merit.edu [mailto:owner-nanog@merit.edu] On Behalf Of Jeff
Shultz
Sent: Sunday, January 20, 2008 12:16 AM
To: Daniel; nanog@merit.edu
Subject: Re: qwest outage?
Daniel wrote:
> Anyone currently aware of a Qwest outage? My qwest sites are down, even
> qwest.com <http://qwest.com>
>
> daniel
Nope.
traceroute www.qwest.com
traceroute to www.qwest.com (155.70.40.252), 30 hops max, 40 byte packets
1 192.168.255.1 (192.168.255.1) 0.287 ms 0.232 ms 0.332 ms
2 stayton2-stinger-gw.wvi.com ( 67.43.68.1) 7.627 ms 7.986 ms 7.097 ms
3 wvi-gw.wvi.com (204.119.27.254) 7.637 ms 8.202 ms 7.607 ms
4 69.59.218.105 (69.59.218.105) 8.889 ms 9.814 ms 8.926 ms
5 sst-6509-gi13-p2p-peak.silverstartelecom.com (12.111.189.105)
22.849 ms 20.245 ms 16.434 ms
6 sst-m10-fe002-p2p-6509-fa347.silverstartelecom.com (12.111.189.233)
10.069 ms 10.456 ms 9.801 ms
7 12.118.177.73 (12.118.177.73) 10.369 ms 11.057 ms 9.951 ms
8 gr1.st6wa.ip.att.net ( 12.123.44.122) 33.398 ms 32.790 ms 32.975 ms
9 tbr1.st6wa.ip.att.net (12.122.12.157) 37.985 ms 38.693 ms 37.595 ms
10 tbr2.sffca.ip.att.net (12.122.12.113) 33.806 ms 34.252 ms 34.272 ms
11 ggr2.sffca.ip.att.net (12.123.13.185) 32.995 ms 32.302 ms 32.994 ms
12 * * *
(nothing after this, but I can bring up Qwest.com just fine.)
--
Jeff Shultz