astrabal service logo
 story category
Level 3 Issues Cause Outage for Comcast, Other ISPs

Comcast and several other major ISPs suffered significant, nationwide outages earlier today. Down Detector indicated that Comcast customers in major cities from New York to Seattle experienced high latency and the inability to access much of the internet for a significant chunk of Monday. Comcast confirmed the issues on Twitter but has yet to offer an explanation. Other ISPs like RCN , but blamed the connectivity issue on a problem with Level 3's backbone.

Level 3, which was only just acquired by CenturyLink, confirmed the origin was a "configuration issue."

"On Monday, Nov. 6, our network experienced a service disruption affecting some customers with IP-based services, Level 3 said in a statement. "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."

»

»

Most recommended from 32 comments



TIGERON
join:2008-03-11
Boston, MA

TIGERON

Member

Get ready....

CenturyLink has just taken over. This is just the beginning of network connectivity issues. A bud once described dealing with CTL as a bunch of "assholes".

Simba7
I Void Warranties
join:2003-03-24
Billings, MT

Simba7

Member

CenturyLink

Screwing up one network at a time. Almost as bad as Charter.

Charter "Hey, we screwed up the network *AND* we're charging more for our services and really gouging our customers!"

CenturyLink "Hold my beer"
Dog2puppy
join:2017-09-27
Union City, OH

Dog2puppy

Member

Only the start...

This is just the start of issues we’re going to have with Level3 being acquired by CenturyLink.
Beck38
join:2014-05-12
Centralia, WA

Beck38

Member

Tracking Probs Across US for 3+Days

I've been tracking problems across the US starting is SF to DC to ATL to DAL to SEA over the weekend, as I transmit high volumes of data to cloud services located in the Tysons Corner area of Virginia, so across the country from Seattle. Just because L3 has the probs it affects all the other major transmission companies and their throughput as well. I've been jumping from one route to another all day today trying to get my data stream back approching 'normal' speeds almost to no avail.

I think there are more problems out there in transmission/router plants than simply L3/Centurylink, after spending close to 40 years constructing and operating transcontinental and transoceanic fiber systems, now retired, I see most operators simply not paying attention to their systems, outsourcing maintenance and engineering to service companies (and I worked for the myself) and mostly take their paycheck and run. Same as what we see with programming 'services' that allow not just the hack of the month, but hack of the day and even hour.

I'm sure they're good professional folks out there but I think it's getting few and far between from what I see.
gtb
join:2016-05-16
Sunnyvale, CA

gtb

Member

Route leak

Wired has posted an analysis of the outage: »wired.com/story/how- ··· -the-us/ which concludes that this was a route leak (happened before, likely will happen again).

camper
just visiting this planet
Premium Member
join:2010-03-21
Bethel, CT
·Comcast XFINITY

camper

Premium Member

Log file showed issues...

 

First log entry was at 12:51:06, high latency but still able to get the data through.

At 12:53:35 data stopped going through.

The issue continued off and on until just after 14:21:20, when it appeared to be resolved.

I haven't seen any issues since then.

(edit: times are EST)
Sliffer21
join:2016-07-06
Dunbar, WV

Sliffer21

Member

Level 3 Outage

Comes just as they announced Century Link closing the acquisition, most likely caused by some sort of post merger process to bind the two to a more uniform service.
pooker314
join:2005-04-12
Brush Prairie, WA

pooker314

Member

trouble in PDX area

Yep, we had troubles in SW Washington. Ooma phone service was next to useless (very choppy), audio streaming basically didn't work, and many websites weren't accessible at all.

How about ..