[outages] Comcast internet in Northern VA
Kenneth Padgett
kenneth at itlifesaver.com
Thu Feb 25 11:37:18 EST 2016
It's sporadic, but here's an example:
Tracing route to google-public-dns-a.google.com [8.8.8.8]
over a maximum of 30 hops:
1 2 ms 1 ms 1 ms [custIP]-static.hfc.comcastbusiness.net
2 63 ms 23 ms 29 ms 96.120.106.81
3 18 ms 15 ms 17 ms
xe-1-3-0-32767-sur01.catharpin.va.bad.comcast.net [68.85.147.5]
4 24 ms 22 ms 22 ms ae-40-0-ar01.whitemarsh.md.bad.comcast.net
[68.85.133.53]
5 63 ms 18 ms 36 ms ae-0-0-ar01.capitolhghts.md.bad.comcast.net
[68.85.67.201]
6 71 ms 55 ms 43 ms hu-0-1-0-3-cr02.ashburn.va.ibone.comcast.net
[68.86.90.229]
7 394 ms 445 ms *
he-0-14-0-1-pe04.ashburn.va.ibone.comcast.net [68.86.86.42]
8 74 ms 72 ms 65 ms as36040-2-c.ashburn.va.ibone.comcast.net
[75.149.229.86]
9 116 ms 143 ms 122 ms 209.85.242.140
10 23 ms 25 ms 26 ms 209.85.143.210
11 * 432 ms 26 ms 216.239.48.160
12 28 ms 26 ms 26 ms 216.239.48.235
13 * * * Request timed out.
14 33 ms 29 ms 25 ms google-public-dns-a.google.com [8.8.8.8]
Trace complete.
Pinging 8.8.8.8 with 32 bytes of data:
Reply from 8.8.8.8: bytes=32 time=27ms TTL=42
Reply from 8.8.8.8: bytes=32 time=151ms TTL=42
Reply from 8.8.8.8: bytes=32 time=27ms TTL=42
Reply from 8.8.8.8: bytes=32 time=29ms TTL=42
Reply from 8.8.8.8: bytes=32 time=27ms TTL=42
Reply from 8.8.8.8: bytes=32 time=26ms TTL=42
Reply from 8.8.8.8: bytes=32 time=545ms TTL=42
Reply from 8.8.8.8: bytes=32 time=30ms TTL=42
Reply from 8.8.8.8: bytes=32 time=42ms TTL=42
Reply from 8.8.8.8: bytes=32 time=26ms TTL=42
Reply from 8.8.8.8: bytes=32 time=24ms TTL=42
Reply from 8.8.8.8: bytes=32 time=25ms TTL=42
Reply from 8.8.8.8: bytes=32 time=203ms TTL=42
Reply from 8.8.8.8: bytes=32 time=386ms TTL=42
Request timed out.
Reply from 8.8.8.8: bytes=32 time=25ms TTL=42
Reply from 8.8.8.8: bytes=32 time=24ms TTL=42
Reply from 8.8.8.8: bytes=32 time=171ms TTL=42
Reply from 8.8.8.8: bytes=32 time=25ms TTL=42
Reply from 8.8.8.8: bytes=32 time=28ms TTL=42
Reply from 8.8.8.8: bytes=32 time=26ms TTL=42
Reply from 8.8.8.8: bytes=32 time=27ms TTL=42
Reply from 8.8.8.8: bytes=32 time=29ms TTL=42
Reply from 8.8.8.8: bytes=32 time=33ms TTL=42
Reply from 8.8.8.8: bytes=32 time=34ms TTL=42
Reply from 8.8.8.8: bytes=32 time=28ms TTL=42
Reply from 8.8.8.8: bytes=32 time=125ms TTL=42
Reply from 8.8.8.8: bytes=32 time=24ms TTL=42
Reply from 8.8.8.8: bytes=32 time=28ms TTL=42
Request timed out.
Reply from 8.8.8.8: bytes=32 time=25ms TTL=42
Reply from 8.8.8.8: bytes=32 time=29ms TTL=42
Reply from 8.8.8.8: bytes=32 time=31ms TTL=42
Reply from 8.8.8.8: bytes=32 time=25ms TTL=42
Reply from 8.8.8.8: bytes=32 time=23ms TTL=42
Reply from 8.8.8.8: bytes=32 time=27ms TTL=42
Reply from 8.8.8.8: bytes=32 time=25ms TTL=42
Reply from 8.8.8.8: bytes=32 time=25ms TTL=42
Reply from 8.8.8.8: bytes=32 time=26ms TTL=42
Reply from 8.8.8.8: bytes=32 time=42ms TTL=42
Reply from 8.8.8.8: bytes=32 time=25ms TTL=42
Reply from 8.8.8.8: bytes=32 time=24ms TTL=42
Reply from 8.8.8.8: bytes=32 time=27ms TTL=42
Reply from 8.8.8.8: bytes=32 time=26ms TTL=42
Reply from 8.8.8.8: bytes=32 time=32ms TTL=42
Reply from 8.8.8.8: bytes=32 time=25ms TTL=42
Request timed out.
Reply from 8.8.8.8: bytes=32 time=42ms TTL=42
Reply from 8.8.8.8: bytes=32 time=26ms TTL=42
Reply from 8.8.8.8: bytes=32 time=24ms TTL=42
Reply from 8.8.8.8: bytes=32 time=409ms TTL=42
Reply from 8.8.8.8: bytes=32 time=31ms TTL=42
On Thu, Feb 25, 2016 at 11:20 AM, John Neiberger <jneiberger at gmail.com>
wrote:
> Can you provide some traceroutes?
>
> Thanks,
> John
>
> On Thu, Feb 25, 2016 at 9:16 AM, Kenneth Padgett via Outages <
> outages at outages.org> wrote:
>
>> Anyone else seeing packet loss and connectivity issues on Comcast in
>> NoVA? We have several clients on Comcast Business with 1000ms+ pings and
>> dropped packets.
>>
>> _______________________________________________
>> Outages mailing list
>> Outages at outages.org
>> https://puck.nether.net/mailman/listinfo/outages
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/outages/attachments/20160225/2d588980/attachment.htm>
More information about the Outages
mailing list