Outages at web infrastructure provider Cloudflare this morning are affecting services such as Twitter/X, OpenAI and Downdetector (!).
https://www.tomshardware.com/news/live/cloudflare-outage-under-investigation-as-twitter-downdetector-go-down-company-confirms-global-network-issue-clone
https://www.cloudflarestatus.com/
1/n
engadget is reporting that Downdetector is showing X, Spotify and other sites as returning to normal.
Cloudflare posted at 8:13 ET that "the issue has been identified and a fix is being implemented. We have made changes that have allowed Cloudflare Access and WARP to recover. Error levels for Access and WARP users have returned to pre-incident rates."
I still cannot access Downdetector or X.
https://www.engadget.com/big-tech/cloudflare-hit-by-outage-causing-widespread-errors-124208302.html
2/n
Downdetector is up now (for me at least). It shows outage reports spiking up again at X, Cloudflare, OpenAI, Spotify, AWS, ...
https://downdetector.com/
3/n
Cloudflare has a long blog post summarizing the root cause of the outages today.
It was triggered by a change to a database systems' permissions which caused it to output multiple entries into a βfeature fileβ used by their Bot Management system. That feature file, in turn, doubled in size.
The software that read this file "panic'd" since the file contained more objects than a predefined limit of 200.
"Don't panic" should be a reqment for real-time sw!
https://blog.cloudflare.com/18-november-2025-outage/
4/n
When faced with unexpected conditions in your software, handle them in some rational way, scrub the data, spit out some alarm messages, email the developer and continue processing, but Don't Panic!
5/n