Hacker News Reader

Comment by tmlee | Hacker News Reader

So it seems... Even https://cloudflare.com/ itself is down

More importantly, their admin dashboard is down. It's impossible to bypass their "orange cloud" proxies and send traffic directly to our hosting. That they can't flip a switch and have their nameservers send dash.cloudflare.com to a separate piece of redundant infrastructure is mind-boggling.

Agreed. First thing I tried to do was login Cloudflare to disable proxying. But can't.

change the nameserver at the registrar to someone else

By the time that change propagates, cloudflare will be backup

Yes, but then next time you will be able to control your DNS.

Though, only if you're using a short TTL. I'm not arguing against your position in general though.

We were able to flip this switch on our services through their API, as we have our Cloudflare config in Terraform.

The API wasn't working perfectly, but with some retries we were able to change the config for our domains.

Yep, I'm seeing 502's all over the web as of a few minutes ago.

Great, now we can't even disable HTTP proxy to allow traffic directly to AWS :/

Point your DNS back to your actual host? Might be the only short term solution, though DNS propagation times kinda rule that out :/

That's a no-go if you transferred your domains to Cloudflare Registrar.

Something something all your eggs in one basket :)

Seems like even other registrars might rely on Cloudflare (e.g. Namecheap) so now people have to continuously ensure there’s no cross-pollination between their infra providers...

I think the only option here would be to change our name servers at registrar level to point to AWS and recreate all DNS records there, but then you have to deal with name server propagation.

We use our own service.

EDIT: the static pages load but trying to log in just times out. I think the static cache is back up but the rest of it is still down.

Seems to be back up and running for me.

So cloudflare.com runs on Cloudflare?

Turtles all the way down.

But in all frankness, if Cloudflare's own site did not run off of Cloudflare's infrastructure, why would anybody trust them with their websites?

Ironic isn't it.

Certainly what I would use if I was building cloudflare.com...

For the site itself that's totally fine, and the status page is separate as it should be, too.

Fair. Some service recently had their status page hosted on the same server that went down, that was funny.

Discord's status page is also down haha

I'm quite surprised Discord's status page is behind Cloudflare. I thought they were using statuspage.io.

They are, but that subdomain is proxied through Cloudflare. If they'd set it to just DNS then it would have still worked.

I guess it's like diversifying one's assets - you put your status page elsewhere than on your own infrastructure.

This is fine-ish...

In case of network issues affecting their proxy, being able to change your configuration to allow direct traffic would be really nice.

Reply on news.ycombinator.com