Xfinity outage leaves tens of thousands in the Bay Area without internet
sfchronicle.com
sfchronicle.com
My other options are DSL, so it's going to max out at 20Mbps or so.
I do have roof access, so I guess I could also see about MonkeyBrains.
All that said, during the outage, I just tethered to my iPhone on an AT&T unlimited plan, and was able to stream full quality video to my laptop. I think I speed tested it to about 80Mbps.
I suppose Sonic is also an option that I would love to entertain, but they're just reselling AT&T DSL here.
If only we had municipal broadband, but the corps own the infrastructure and have long contracts with the cities :(
And as far as alternatives, in the Southbay it's very limited. I looked into this when I moved earlier this year and even Sonic only had DSL available where I live now. AT&T didn't even offer gigabit, and I'm not exactly in a bad spot other than that it's a suburb area (but I'm extremely close to a HQ for a FAANG).
Sonic fiber is available by building, not neighborhood.
https://arstechnica.com/uncategorized/2007/11/eff-study-reve...
https://www.eff.org/deeplinks/2019/06/fcc-siding-landlords-a...
ISP monopolies are a huge problem and I find smaller ISPs tend to have better services. My previous apartment has a dedicated support team from a small ISP, and the tier 1 rep on the support line was capable of explaining the building's network topology and how they do natting.
In contrast, AT&T DSL FTTN (Fiber to the Node) and Sonic DSL (not resold) have been rock solid. I am using AT&T for both home and business now and can't remember the last time there was an outage or issues with the modem. For me, a stable connection at 50mbps is preferable to unstable 1gig.
I would rather support Sonic, but they don't have fiber in my area and I had a bad experience with their resold AT&T FTTN service that was beyond their control. Their straight DSL product is solid, as long as you are close to the central office and can get a good speed.
So for the second Comcast outage in a row, my first line of confirmation on the outage (as opposed to damaged house wiring or hardware or something) was ham radio. I turned on the HT, hit scan, and the first carrier found was a conversation about the outage, a couple cities north. That's always helpful just to get oriented. But funny because there ought to be a better information fallback now that internet service is so crucial. I couldn't even log into the Xfinity app on my phone.
Also, for the first time, I realized that texts using Google messenger's enhanced chat features may not go through at all in this situation, as one would expect normal texts to do. This was worrying because...do I need to disable this feature every time I go hiking now, if I want my texts to send?
Y'all must have some excellent broadband in California on average, wide-area Comcast outages are pretty common where I live, they certainly don't make the news.
Edit: Guess I spoke too soon, people are indeed reporting outages across the country.
I can’t help but wonder if this is the result of a cyber attack on Comcast’s infra.
Obviously don’t start getting angry, but if there’s a point of frustration please pass it along.
Tier one CS is there to confirm where a fault lies, teach you basic troubleshooting, and send out techs. If the issue isn't on your premise the best we can do is check that outage for an ETR, though most of the time the crews won't establish one because that creates a deadline for them to meet.
The human being at the other end of the phone is not your therapist or the object of your frustrations. It's the same with waitstaff. They have their own problems; they aren't their to be kicked when you are frustrated.
> their CS agent actually suggested that although they are working from home they should go use a public xfinity wifi spot
That's a reasonable workaround, given that their home Internet is unavailable.
I spent 6 and a half years working for what was once the largest privately owned prime contractor that did work for Comcast.
I'll measure my empathy based on the fact that their continuing to agree to work that job is in fact enabling Comcast's abusive/neglectful behaviors towards customers, contractors, hell even non-customers can get caught in the crossfire.
I mean FFS, I made a point to live in areas so that I don't have to get Comcast and they -still- found a way to make my life a living hell a couple years ago. We're talking kafka-esque levels of "You can't speak to a human that will do anything but tell you to fill out this form with information you legally should not have to give." (Yes, I tried filling out the form omitting the information that was not legally required. They rejected it and then asked for even MORE.)
Sadly, the only thing that -did- work in stopping the harassment was to harass back. I would politely argue, ask them to consider a career that wasn't so soul-sucking, and point out at the start and end of every call how much time I had spent on the phone with Comcast, and the resulting number of dollars it was costing them to not just leave me the F alone.
I probably can never get Comcast service at this point, but at least they stopped violating my FDCPA rights and messing with my credit...
Wow. I've seen people say that you shouldn't work for people like NSO, or national security agencies, or Facebook, but you should fall on your sword for Comcast customer service problems? There aren't many jobs left that meet your standards. I think we are taking rationalization way too far.
Yeah, fuck that shit.
At my office, also nearby, the outage was shorter; it's on a static IP.
Probably unrelated.
Which is something that's nearly impossible across most of the US, given the monopoly (or, if you are lucky, duopoly) in ISPs.
https://media.ccc.de/v/32c3-7133-beyond_your_cable_modem
A email I sent just weeks ago..
________________________
>> ------- Forwarded Message -------- >> Subject: Serious DOCSIS maintenance network issue >> Date: Sat, 23 Oct 2021 21:09:16 -0700 >> From: Admin <admin@badmodems.com> >> To: xxxx@cablelabs.com, xxxx@cablelabs.com, xxx@cablelabs.com, xxx@cablelabs.com, xxx@cablelabs.com >> >> >> >> Hi all.. >> >> You guys hate me :( First it was Puma and the badmodems.com list and now this.. >> >> I am sorry to directly email you. No need to respond. Its OK, I understand its a legal thing. I wont email again. Sorry for this hassle. Sorry for a long read. >> >> There appears to be a very serious gap in your security best practices and policies that could result in a very widespread serious incident that could effect all DOCSIS systems worldwide and result in a worldwide incident. >> >> This appears to be from MSOs deploying horrendously bad security on the maintenance network. >> >> The issues are being discussed publicly. This thread begins with discussion of firmware and then turns to the maintenance network which appears to have little if any security implemented possibly because there is no modern published best practices for the maintenance network beyond something from the 1990's. https://www.dslreports.com/forum/r31122204-SB6190-Puma6-TCP-... >> >> The maintenance network, which controls all the devices on a DOCSIS network, is susceptible to attack. In fact its nearly criminally negligent in its lack of security and appears to be based on 1990's security protocols of mostly security thru obscurity. .. A subscriber on the LAN side can determine his address on the maintenance network and can ping ANY CPE on the network as long as they are on the same ISP. The CPE are not walled off from each other in any way. This could result in a VAST compromise of the entire MSO network nationwide from a 0-day worm that self spreads via the wide open maintenance network connecting all devices. . . ALL susceptible devices on your network, 10's of millions, could be taken over in hours with a self spreading worm with a nearly impossible task of clean up and maybe a week of complete ISP downtime. This would also result in the largest loss of subscribers in history for cable as people flee to DSL and 5G that day trying to get internet. You would need new firmware for every device that addresses the issue, and getting new firmware will take weeks. All the susceptible CPE might be bricked with no hope of recovery once taken over. The current security practices are inadequacy. The news coverage would be devastating. Each modem/router could attack the subscriber side and scrape data and files. On the ISP side it would lock out all maintenance access and recovery of the devices, and the whole network, nearly impossible. It would setup a serious botnet - possibly the largest ever created when combined with the other top world wide ISPs. It might even result in a Ransom ware attack on a massive scale with all the CPE locked out from the ISP. A silent malware could spread stealthy and then sit on CPE and attack the subscribers quietly by doing fake DNS and even MiM attacks. This could already be the case. A botnet of CPE would be incredibly powerful >> >> This wide open gap appears to exist in most ISPs. So it is a CableLabs lack of proper security vision to keep up with modern threats by doing best practices for the maintenance network seems to be the main issue. 10G offers micronets and SDN containment of LAN devices,,, yet the ISP has nothing like it to protect its own network and its subscribers. >> >> Each ISP will need to do a 3rd party security audit and pentest of all the MSO's maintenance networks and secure them. The kinda emergency level, possible fairly easy temp fix is simple. Isolate each piece of CPE. Right now all CPE can see each other and spread worms. Simply doing a config change could wall off each device with NO downside. This might be able to be implemented maybe in a day. This alone would reduce the issue to nearly zero. BLocking access to the maintenance network from the subscriber is also key and most likely easy. MSOs REALLY need to do this and because these discussions are going on now, badguys could be reading, so RIGHT NOW is the time to secure MSO networks BEFORE a incident occurs. >> >> There may be simple quick solutions to avoid this doomsday scenario.. Make sure you read up to the current postings. https://www.dslreports.com/forum/r31122204-SB6190-Puma6-TCP-... >> >> I will be following up to be sure you got this message. >> >> You can contact me for any further details or respond to this email. >> >> I am the guy who found the Puma issue. So you guys know I can be persistent and noisy. I would really like to hear that CableLabs is going to pursue a whole new approach to device security on the maintenance network including RAPID firmware deployment. EVERYBODY wins.. >> >> Sorry for blasting the email. Sorry to start your monday kinda ruff. Think of it as a cool new feature. >> >> I have contacted all the top 10 MSOs and sent reports to the security teams. They are the guys who made this mess, but, they need a good best practice to follow and that does not seem to be there. >> >> Gone are the days of junk boxes with poor CPUs. MSOs are dropping POWERFUL devices with lots of RAM and Flash. They run Microsoft or Linux. They are connected to a massive bandwidth pipe. It looks possible to take over whole ISPs. These are prime targets no one has noticed yet apparently. Gone are the days of old.. These are high value targets and a bot net of incredible scale... Its time for a top down new approach to firmware and device security.. >> >> Of course none of my doomsday scenarios most likely will ever happen.. And most likely everything is fine.. BUT MSO's can't just keep these maintenance networks so 1990s sloppy. >> >> IMHO.. >> >> xxxxxx xxxxxxxxxx >> >> >> >
This is a bizarrely overdramatic response to one provider being down for an hour, and I can't imagine why the author felt the need to include it, other than to further dramatize their own dramatization of a rather innocuous situation.
That's exactly why they included it. It's the internet equivalent of when journalists go out and interview random pedestrians to get their reactions/commentary to some event.
They want a soundbite that will stick in your mind after reading/viewing the news segment, regardless of how useful the commentary really is.
As long as most news is for-profit, and therefore their incentives lie primarily in maximizing engagement/ratings/ad revenue, they will continue to optimize for those things with different iterations of what is essentially clickbait.
Even here on the relatively intellectual HN, I regularly see articles posted that have very clickbaity and misleading titles.
Next he's going to talk about keeping a horse in a stable out back in case the gas station runs out of fuel.
(Of course if internet goes down my phone has tons of spotify tracks downloaded onto it, so I'm sure I'll cope)
What about being able to work?