Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Cloudflare was down

cloudflarestatus.com

Post reply on HN
Print view View original

321–330 of 499 posts

Re: Cloudflare was down

#321

Post by cuu508 »

cm2187 wrote: post #290
Figs wrote: post #276

Earlier quoted context omitted.

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.

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

Cloudflare is also the authoritative DNS server for many services. If Cloudflare is down, then for those services Google's DNS has nowhere to get the authoritative answers from.

Re: Cloudflare was down

#322

Post by tick_tock_tick »

toast0 wrote: post #317
atemerev wrote: post #216

Earlier quoted context omitted.

Be the change you want to see in the world :) There are no somebodys somewheres. One question is how to do DDoS protection without somebody like Cloudflare. Some new protocol for edge caching, perhaps?

DDoS has two components: a) complexity: trick your servers into doing something hard b) volumetric: overwelm your servers with a lot of traffic c) volumetric part two: overwelm your servers with a lot of requests, so you respond with a lot of traffic A and C are things you can work on your self --- try to limit the amount of work your server does in response to requests, and/or make resource consuming responses requi…

B) is the only one that really needs a solution and traffic is breaking two or three levels above you.

Re: Cloudflare was down

#323

Post by huderlem »

toast0 wrote: post #317
atemerev wrote: post #216

Earlier quoted context omitted.

Be the change you want to see in the world :) There are no somebodys somewheres. One question is how to do DDoS protection without somebody like Cloudflare. Some new protocol for edge caching, perhaps?

DDoS has two components: a) complexity: trick your servers into doing something hard b) volumetric: overwelm your servers with a lot of traffic c) volumetric part two: overwelm your servers with a lot of requests, so you respond with a lot of traffic A and C are things you can work on your self --- try to limit the amount of work your server does in response to requests, and/or make resource consuming responses requi…

I'm not very familiar with DDoS protection strategies. Can you please elaborate on what is meant in (c) by "make resource consuming responses require resource consuming requests"?

Re: Cloudflare was down

#324

Post by cortesoft »

ashleyn wrote: post #107

It really defies the original vision of the internet to have so many services depend on a single company. Almost every news site I was reading dropped off at once. I thought for a second that I lost internet in my own house.

I don't understand why the big companies don't always have at least two CDN providers, so they can failover to another one if something like this happens.

I know a lot of big companies do, but I am always surprised when you see ones that don't.

Re: Cloudflare was down

#325

Post by Figs »

cm2187 wrote: post #290
Figs wrote: post #276

Earlier quoted context omitted.

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.

No, I changed the setting back and forth while it was down to confirm that the issue was that I could not reach 1.0.0.1. All the entries I tried from my host file were responsive (which is how I ruled out an issue with my local equipment initially and confirmed that it wasn't a complete failure upstream -- I could still reach my servers). Changing 1.0.0.1 to 8.8.8.8 allowed me to reach websites like Google and HN, and changing back to default DNS settings (which reset to 1.0.0.1, confirmed in Wireshark) resulted in the immediate return of failures. 1.0.0.1 was not responsive to anything else I tried.

Again, it may not have been the only issue -- and there are a number of possible reasons why 1.0.0.1 wasn't reachable -- but it certainly was an issue.

Re: Cloudflare was down

#326

Post by Exuma »

Aside from this one issue, is switching to 1.1.1.1 a good idea in your guys experience? Right now I just realized I hvae the DNS for my ISP which is probably how they inject bullshit 404 pages full of ads. What is the fastest/best public DNS in your guys experience?

Re: Cloudflare was down

#328

Post by Cultmethod »

rococode wrote: post #9

Discord is entirely down right now, both the website and the app itself. Amusingly, a lot of the sites that normally track outages are also down, which made me think it was my internet at first. Downdetector, monitortheinternet, etc. Lots of other big sites that are down: Patreon, npmjs, DigitalOcean, Coinbase, Zendesk, Medium, GitLab (502), Fiverr, Upwork, Udemy Edit: 15 min later, looks like things are starting to…

Thought something like this was going on. At first I thought it was my router and restarted everything - to no avail. Glad to see confirmation that it wasn't an issue on my end.

Re: Cloudflare was down

#329

Post by toast0 »

nobleach wrote: post #184
parliament32 wrote: post #47

Earlier quoted context omitted.

Eggs and baskets etc etc

Good DNS practice (at least when I did system admin 10 years ago) was ALWAYS having a secondary at some other location/network. Why do we just put some info in Cloudflare and call it good these days?

It's hard to use Cloudflare as a reverse proxy without using them as your delegated name servers (maybe you can use CNAMEs on paid plans?), and fancy dynamic nameservers make it hard to run secondary servers with zone transfers.

Re: Cloudflare was down

#330

Post by wolfgang42 »

logicalmonster wrote: post #41

Given that the US is basically in a non-shooting war with China, I wonder if this is something technical or part of some kind of attack. Something that I’d keep in mind.

There are enough ways for bits of the Internet to go kablooey on their own that “it’s an attack!” is a pretty big jump to a conclusion. If this turns out to be something other than Cloudflare tripping over a weird bug, my first guess would be that someone fat-fingered a BGP table yet again.
Post reply on HN