December 5, 2025
Global switch, global glitch
Cloudflare outage on December 5, 2025
Cloudflare’s 25‑minute hiccup: devs roast the “global switch”
TLDR: Cloudflare went down for 25 minutes, affecting about 28% of traffic, after a protective tweak for a new React issue backfired. Comments blasted a no‑rollout “global switch,” argued fail‑closed vs fail‑open, and memed “unwrap” while reigniting type‑system debates—because when Cloudflare trips, the internet feels it.
Cloudflare, the company that speeds and shields much of the web, stumbled for about 25 minutes at 08:47 UTC, with roughly 28% of traffic impacted. It wasn’t a hack—Cloudflare says the meltdown came from changes while guarding against a new issue in React Server Components, explained in their post and vuln write‑up. The fix collided with a bug and poof—errors.
But the real story? The comments went feral. One coder deadpanned “Unwrap() strikes again”, turning a programmer pain point into today’s meme. Another highlighted Cloudflare’s own words: a global configuration system that “does not use gradual rollouts,” a phrase instantly crowned the villain of the day. As xnorswap paraphrased, the change “broke everything at once,” igniting demands for blast‑radius control and staged rollouts.
Drama escalated around fail‑closed decisions (systems stopping when uncertain) versus keep‑things‑running tactics, with kachapopopow sighing that it all felt “oddly familiar.” barbazoo noted the China network wasn’t affected—“Interesting”—fueling eyebrow‑raises. Then came the language wars: some insisted strong type systems would’ve prevented this class of bug, while others rolled their eyes at the idea that one language can save the internet. Cloudflare promised fixes after their November 18 wobble; the crowd’s verdict: test, stage, and stop flipping global switches in seconds.
Key Points
- •Cloudflare experienced an outage on December 5, 2025, from 08:47 to 09:12 UTC (~25 minutes).
- •About 28% of Cloudflare’s HTTP traffic was affected during the incident.
- •The outage was not caused by a cyberattack or malicious activity.
- •The trigger was changes to body parsing logic made to mitigate a newly disclosed React Server Components vulnerability.
- •Cloudflare will publish more details next week on prevention efforts following a prior incident on November 18.