Slashdot Mirror
Comcast's Xfinity Internet Service Is Down Across the US [Update] (theverge.com)
Readers share a report: Comcast's internet service, Xfinity, appears to be suffering an outage across the country. DownDetector.com shows it being down around the United States, including in large cities like San Francisco, Los Angeles, and Boston. So far, online reports don't suggest that TV service or home phones are affected. On Twitter, Comcast confirmed the outage. Adding, "Some customers are having issues with their XFINITY Internet service. We apologize & appreciate your patience while we work to fix." The company tweeted moments ago, "Our teams continue to monitor an external network issue. We apologize for the inconvenience -- will provide updates as we learn more." In another tweet, Comcast said the issue is nationwide.
Update: At 20:39 GMT on Monday, Comcast said it had resolved the issue.
Update: At 20:39 GMT on Monday, Comcast said it had resolved the issue.
I have comcast and I live in the middle of the country (over 1,000 miles from my home to the nearest ocean). I just logged in to my box at home (which is connected by comcast) from work and everything is fine.
Damn_registrars has no butt-hole. Damn_registrars has no use for a butt-hole.
I'm on non-Xfinity internet from Comcast and I am here wasting time and posting on /.
I almost feel compelled to do a "carrier lost" joke, but that would take way from pointing out the above.
I am Slashdot. Are you Slashdot as well?
It could be an outbound issue, like a DNS server. That would also explain why the outage covers multiple regions.
I am not your blowing wind, I am the lightning.
Very slow in Seattle from about 10:00 AM to noon. Back to normal now. My biggest problem with Comcast has been unannounced (but obviously scheduled) outages between midnight and 2AM. I had AT&T in Dallas for three years and never had an outage.
There's a big global DDOS attack going on right now.
Our whole shop is down and can't access Azure or TFS
http://www.digitalattackmap.com/#anim=1&color=0&country=ALL&list=0&time=17475&view=map
I noticed some websites took awhile to respond.
I changed my DNS settings on my router to openDNS and that helped.
http://saveie6.com/
Which is one of the reasons I don't exclusively use my local ISP's DNS services... Well, that and the tracking information it gives them...
I'm on Xfinity right now. Slashdot is fine. Most things are fine, but I'm having issues with specific services, including connecting to work, which I know to be working for others.
Stupid sexy Flanders.
It could be an outbound issue, like a DNS server. That would also explain why the outage covers multiple regions.
I can confirm. I changed my DNS settings and all is good again. GO use OpenDNS it is free and you can google it for home or small business use.
http://saveie6.com/
Lots of stuff was slow or would not come up, then I shifted to a Level3 DNS and removed Comcast, seems mostly OK after that.
"There is more worth loving than we have strength to love." - Brian Jay Stanley
This looks like it was actually a Level3 outage. Level3 carries a lot of the nationwide internet traffic (including traffic to/from Comcast), and the outage there caused various ripple effects (you can't get there from here, or can only get there very slowly across this (now) overloaded path).
Had to Power cycle everything and it came back.
Botched patch?
I don't use Comcast DNS I use OpenDNS.
I'm on Xfinity, I often change to Google's DNS when Comcast's goes down. I switch back because Xfinity is faster when it works.
Stupid sexy Flanders.
Better yet, run your own adblocking DNS server (on a VM if necessary) and enjoy life again!
https://pi-hole.net/
Beware of the Leopard.
Comcast is fine. Level 3 is the issue. It's been having issues since around 1PM ET. This is right around the time that Centurylink was tweeting the Level 3 is now Centurylink.
It's everyone playing this new paperclip game:
http://www.decisionproblem.com...
And crashing the internet...
( :) )
If their DNS isn't working, telling them to use "OpenDNS" won't be of much help.
https://146.112.62.105/
#DeleteFacebook
Mine is running like a top in the southeast US. I use Google's DNS, though, and have been hearing the outage is DNS-related.
Just add Google as a tertiary so it will fail over automatically. No need to switch. It won't use google unless the first two fail (unless your DNS client is set to retarded mode & round robins)
Comcast Internet service was bad, slow, and I changed my DNS servers to Google's and things are good. I'm in Colorado Springs, CO., so the problem is probably pretty wide.
In a time of universal deceit, telling the truth is a revolutionary act. George Orwell
To best implement OpenDNS, remember you either need to put in their IPv6 DNS servers or point your IPv6 entries to their IPv4 servers, or just turn off IPv6 altogether (not recommended). This is because newer operating systems prefer the IPv6 entries first.
Spectrum had a similar outage in my area (Austin) last week. I wonder if this is an outside attack on mainstream cable providers?
If this is a common issue, you might want to consider putting a caching DNS server locally on your LAN that does recursive lookups against Google's servers, but caches them locally so they're fast (after the initial, uncached lookup, of course).
It always says that if you zoom out on the map. The person writing this article must never have visited that website before.
I'm in San Jose, Ca, and I've been seeing some intermittent connectivity loss the last 1-2 weeks... But that might be a localized issue. Otherwise I'm fine. This big outage isn't affecting me. If it is DNS, then I won't see any issues. I'm running my own DNS servers. I'm also running Comcast business rather than Xfinity, so slight chance that's a factor as well.
It's not a DDOS, all the COD:WWII players are raging because the system can't serve up the most recent patches.
It could be an outbound issue, like a DNS server. That would also explain why the outage covers multiple regions.
It was only certain sites. Sites that had their own CDN's like Facebook and Steam were fine. It may have been a Level 3 issue. There were two interesting things reported via twitter:
Comcast indicating "external network issue": https://twitter.com/comcastcar...
Level 3 indicating "our network experienced a disruption affecting some IP customers due to a configuration error": https://twitter.com/Level3NOC/...
Further evidence of outage, outage statistics from DownDetector:
http://downdetector.com/status...
http://downdetector.com/status...
We'll make great pets
Yes, there are.
First, never trust a provider to own up to its own outage.
Second, use sources that check general network traffic at specified hubs.
Third, check international links the Net uses for flooding.
-- Tigger warning: This post may contain tiggers! --
Now that they have an industry lobbyist in the FCC, they're installing the internet toll booths so they can start charging you extra for Netflix.
I wish I was joking.
That's our life, the big wheel of shit. - The Fat Man, Blue Tango Salvage
They're just testing the post net neutrality internet, citizen.
The government has a defect: it's potentially democratic. Corporations have no defect: they're pure tyrannies. -Chomsky
... you log into your account and create a trouble ticket.
It must have been something you assimilated. . . .
Caching servers probably have extremely long DNS TTL values - it is one more factor in latency.
It's not frequent, though. (At least I don't hear about it often.) Last Fall there was a fairly sizable Comcast outage and the project I was working on lost contact with the segment of our team located in TX. They were all using Comcast as their ISP and it took the better part of a day for them to resume work by driving around to various coffee shops until they found one not using Comcast. (That outage hit our area, too, as well but I wasn't using Comcast.)
CUR ALLOC 20195.....5804M
Comcast-provided DNS wasn't the problem for us. We don't use Comcast DNS, we use OpenDNS. We were not getting packets routed reliably or promptly to numeric IP addresses. Not a DNS issue at all, from our location near San Francisco.
In theory, practice and theory are the same. In practice, they rarely are.
No surprise, it appears to be human error in Border Gateway Protocol information sharing. Again.
Whether deliberate or unintentional, human-introduced errors in BGP routing (typo or espionage?) have happened before, and from reports I've seen, happened again this morning. This isn't something easily bypassed, like using numeric IP addresses instead of DNS lookups. It's fundamental to the resiliency of the Internet by design. Too bad such a fundamental part of the Internet architecture is still so dependent on trust.
In theory, practice and theory are the same. In practice, they rarely are.
Great catch here! It looks very much like someone at Level 3 screwed up the BGP tables introducing a much more specific /15 CIDR where a less specific /12 was already in place, which encapsulated a huge portion of Comcasts regional traffic and re-routed it through Level 3, which could not handle the load. Bonus points if anyone has the footage of the Level 3 tech getting flogged in the Noc ;)
/* * pope1 */
I have so many comcast outages that one more is just a drop in the ocean.
Circle the wagons and fire inward. Entropy increases without bounds.