
Comcast appears to be experiencing an outage in the south SF Bay Area. Not sure how wide spread it is but confirmed on the automated customer service line Grant Sent from my iPhone

Looks like its the entire bay area per twitter and up to Sac per http://downdetector.com/status/comcast-xfinity/map/ Automated phone service says an ETR of 3am -Grant On Wed, Nov 30, 2016 at 12:28 AM, Grant Ridder <shortdudey123@gmail.com> wrote:
Comcast appears to be experiencing an outage in the south SF Bay Area. Not sure how wide spread it is but confirmed on the automated customer service line
Grant
Sent from my iPhone

No connectivity issues or disturbances tonight on my residential Comcast cable connection in San Francisco (near Twin Peaks). So it's not a total outage for the area. Traceroute to 8.8.8.8: 3 te-0-7-0-1-sur04.sf19th.ca.sfba.comcast.net (68.85.103.125) 9.898 ms 9.915 ms 10.304 ms 4 be-311-ar01.hayward.ca.sfba.comcast.net (162.151.79.85) 10.701 ms 10.697 ms 11.078 ms 5 hu-0-19-0-0-ar01.santaclara.ca.sfba.comcast.net (68.85.154.253) 13.159 ms hu-0-19-0-1-ar01.santaclara.ca.sfba.comcast.net (68.85.57.177) 13.251 ms 13.207 ms 6 be-33651-cr01.sunnyvale.ca.ibone.comcast.net (68.86.90.93) 13.066 ms 10.560 ms 12.579 ms 7 hu-0-11-0-0-pe02.529bryant.ca.ibone.comcast.net (68.86.86.70) 13.655 ms hu-0-14-0-1-pe02.529bryant.ca.ibone.comcast.net (68.86.89.230) 11.114 ms hu-0-12-0-1-pe02.529bryant.ca.ibone.comcast.net (68.86.87.14) 11.049 ms 8 as15169-3-c.529bryant.ca.ibone.comcast.net (23.30.206.102) 11.083 ms 10.895 ms 66.208.228.70 (66.208.228.70) 11.273 ms 9 108.170.242.241 (108.170.242.241) 12.147 ms 108.170.242.81 (108.170.242.81) 12.072 ms 108.170.242.241 (108.170.242.241) 12.081 ms 10 216.239.49.121 (216.239.49.121) 12.132 ms 216.239.56.121 (216.239.56.121) 13.438 ms 216.239.49.103 (216.239.49.103) 13.449 ms 11 google-public-dns-a.google.com (8.8.8.8) 12.914 ms 12.935 ms 12.873 ms On Wed, 30 Nov 2016, Grant Ridder via Outages wrote:
Looks like its the entire bay area per twitter and up to Sac per http://downdetector.com/status/comcast-xfinity/map/ Automated phone service says an ETR of 3am
-Grant
On Wed, Nov 30, 2016 at 12:28 AM, Grant Ridder <shortdudey123@gmail.com> wrote:
Comcast appears to be experiencing an outage in the south SF Bay Area. Not sure how wide spread it is but confirmed on the automated customer service line
Grant
Sent from my iPhone
--- Jesse <j@lumiere.net>

This is the 3rd time in the past couple months (at most) where Comcast has done this type of maintenance in Silicon Valley. Important detail: this is cable network/node maintenance, not IP network. Every time this work has been done in the past few months, it manifests in mostly the same way. Per discussions with other list members as well as with some folks in Comcast Network Maintenance Engineering, what I see for my specific area is not necessarily what's going on a city or two over (or sometimes even within the same city!). That said, this is a "general overview" of what I've personally witnessed (with months of logs to back it up): They appear to be trying to introduce additional downstream channels. Where I live (Old Mountain View), the freqs were 735/741/747/753MHz. During the last maintenance (2-3 weeks ago) they got this working (in contrast the maintenance 3-4 weeks prior to that, which was a failure and had to be rolled back), but for Mountain View there was a period of over 24 hours of 25-30% packet loss when reaching the CMTS. Tonight's work is now a horse of a different colour: they appear to have pulled 735-753MHz and instead introduced 657MHz (?!?). So right now I've 21 bonded DS channels, which is a bit odd (pun intended), with a very elevated rate of DS correctables and occasional batches of uncorrectables. The latter is likely due to technicians still working on things (it's 02:53 PST), but the former, well... I'll just say it: There are network issues here in my area, particularly an abnormally high rate of DS correctables, i.e. RS/FEC is being applied heavily, where the pre-FEC BER rate is no where near what it was prior to July 2016. I've been in contact with Network Maintenance Engineering techs and supervisors out of Menlo Park for months about this, and met in person/on foot in the field several times. Every time they do the above work, though, the issue is exacerbated -- in almost all cases DS SNR gets substantially worse (2-3dB at times), as does DS power. It's often a specific frequency range that suffers this way. What makes this extra weird is that for a period of almost 48 hours on 9/24, the issues I describe in this paragraph *completely disappeared*, then reappeared out of no where; this leaves me with the impression there is some interconnect wiring, or hub, or *something* on the network between here and Santa Clara that got jostled in such a way where the issue went away. It really smells interference seepage. I can't speak for others, but all this is work is extra annoying for me, because every time they add new frequencies I have a boatload of scripts and DBs to alter/modify/manipulate as a result. It takes me a couple hours, and in a couple occasions right when I got everything updated, they'd make another change and I'd have to do the same again. Like for tonight, I'm actually afraid to change any of my code because for all I know in 2 hours they might change it all again. I'm fine with maintenance, but this feels much like someone "playing around in production", rather than having a plan of action and proper rollback procedure. It's more like "eh, it mostly kinda works, I guess we'll leave it like that for now", rinse lather repeat every 2-4 weeks. -- | Jeremy Chadwick jdc@koitsu.org | | UNIX Systems Administrator http://jdc.koitsu.org/ | | Making life hard for others since 1977. PGP 4BD6C0CB | On Wed, Nov 30, 2016 at 12:28:54AM -0800, Grant Ridder via Outages wrote:
Comcast appears to be experiencing an outage in the south SF Bay Area. Not sure how wide spread it is but confirmed on the automated customer service line
Grant
Sent from my iPhone _______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages

Sure looks like ingress leakage. On 11/30/16 2:58 AM, Jeremy Chadwick via Outages wrote:
They appear to be trying to introduce additional downstream channels. Where I live (Old Mountain View), the freqs were 735/741/747/753MHz.
Right smack in the middle of the LTE cellular downlink. Lots of cell sites shared on the same poles as cable plant in the Bay Area.
Tonight's work is now a horse of a different colour: they appear to have pulled 735-753MHz and instead introduced 657MHz (?!?).
KBCW channel 44. -- Jay Hennigan - CCIE #7880 - Network Engineering - jay@impulse.net Impulse Internet Service - http://www.impulse.net/ Your local telephone and internet company - 805 884-6323 - WB6RDV
participants (4)
-
Grant Ridder
-
Jay Hennigan
-
Jeremy Chadwick
-
Jesse