[outages] Comcast - East Coast issues ?

Micah Brandon brandon at netsville.com
Fri Jun 22 14:41:42 EDT 2012


We've also received a call from customer on Comcast that can't reach us.  We come in from XO and our trace ends at the same point.

traceroute to www.g.comcast.com (69.241.45.20), 64 hops max, 40 byte packets
 1  roc-core3 (69.55.64.3)  0.537 ms  0.337 ms  0.308 ms
 2  roc-edge2 (69.55.64.2)  0.522 ms  0.553 ms  0.377 ms
 3  roc-edge4 (69.55.64.4)  0.475 ms  0.415 ms  0.441 ms
 4  nysys-gw (69.55.69.36)  1.980 ms  1.905 ms  2.286 ms
 5  66.238.116.197.ptr.us.xo.net (66.238.116.197)  8.049 ms  7.548 ms  9.537 ms
 6  216.156.8.13.ptr.us.xo.net (216.156.8.13)  8.689 ms  7.299 ms  6.940 ms
 7  vb1111.rar3.chicago-il.us.xo.net (216.156.0.53)  20.504 ms  22.675 ms  19.280 ms
 8  * 207.88.14.194.ptr.us.xo.net (207.88.14.194)  25.729 ms  17.183 ms
 9  206.111.2.206.ptr.us.xo.net (206.111.2.206)  17.062 ms  18.956 ms  16.786 ms
10  64.86.79.1 (64.86.79.1)  16.639 ms  23.481 ms  21.564 ms
11  173.167.59.161 (173.167.59.161)  27.794 ms
    173.167.59.153 (173.167.59.153)  27.395 ms  34.985 ms
12  * * *


On 06/22/2012 02:05 PM, Andy Ringsmuth wrote:
> Traceroute from Lincoln, Nebraska:
> 
> (My connection is via Unite Private Networks fiber)
> 
> Last login: Thu Jun 21 20:52:10 on console
> 618-Andy-Ringsmuth:~ andyring$ traceroute comcast.com
> traceroute: Warning: comcast.com has multiple addresses; using 69.241.45.4
> traceroute to comcast.com (69.241.45.4), 64 hops max, 52 byte packets
>  1  192.168.1.2 (192.168.1.2)  0.494 ms  0.209 ms  0.219 ms
>  2  ge1/2.224_ne_lnk_off_7606.upnllc.com (208.82.104.193)  0.662 ms  0.566 ms  0.582 ms
>  3  65.125.9.33 (65.125.9.33)  1.995 ms  2.543 ms  2.488 ms
>  4  chp-brdr-04.inet.qwest.net (67.14.8.234)  19.505 ms  19.259 ms  19.527 ms
>  5  63.146.26.14 (63.146.26.14)  19.556 ms  19.500 ms  19.514 ms
>  6  64.86.79.1 (64.86.79.1)  19.617 ms *  19.643 ms
>  7  173.167.59.149 (173.167.59.149)  26.930 ms
>     173.167.59.165 (173.167.59.165)  27.209 ms
>     173.167.59.169 (173.167.59.169)  31.145 ms
>  8  * * *
>  9  * * *
> 10  * * *
> 
> Won't pull up in a Web browser either.
> 
> ---
> Andy Ringsmuth
> (402) 304-0083
> andyring at inebraska.com
> 
> On Jun 22, 2012, at 12:58 PM, John Neiberger wrote:
> 
>> Yes, please post a traceroute.
>>
>> Thanks,
>> John
>>
>> On Fri, Jun 22, 2012 at 11:54 AM, Brandon Applegate <brandon at burn.net> wrote:
>>> Hello,
>>>
>>> Having multiple customers call in about reachability - common thread is
>>> their side users are all on Comcast.  Not to mention the fact that we can't
>>> even hit www.comcast.com from our network currently.
>>>
>>> We have Level3 (Cincinnati) and Qwest (Chicago).  Traceroutes from us
>>> outbound seem to prefer Qwest and then die in Comcast.
>>>
>>> I can post traceroutes if need be - just wanted to see if anyone knew
>>> anything before I call my upstreams and wade through phone tree hell.
>>>
>>> --
>>> Brandon Applegate - CCIE 10273
>>> PGP Key fingerprint:
>>> 8779 B023 7637 CEC8 C5C6 4052 664D 7E08 3CBB 1739
>>> "SH1-0151.  This is the serial number, of our orbital gun."
>>>
>>> _______________________________________________
>>> Outages mailing list
>>> Outages at outages.org
>>> https://puck.nether.net/mailman/listinfo/outages
>>
>> _______________________________________________
>> Outages mailing list
>> Outages at outages.org
>> https://puck.nether.net/mailman/listinfo/outages
> 
> 
> _______________________________________________
> Outages mailing list
> Outages at outages.org
> https://puck.nether.net/mailman/listinfo/outages

-- 
micah brandon
netsville.com
p585.232.5670



More information about the Outages mailing list