[101871] in North American Network Operators' Group

home help back first fref pref prev next nref lref last post

Re: qwest outage?

daemon@ATHENA.MIT.EDU (Daniel)
Sun Jan 20 02:49:49 2008

Date: Sun, 20 Jan 2008 00:29:56 -0700
From: Daniel <accesss801@gmail.com>
To: frnkblk@iname.com
Cc: "Jeff Shultz" <jeffshultz@wvi.com>, nanog@merit.edu
In-Reply-To: <!&!AAAAAAAAAAAuAAAAAAAAAKTyXRN5/+lGvU59a+P7CFMBAN6gY+ZG84BMpVQcAbDh1IQAAAATbSgAABAAAACdgDLWu0ytSLTnZLmoI9+/AQAAAAA=@iname.com>
Errors-To: owner-nanog@merit.edu


------=_Part_10213_13900406.1200814196614
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Yes it looks like Qwest wasn't having problems. The issues we were seeing
appear to be related to AT&T.

On Jan 20, 2008 12:08 AM, Frank Bulk <frnkblk@iname.com> wrote:

> 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.097ms
>  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.975ms
>  9  tbr1.st6wa.ip.att.net (12.122.12.157)  37.985 ms   38.693 ms   37.595ms
> 10  tbr2.sffca.ip.att.net (12.122.12.113)  33.806 ms   34.252 ms   34.272ms
> 11  ggr2.sffca.ip.att.net (12.123.13.185)  32.995 ms   32.302 ms   32.994ms
> 12  * * *
> (nothing after this, but I can bring up Qwest.com <http://qwest.com/> just
> fine.)
>
>
> --
> Jeff Shultz
>
>

------=_Part_10213_13900406.1200814196614
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

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

------=_Part_10213_13900406.1200814196614--


home help back first fref pref prev next nref lref last post