What happened
Cloudflare: Bot Management feature file doubled and crashed traffic-routing software. Scope: Global.
CHYP.ai · ORBIT // Cloudy_Day Security Suite
OUTAGE DISSECTOR · CASE FILE · Meltdown Index · vendor post-incident report
Cloudflare: Bot Management feature file doubled and crashed traffic-routing software. Scope: Global.
Severe storm
Drag or press Play to replay what was public at each moment. Each dot links to its evidence. Lanes are kept separate on purpose.
Cloudflare: Bot Management feature file doubled and crashed traffic-routing software. Scope: Global.
Cloudflare core proxy / CDN, Workers KV, Cloudflare Access.
14 catalogued services run on Cloudflare (inferred). Hit: Global.
Resolved after 5h 46m.
Center: Cloudflare. Inner ring: what it runs on. Outer ring: catalogued services that run on it, coloured by their official status right now. Dependencies are inferred from public information.
Places come from names in the public text (cities, PoP codes, countries, regions). Approximate.
Failure modes as stated in the vendor's own post-incident report (Meltdown Index).
Correlation is not causation
Five independent lanes across the window. Brighter = stronger item. Items landing in the same column are coincidence unless the provider says otherwise.
It was triggered by a change to one of our database systems’ permissions which caused the database to output multiple entries into a “feature file” used by our Bot Management system. That feature file, in turn, doubled in size. The larger-than-expected feature file was then propagated to all the machines that make up our network. The software running on these machines to route traffic across our network reads this feature file to keep our Bot Management system up to date with ever changing threats. The software had a limit on the size of the feature file that was below its doubled size. That caused the software to fail.
Onset 11:20 UTC; core traffic largely normal by 14:30 UTC (3h 10m); all systems functioning as normal as of 17:06 UTC (5h 46m). duration_minutes records the official core-traffic recovery. Cloudflare stated the issue was not a cyber attack.
Verbatim excerpt from Cloudflare outage on November 18, 2025.
75% similar · same provider
Backbone router configuration error overwhelmed Atlanta
Config pushCapacity
70% similar · same provider
WAF change for a React vulnerability hit a latent Lua bug
Config push
70% similar · same provider
New DDoS rule exposed a latent rate-limiting bug
Config push
Nearest matches in the Control-Plane Meltdown Index (1.0.0, vendor-sourced, tracked since 2024 with earlier landmark cases). Similarity = provider + failure modes + scope.
Automated take: rules written by Cloudy_Day, applied to public data. Not a human verdict on this incident, not a root-cause finding, not affiliated with Cloudflare.
Everything above as one shareable, citable capsule with a content hash.
JSON capsuleMarkdownShare card (SVG)
Open Cloudflare in the War Room →Status page →
<a href="https://www.chyp.ai/dissect/m/cf-bot-feature-file-2025-11-18/"><img src="https://www.chyp.ai/dissect/m/cf-bot-feature-file-2025-11-18/card.svg" alt="Bot Management feature file doubled and crashed traffic-rou… · ORBIT Outage Dissector" width="600"></a>