[outages] Comcast issues in the Bay Area for the last 24 hours
Robbie Trencheny
me at robbiet.us
Wed May 11 12:44:42 EDT 2016
This outage is still on going. Comcast is continually pushing back the
ETOR. I was also informed that Pandora.com HQ is affected by the same issue
(they are located across the street from me). Just seeing random packet
loss. Will try to get a traceroute today.
On Monday, May 9, 2016, Michael Sinatra <michael+outages at burnttofu.net>
wrote:
> I am still seeing significant loss between my work (ESnet in Berkeley) and
> my home (Comcast Business Class in Uptown Oakland):
>
> [noc5] ~% ping manasquan.burnttofu.net
> PING manasquan.burnttofu.net (98.210.60.123): 56 data bytes
> 64 bytes from 98.210.60.123: icmp_seq=0 ttl=247 time=15.060 ms
> 64 bytes from 98.210.60.123: icmp_seq=1 ttl=247 time=12.531 ms
> 64 bytes from 98.210.60.123: icmp_seq=2 ttl=247 time=13.307 ms
> 64 bytes from 98.210.60.123: icmp_seq=3 ttl=247 time=12.680 ms
> 64 bytes from 98.210.60.123: icmp_seq=8 ttl=247 time=12.489 ms
> 64 bytes from 98.210.60.123: icmp_seq=9 ttl=247 time=12.865 ms
> 64 bytes from 98.210.60.123: icmp_seq=10 ttl=247 time=22.611 ms
> 64 bytes from 98.210.60.123: icmp_seq=11 ttl=247 time=22.628 ms
> 64 bytes from 98.210.60.123: icmp_seq=12 ttl=247 time=14.488 ms
> 64 bytes from 98.210.60.123: icmp_seq=13 ttl=247 time=22.506 ms
> 64 bytes from 98.210.60.123: icmp_seq=14 ttl=247 time=12.523 ms
> 64 bytes from 98.210.60.123: icmp_seq=16 ttl=247 time=22.536 ms
> 64 bytes from 98.210.60.123: icmp_seq=17 ttl=247 time=23.900 ms
> 64 bytes from 98.210.60.123: icmp_seq=18 ttl=247 time=12.726 ms
> 64 bytes from 98.210.60.123: icmp_seq=19 ttl=247 time=13.563 ms
> 64 bytes from 98.210.60.123: icmp_seq=20 ttl=247 time=22.434 ms
> ^C
> --- manasquan.burnttofu.net ping statistics ---
> 21 packets transmitted, 16 packets received, 23.8% packet loss
> round-trip min/avg/max/stddev = 12.489/16.803/23.900/4.681 ms
>
> ESnet has a number of perfSONAR hosts (e.g. sunn-owamp.es.net) from/to
> which you can do ping and traceroute if that helps.
>
> Similarly, I am seeing loss from UC San Francisco to my home network:
>
> [tulare:~] ms% ping manasquan.burnttofu.net
> PING manasquan.burnttofu.net (98.210.60.123): 56 data bytes
>
> --- manasquan.burnttofu.net ping statistics ---
> 26 packets transmitted, 23 packets received, 11.5% packet loss
> round-trip min/avg/max/stddev = 16.218/22.903/50.951/7.144 ms
>
> I am not seeing any loss between UCSF and a VPS I have in Los Angeles.
>
> Traceroutes from UCSF to home:
>
> traceroute to manasquan.burnttofu.net (98.210.60.123), 64 hops max, 52
> byte packets
> 1 10.131.240.1 (10.131.240.1) 3.862 ms 4.669 ms 6.025 ms
> 2 10.255.255.0 (10.255.255.0) 3.680 ms 3.583 ms 4.700 ms
> 3 3002-s251-r01.ucsf.edu (169.230.252.9) 3.489 ms 3.166 ms 5.008 ms
> 4 oak-agg4--ucsf--10ge.cenic.net (137.164.3.113) 5.633 ms 4.747 ms
> 9.053 ms
> 5 dc-svl-agg4--oak-agg4-100ge.cenic.net (137.164.46.145) 5.550 ms
> 8.902 ms 8.859 ms
> 6 xe-0-1-0.0.rtr.paix.net.internet2.edu (64.57.21.4) 6.259 ms
> xe-1-1-0.0.rtr.paix.net.internet2.edu (64.57.21.6) 5.475 ms
> xe-0-1-0.0.rtr.paix.net.internet2.edu (64.57.21.4) 5.857 ms
> 7 te-0-3-0-0-pe02.529bryant.ca.ibone.comcast.net (66.208.233.121) 6.002
> ms 6.885 ms 6.002 ms
> 8 * * *
> 9 be-7922-ar01.santaclara.ca.sfba.comcast.net (68.86.90.94) 14.099 ms
> 6.931 ms 9.776 ms
> 10 hu-0-5-0-1-sur03.oakland.ca.sfba.comcast.net (68.85.57.62) 8.405 ms
> 8.775 ms
> hu-0-5-0-0-sur03.oakland.ca.sfba.comcast.net (68.85.57.58) 10.548 ms
> 11 te-6-1-acr05.oakland.ca.sfba.comcast.net (68.85.217.178) 8.970 ms
> 8.436 ms
> te-6-0-acr05.oakland.ca.sfba.comcast.net (68.85.190.70) 8.556 ms
> 12 c-98-210-60-123.hsd1.ca.comcast.net (98.210.60.123) 26.135 ms 43.082
> ms 32.402 ms
>
> Note, hop 8, when it does respond, looks like this:
>
> 8 68.86.86.29 (68.86.86.29) 7.791 ms
> 68.86.86.145 (68.86.86.145) 7.724 ms
> 68.86.86.69 (68.86.86.69) 8.259 ms
>
> michael
>
> On 5/9/16 2:02 PM, John Neiberger via Outages wrote:
>
>> Gotcha. Well, if it happens again, let me know. I'd be glad to take a
>> look. I haven't heard of any widespread issues in that area. I was
>> hoping we could narrow it down a bit.
>>
>> Thanks,
>> John
>>
>> On Mon, May 9, 2016 at 2:52 PM, Robbie Trencheny <me at robbiet.us
>> <mailto:me at robbiet.us>> wrote:
>>
>> John,
>>
>> Just looking at my PFSense reports. No traceroutes at the moment as
>> the problem seems to have cleared up for now. I was seeing packet
>> loss as high as 15% about 35 minutes ago according to PFSense.
>>
>>
>> On Monday, May 9, 2016, John Neiberger <jneiberger at gmail.com
>> <mailto:jneiberger at gmail.com>> wrote:
>>
>> How are you verifying the packet loss? Do you have traceroutes?
>>
>> Thanks,
>> John
>>
>> On Mon, May 9, 2016 at 2:42 PM, Robbie Trencheny via Outages
>> <outages at outages.org> wrote:
>>
>> There has been a Comcast outage/degradation of services in
>> the Bay Area starting at 1403 PDT 05/08/2016. The current
>> estimated restoration time is 1707 PDT. I couldn't get any
>> details from Comcast about the issues. I've been seeing high
>> packet loss. They did tell me that I will receive a bill
>> credit.
>>
>> Robbie Trencheny (@robbie <http://twitter.com/robbie>)
>>
>> _______________________________________________
>> Outages mailing list
>> Outages at outages.org
>> https://puck.nether.net/mailman/listinfo/outages
>>
>>
>>
>>
>> --
>> Robbie Trencheny (@robbie <http://twitter.com/robbie>)
>> 925-884-3728 <tel:925-884-3728>
>> robbie.io <http://robbie.io>
>>
>>
>>
>>
>> _______________________________________________
>> Outages mailing list
>> Outages at outages.org
>> https://puck.nether.net/mailman/listinfo/outages
>>
>>
>
--
Robbie Trencheny (@robbie <http://twitter.com/robbie>)
925-884-3728
robbie.io
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/outages/attachments/20160511/b32e9697/attachment.htm>
More information about the Outages
mailing list