I recall a time when having your site down due to the /. effect was a point of pride. People would put banners on their website (afterwards) with "I've been slashdotted!"
Somehow, "I've been cloudflared!" doesn't have *quite* the same ring, eh?
So after the last #Cloudflare outage I mistakenly thought they would unlikely have the same issue again and have been all week looking at offering some other CF service solution for one of our clients, well that's all down the pan now!
one day you unwrap() what you shouldn't have, another day you again unwrap what you shouldn't have. What should I do with you bigtech? #cloudflare #whatsapp #bigtech
What a great and transparent analysis of the outage. No excuses, honest admission of mistakes, and even shared an internal chat. Many large corporations could learn from this.
Cloudflare suffered a service outage on November 18, 2025. The outage was triggered by a bug in generation logic for a Bot Management feature file causing many Cloudflare services to be affected.
> the root cause of the outage was a configuration file that is automatically generated to manage threat traffic. The file grew beyond an expected size of entries and triggered a crash in the software system that handles traffic for a number of Cloudflare’s services arstechnica.com/tech-policy/20…
hypercentralizers are not having a good day today -- #github has joined #cloudflare to block or slow down millions of folks from doing stuff.
Maybe a good time to checkout out this new ACLU article about the current Apple/Google app-store oligopoly aclu.org/news/free-speech/app-…
TL;dr Google/Apple increasingly wield their world-wide #appcontrol in the political interests of various governments, and not in the interest of user security or privacy. The article lays out three areas of fighting back ...
it's not a proper outage until the status page is rendering without CSS (it's not a flawless 10/10 outage until the status page is in a DNS black hole)
