Oregon/Washington Comcast outage
Darryl Dunkin
ddunkin at netos.net
Tue May 27 20:34:00 UTC 2008
Here is the reverse view from one of my systems on residential Comcast
in the Everett/Mill Creek area (source is 76.121.150.xxx):
Tracing route to 208.74.128.9 over a maximum of 30 hops
1 <1 ms <1 ms <1 ms 192.168.254.254
2 * * * Request timed out.
3 9 ms * 9 ms
ge-1-8-ur01.everett.wa.seattle.comcast.net [68.86.177.117]
4 10 ms * 18 ms
te-9-1-ar01.burien.wa.seattle.comcast.net [68.86.96.177]
5 10 ms * 11 ms
te-9-1-ar02.burien.wa.seattle.comcast.net [68.86.96.170]
6 11 ms 9 ms 9 ms
te-8-1-ar02.seattle.wa.seattle.comcast.net [68.86.96.134]
7 11 ms 11 ms 12 ms
te-9-1-ar02.seattle.wa.seattle.comcast.net [68.86.90.210]
8 11 ms 11 ms 12 ms
COMCAST-IP-SERVICES.TenGigabitethernet1-4.ar5.SEA1.gblx.net
[64.209.111.94]
9 10 ms 11 ms 11 ms TenGigabitethernet1-4.ar5.SEA1.gblx.net
[64.209.111.93]
10 38 ms 38 ms 39 ms
Prime-Time-Ventures.so-2-1-0.ar2.SEA1.gblx.net [64.212.109.182]
11 39 ms 40 ms 38 ms 208.74.128.9
-----Original Message-----
From: Kameron Gasso [mailto:kgasso-lists at visp.net]
Sent: Tuesday, May 27, 2008 13:21
To: nanog at merit.edu; outages at isotf.org
Subject: Oregon/Washington Comcast outage
Looks like I can't reach several of Comcast's fiber/coax customers in
Oregon and Washington:
grps-edge-rtr-1#trace 75.145.64.XXX
Type escape sequence to abort.
Tracing the route to 75-145-64-XXX-Oregon.hfc.comcastbusiness.net
(75.145.64.XXX)
1 fa-6-0.grps-edge-rtr-2.visp.net (208.74.128.9) 0 msec 4 msec 0 msec
2 c1-mdfd-s40-visp.mind.net (69.9.134.65) [AS 6296] 0 msec 4 msec 0
msec
3 so-2-1-0.ar2.SEA1.gblx.net (64.212.109.181) [AS 3549] 12 msec 12
msec 12 msec
4 pos10-0-2488M.cr1.SEA1.gblx.net (67.17.71.182) [AS 3549] !H * !H
Our NOC has had several calls from folks using Comcast who weren't able
to reach us, and we then confirmed that they had no network connectivity
whatsoever...
--
Kameron Gasso | Senior Systems Administrator | visp.net
Direct: 541-955-6903 | Fax: 541-471-0821
More information about the NANOG
mailing list