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

Cloudflare outage on February 20, 2026

blog.cloudflare.com

Post reply on HN
Print view View original

51–60 of 135 posts

Re: Cloudflare outage on February 20, 2026

#51

Post by slophater »

slophater wrote: post #46
atty wrote: post #4

I do not work in the space at all, but it seems like Cloudflare has been having more network disruptions lately than they used to. To anyone who deals with this sort of thing, is that just recency bias?

been at cf for 7 yrs but thinking of gtfo soon. the ceo is a manchild, new cto is an idiot, rest of leadership was replaced by yes-men, and the push for AI-first is being a disaster. c levels pretend they care about reliability but pressure teams to constantly ship, cto vibe codes terraform changes without warning anyone, and it's overall a bigger and bigger mess even the blog, that used to be a respected source of t…

amazing how my comment was flagged in 30 seconds... keep bootlicking

Re: Cloudflare outage on February 20, 2026

#53

Post by argestes »

otar wrote: post #50

Reliability was/is CF's label. It's alarming already. Too many outages in the past months. CF should fix it, or it becomes unacceptable and people will leave the platform. I really hope they will figure things out.

I have many things dependent on Cloudflare. That makes me root for Cloudflare and I think I'm not the only one. Instead of finding better options we're getting stuck on an already failing HA solution. I wonder what caused this.

Re: Cloudflare outage on February 20, 2026

#54

Post by martinald »

CommonGuy wrote: post #3

Insufficient mock data in the staging environment? Like no BYOIP prefixes at all? Since even one prefix should have shown that it would be deleted by that subtask... From all the recent outages, it sounds like Cloudflare is barely tested at all. Maybe they have lots of unit tests etc, but they do not seem to test their whole system... I get that their whole setup is vast, but even testing that subtask manually would…

Just crazy. Why does a staging environment matter? They should be running some integration tests against eg an in memory database for these kinds of tasks surely?

Re: Cloudflare outage on February 20, 2026

#55

Post by jbxntuehineoh »

blibble wrote: post #35
bretthoerner wrote: post #20

Earlier quoted context omitted.

> even if the client had passed a value it would have still done exactly the same thing, as the value of "v" (or anything from the request) is not used in that block If they passed in any value, they would have entered the block and returned early with the results of FetchPrefixesPendingDeletion. From the post: > this was implemented as part of a regularly running sub-task that checks for BYOIP prefixes that should b…

okay so the code which returned everything isn't there actual explanation: the API server by default returns everything. the client attempted to make a request to return "pending_deletes", but as the request was malformed, the API instead went down the default path, which returned everything. then the client deleted everything. makes sense now but is that explanation is even worse because that means the code path was…

or they tested it, but not with a dataset that contained prefixes not pending deletion

Re: Cloudflare outage on February 20, 2026

#56

Post by dilyevsky »

> Because the client is passing pending_delete with no value, the result of Query().Get(“pending_delete”) here will be an empty string (“”), so the API server interprets this as a request for all BYOIP prefixes instead of just those prefixes that were supposed to be removed.

Lmao, iirc long time ago Google's internal system had the same exact bug (treating empty as "all" in the delete call) that took down all their edges. Surprisingly there was little impact as traffic just routed through the next set of proxies.

Re: Cloudflare outage on February 20, 2026

#57

Post by samrus »

dakiol wrote: post #36
NinjaTrance wrote: post #8

Earlier quoted context omitted.

Engineers have been vibe coding a lot recently...

No joke. In my company we "sabotaged" the AI initiative led by the CTO. We used LLMs to deliver features as requested by the CTO, but we introduced a couple of bugs here and there (intentionally). As a result, the quarter ended up with more time allocated to fix bugs and tons of customer claims. The CTO is now undoing his initiative. We all have now some time more to keep our jobs.

Thats actively malicious. I understand not going out of your way to catch the LLMs' bugs so as to show the folly of the initiative, but actively sabotaging it is legitimately dangerous behavior. Its acting in bad faith. And i say this as someone who would mostly oppose such an initiative myself

I would go so far as to say that you shouldnt be employed in the industry. Malicious actors like you will contribute to an erosion of trust thatll make everything worse

Re: Cloudflare outage on February 20, 2026

#59

Post by a24446ff87 »

slophater wrote: post #46
atty wrote: post #4

I do not work in the space at all, but it seems like Cloudflare has been having more network disruptions lately than they used to. To anyone who deals with this sort of thing, is that just recency bias?

been at cf for 7 yrs but thinking of gtfo soon. the ceo is a manchild, new cto is an idiot, rest of leadership was replaced by yes-men, and the push for AI-first is being a disaster. c levels pretend they care about reliability but pressure teams to constantly ship, cto vibe codes terraform changes without warning anyone, and it's overall a bigger and bigger mess even the blog, that used to be a respected source of t…

GSD! GSD!! ship! ship! ship!

**everything breaks**

...

**everything breaks again**

oh fuck! Code Orange! I repeat, Code Orange! we need to rebuild trust(R)(TM)! we've let our customers down!

...

**everything breaks again**

Code Orangier! I repeat, Code Orangier!

Post reply on HN