November 06, 2017
As far as nightmarish Mondays go, this one was a doozy for Comcast, not to mention the company's millions and millions of customers.
Around 1 p.m. EST, this is what Xfinity internet service looked like across the United States.
That's what people in the industry like to call not good. At the same time Comcast experienced its outages, a similar spike showed up for Level3, another telecom and ISP for business customers. That meant a lot of work days were suddenly doomed.
The local tech giant got on this case quickly, rest assured, and seems to have resolved the outages for the vast majority of customers.
UPDATE: our teams continue to monitor an external network issue. We apologize for the inconvenience & will provide updates as we learn more.— ComcastCares (@comcastcares) November 6, 2017
Internet issues should now be resolved for almost all customers. We apologize for the inconvenience & thank you for your patience.— ComcastCares (@comcastcares) November 6, 2017
But not before the rest of the internet got on Comcast's case. Here's a look a look at how America's feelings toward Comcast manifested on Twitter.
Am i crazy, or does the #comcastoutage seem like an attack on US internet infrastructure happening right before VA election?— Mandy B'Rabble (@Mandy_Rabble) November 6, 2017
Dear Comcast,— Glen Krisch (@glenkrisch) November 6, 2017
It's bad form to spam my inbox on the day your service has been a dumpster fire.
The United States#Comcast
Really #Comcast? Really? I had things I needed the Internet for today. WTF.— thesamuraigamer (@AkodoKusamoto) November 6, 2017
It's not entirely clear whether Level3's issues were caused by Comcast's issues or vice versa. Level3 provided a statement to TechCrunch explaining that the issue was the result of a configuration error.
On Monday, Nov. 6, our network experienced a service disruption affecting some customers with IP-based services. The disruption was caused by a configuration error. We know how important these services are to our customers. Our technicians were able to restore service within approximately 90 minutes.
Some on Twitter assigned technical blame for what happened to Comcast, citing the company's Border Gateway Protection (BGP) practices—i.e., how it handles the routing protocol used to regulate the flow information from autonomous systems on the internet.
Yes it was a Comcast's fault. They announced non-summarized BGP routes, elevating preference and congesting Level3. No fiber cuts involved.— Mikael (@xycmu) November 6, 2017
Yes it was a Comcast "thing." They announced non-summarized BGP routes, elevating preference and congesting Level3— Mikael (@xycmu) November 6, 2017
Yeah and they don't manipulate BGP either. If you believe that I have some lush rainforest for sale in Nevada.— David Dozier (@The_Dozier) May 19, 2017
My best guess is a routing/BGP issue. I'm on Comcast, and the issue seemed widespread enough to be a single yuge ISP like them or TWC— r000t (@rootworx) March 13, 2017
So, teachable moment?