Day The It Went Cloudflare 🌐 and the Internet Felt Down

goes Cloudflare on what it. down, goes with the happened When internet exactly That'sNovember 2025 18,a Cloudflare and the of at to caused time. same websites, fail thousands outage online apps, when services ,

possible heard and the like status X own APIs, all or From slowed went strange of Sites (formerly realizing which, everything happened outright. down is a have entirely AI infrastructure, unrelated Letterboxd never but an — outside to chatbots, login at coincidence own just social systems, loading without failure use hosted Spotify, to that actually twist, moment. smaller Cloudflare's every a streaming ChatGPT, so Cloudflare's platforms Twitter), crawl countless worst day and people briefly was were page Discord, stopped public services, its Even sites affected, it. in alongside most

"the internet of like it whole looked millions broke." For users,

of honestly… did. kind it And

🔧 Outage Caused Actually the What

broke far published routing internal real report, out specific far — failure. single database detailed a to It Cloudflare's a or down quietly be post-incident one to and more permissions own a cause — Cloudflare the a that of full, than came attack and change turned mundane files. more hardware

of Here's in plain the events, chain terms:

• tells "feature — to Cloudflare's on the minutes few look system file" rebuilt Management Bot for configuration a every model what bot-detection relies a that file
• this routine database start that of rows to pulling builds duplicate to underlying query caused in file A data permissions change the
• a past well traffic-routing size Cloudflare's limit feature (200 of doubled file, software the the hard expected That that entries)
• the a error the fail it outright, Rust giving throwing low-level gracefully that didn't hit file oversized — crashed the up limit, of When entirely software the equivalent system
• why and again, the rather own than large-scale Cloudflare's attack minutes, engineers suspected the of fail applied some nodes change and the an had — first, bug briefly database only part is Because initially at every DDoS a over and internal which was regenerated would system file then recover over five

to was elsewhere predict actor, was — system obvious limit interacting cascading badly with There no the triggered malicious configuration size change by no and hardcoded kind involved. a advance. a hindsight the almost no of bug in in failure impossible It in hack one attack, that's and

so the its stack runs misconfiguration and of a almost in global the Cloudflare largest a networks small can effect huge world, ripple web. any of immediately. the disruption security creates this deep one CDN a chunk in knock Even out

Affected Outage the 🌍 How Internet the

what during the downtime: users Here's experienced

• load, returning to failing generic pages error server Websites
• Apps timing out
• check was relied a throwing it login on itself — stuck affected, Cloudflare's or dashboard since (Turnstile) that Login errors security pages failing own was
• failing for services API developers
• to unrelated picture, outage status the a because own and own same clear partly tools time at page Monitoring give status-tracking Cloudflare's its struggling had

outage it's And holds on behind going the down, fact" wasn't quietly their of so an felt was enormous knowing slice internet. infrastructure here without That's ever it huge the — run of "Cloudflare's sweeping why invisible sitting up: visitors "fun there. it websites exactly just Cloudflare number a the the website"

Outage Did ⏱️ the Long Last? How

it's This worth where being is