Cloudflare was down • Hacker News Board

Re: Cloudflare was down

#281

Post by neurostimulant » Fri, Jul 17, 2020, 9:52 PM UTC

soup10 wrote: post #223

alex_young wrote: post #87

Yesterday I noticed most of their lava lamps are out (which generate random bits). Perhaps these are a critical component. https://photos.app.goo.gl/g6eR8V2PSY3EVjCLA

Good guy cloudflare giving programmers an early weekend.

But overtime for their own programmers :)

Re: Cloudflare was down

#282

Post by ricopags » Fri, Jul 17, 2020, 9:52 PM UTC

awinder wrote: post #162

NextDNS got taken out by this, id been really happy with it up until now. And unfortunately “dns service went down” has a wide enough blast radius at home now that it’s a real pain.

How did you verify that? I determined the issue was with Cloudflare's DNS by toggling on NextDNS, which worked and continues to.

Re: Cloudflare was down

#283

Post by dijit » Fri, Jul 17, 2020, 9:52 PM UTC

AdamGibbins wrote: post #262

blisseyGo wrote: post #252

Earlier quoted context omitted.

Out of curiosity, done HN use any CDN or other way of DDOS protection? dang?

It's hosted on AWS, you don't need DDoS protection, just a big wallet.

Thats not even slightly true.

Their IP belongs to AS21581; which is registered with a company called 'M5 Computer hosting' out of west-coast USA.

m5hosting.com

The last hop is Santa Barbera.

Definitely does not fall in the AWS ranges.

Re: Cloudflare was down

#284

Post by brycewray » Fri, Jul 17, 2020, 9:52 PM UTC

Vercel also appears to be dropping out and coming back in intermittently over the last 30 minutes or so. Not aware they're using Cloudflare, although they do mention using AWS.

Re: Cloudflare was down

#285

Post by juancampa » Fri, Jul 17, 2020, 9:52 PM UTC

remmargorp64 wrote: post #242

rozab wrote: post #136

We can't keep going on like this. The vulnerability of centralised internet infrastructure is a huge problem for everyone. Somebody, somewhere, really ought to sort it all out

Sounds like a problem for... us!

If only there was some website full of computerphiles...

Re: Cloudflare was down

#286

Post by zubiaur » Fri, Jul 17, 2020, 9:52 PM UTC

LeoPanthera wrote: post #90

I'm having real problems with DNS, is this Cloudflare too? They say "All Systems Operational", so maybe not? Half the damn internet is not currently resolving.

Yes, same here. Changed DNSs to level 3, all better now.

Re: Cloudflare was down

#287

Post by xen2xen1 » Fri, Jul 17, 2020, 9:52 PM UTC

Remind me to check and see that I have 8.8.8.8 and 1.1.1.1 on my networks, not just one or the other..

Re: Cloudflare was down

#288

Post by kube-system » Fri, Jul 17, 2020, 9:53 PM UTC

Of course, I read this after I spend an hour debugging some strange DNS issues.

Re: Cloudflare was down

#289

Post by spenczar5 » Fri, Jul 17, 2020, 9:53 PM UTC

hpfr wrote: post #247

remmargorp64 wrote: post #193

Earlier quoted context omitted.

I consider DNS and the way how top level domains are handled to be one of the weakest parts of our current Internet design. We REALLY need a truly decentralized, distributed DNS system that is not owned by private entities.

https://handshake.org is pretty interesting.

The "decentralized internet" folks always talk a lot about fighting corporate control. I think they should spend more time talking about resiliency and blast-radius reduction.

Re: Cloudflare was down

#290

Post by cm2187 » Fri, Jul 17, 2020, 9:53 PM UTC

Figs wrote: post #276

cm2187 wrote: post #117

Earlier quoted context omitted.

A sudden disruption on a large number of services for everybody at once doesn't look like a DNS problem to me, with all the caching in DNS. It would fail progressively and inconsistently.

DNS absolutely was an issue. I changed DNS manually from Cloudflare's 1.0.0.1 (which is what DHCP was giving me) to 8.8.8.8 (Google) and most things I'm trying to reach work. There may be other failures going on as well, but 1.0.0.1 was completely unreachable.

I don't use cloudflare DNS but google DNS and got the same problems thant everyone else

The problem seems to have been resolved now, you might have made the change when they fixed it.