Live data from Hacker News

Level 3 Global Outage

puck.nether.net

141–150 of 393 posts

Re: Level 3 Global Outage

#141
post #5
post #4

I'm having issues reaching IP addresses unrelated to Cloudflare. Based on some traceroutes, it seems AS174 (Cogent) and AS3356 (Level 3) are experiencing major outages.

Is there any one place that would be a good first place to go to check on outages like this? It would be really cool and useful to have an "public Internet health monitoring center"... this could be a foundation that gets some financing from industry that maintains a global internet health monitoring infrastructure and a central site at which all the major players announce outages. It would be pretty cheap and have a…

You just imagined the first target in an attack. Might as well just call it honeypotnumber1.

Re: Level 3 Global Outage

#143
Seems like "the internet" works again here in Norway. I've been limited to local sites all day.

Hacker news has been off for several hours for me.

Whatever it was it must have been nasty.

Re: Level 3 Global Outage

#145
post #138

Earlier quoted context omitted.

So it's not a BGP blackhole incident then?

Not all BGP blackholes are the same. The AS7007 incident from over twenty years ago is an entirely different cause, and thus unrelated.

What I take from that: It is a BGP blackhole incident.

Re: Level 3 Global Outage

#146
post #22

DDG, down detector are all very slow. Both are on cloudflare. Fastly, HN, Reddit too. Only Google domains are loading here.

From where I am (mid-altantic US) Google site are completely down (google.com, youtube)

Re: Level 3 Global Outage

#147
post #91
post #83

Earlier quoted context omitted.

HN working for me from the UK on BT, but traceroute showing lots of different bouncing around and a lot of different hops in the US 7 166-49-209-132.gia.bt.net (166.49.209.132) 9.877 ms 8.929 ms 166-49-209-131.gia.bt.net (166.49.209.131) 8.975 ms 8 166-49-209-131.gia.bt.net (166.49.209.131) 8.645 ms 10.323 ms 10.434 ms 9 be12497.ccr41.par01.atlas.cogentco.com (154.54.56.130) 95.018 ms be3487.ccr41.lon13.atlas.cogentc…

Guessing the traceroute looks a bit messy because of multiple paths being available. You can use `-q 1` to send a single traceroute probe/query instead of the default 3, it might make your traceroute look a little cleaner.

I don't normally see multi paths for a given IP, but that aside it's bouncing through far more than I'd expect. That said, it's rare I look at traceroutes across the continental U.S, maybe that many layer 3 hops are normal, maybe routes change constantly.

HN has dropped off completely from work - I see the route advertised from Level 3 (3356 21581 21581) and from Telia and onto Cogent (1299 174 21581 21581). Telia is longer, so traffic goes into to Level3 at Docklands via our 20G peer to London15, but seems to get no further.

Heading to Tata in India, route out is via same peer to level3, then onto the London, Marseile, and then peers with Tata in Marseille, working fine.

My gut feeling is a core problem in Level3's continental US network rather than something more global.

Re: Level 3 Global Outage

#149
post #115

I hope these kind of “ipv4” only outages encourages more and more websites to upgrade to ipv6. #OutageBenefit ;)

Sadly, in my experience, ipv4 is generally more reliable than ipv6 still. Set up two hosts, host A and host B in two different data centers. Make them send HTTP requests to each other over ipv4 and over ipv6. You'll see that latency spikes, packet loss is more frequent over ipv6.

Why is that?

Re: Level 3 Global Outage

#150
post #104

India just lost to Russia in the final of the firstever online chess olympiad, probably due to connection issues of two of its players. I wonder if it's related to this incident and if the organizers are aware. Edit: the organizers are aware, and Russia and India have now been declared joint winner.

That's fascinating. But I wonder, why don't they start over, or continue where they left off, once the internet is back?
Post reply on HN