Live data from Hacker News

Cloudflare Global Network experiencing issues

cloudflarestatus.com

901–910 of 1001 posts

Re: Cloudflare Global Network experiencing issues

#901

How did we get to a place where either Cloudflare or AWS having an outage means a large part of the web going down? This centralization is very worrying.

Because it's better to have a really convenient and cheap service that works 99% of the time, than a resilient that is more expensive or more cumbersome to use.

It's like github vs whatever else you can do with git that is truly decentralized. The centralization has such massive benefits that I'm very happy to pay the price of "when it's down I can't work".

Re: Cloudflare Global Network experiencing issues

#902

How did we get to a place where either Cloudflare or AWS having an outage means a large part of the web going down? This centralization is very worrying.

I would be less worried if Cloudflare and AWS weren't involved in many more things than simply running DNS.

AWS - someone touches DynamoDB and it kills the DNS.

Cloudflare - someone touches functionality completely unrelated to DNS hosting and proxying and, naturally, it kills the DNS.

There is this critical infrastructure that just becomes one small part of a wider product offering, worked on by many hands, and this critical infrastructure gets taken down by what is essentially a side-effect.

It's a strong argument to move to providers that just do one thing and do it well.

Re: Cloudflare Global Network experiencing issues

#903
post #899

Later today or tomorrow there's going to be a post on HN pointing to Cloudflare's RCA and multitudes here are going to praise CF for their transparency. Let's not forget that CF sucks and took half the internet down for four hours. Transparency or no, this should not be happening.

Alot of things shouldnt be happening. Fact is that no one forced half the internet to make CF their point of failure. The internet should ask themselves if that was the right call

Re: Cloudflare Global Network experiencing issues

#904

How did we get to a place where either Cloudflare or AWS having an outage means a large part of the web going down? This centralization is very worrying.

Most developers don't care to know how the underlying infrastructure works (or why) and so they take whatever the public consensus is re: infra as a statement of fact (for the better part of the last 15 years or so that was "just use the cloud"). A shocking amount of technical decisions are socially, not technically enforced.

Re: Cloudflare Global Network experiencing issues

#905

> A fix has been implemented and we believe the incident is now resolved. We are continuing to monitor for errors to ensure all services are back to normal. Posted 3 minutes ago. Nov 18, 2025 - 14:42 UTC Seems like they think they've fixed it fully this time!

Close! They just updated their states and it's back to working on a fix

Update - Some customers may be still experiencing issues logging into or using the Cloudflare dashboard. We are working on a fix to resolve this, and continuing to monitor for any further issues. Nov 18, 2025 - 14:57 UTC

Re: Cloudflare Global Network experiencing issues

#907

Since when does critical infrastructure fail weekly?! One week is AWS, then azure + AWS, now cloudfare... Time to go back to on prem. AWS and co are too expensive anyways

A lot of people are "on prem" but use CloudFlare to proxy traffic for DDoS attack mitigation, among other reasons.

Re: Cloudflare Global Network experiencing issues

#908

How did we get to a place where either Cloudflare or AWS having an outage means a large part of the web going down? This centralization is very worrying.

This was always the case. There was always a "us-east" in some capacity, under Equinix, etc. Except it used to be the only "zone," which is why the internet is still so brittle despite having multiple zones. People need to build out support for different zones. Old habits die hard, I guess.

Re: Cloudflare Global Network experiencing issues

#910

If anyone needs commands for turning off the CF proxy for their domains and happens to have a Cloudflare API token. First you can grab the zone ID via: curl -X GET "https://api.cloudflare.com/client/v4/zones" -H "Authorization: Bearer $API_TOKEN" -H "Content-Type: application/json" | jq -r '.result[] | "\(.id) \(.name)"' And a list of DNS records using: curl -X GET "https://api.cloudflare.com/client/v4/zones/$ZONE_ID…

This is exactly what we've decided we should do next time. Unfortunately we didn't generate an API token so we are sitting twiddling our thumbs. Edit: seems like we are back online!

Im able to generate keys right now through warp. Login takes forever but it is working.
Post reply on HN