Michael Acosta wrote:
As a Comcast customer in the NW, I see the same thing outbound.
Traceroute to some sites die in glbx, and other sites work via other
transit providers.
Looks like whatever the SNAFU between Comcast and GLBX was, it's been
resolved for some time now... :)
Cheers,
--
Kameron Gasso | Senior Systems Administrator | visp.net
Direct: 541-955-6903 | Fax: 541-471-0821
On Tue, May 27, 2008 at 1:21 PM, Kameron Gasso <[EMAIL PROTECTED]> wrote:
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
