CHYP.ai · ORBIT // Cloudy_Day Security Suite

OUTAGE DISSECTOR · CASE FILE · Meltdown Index · vendor post-incident report

Bot Management feature file doubled and crashed traffic-routing software

Cloudflare resolved M8.1 Severe storm 2025-11-18

Cloudflare: Bot Management feature file doubled and crashed traffic-routing software. Scope: Global.

M8.1

Severe storm

How CHYP Magnitude works

  • 5h 46mDurationstart → resolved
  • 3Systems namedfrom the source
  • 7Places named7 on the map
  • 14Dependentscatalogued, inferred
  • 2/4Evidence kindsindependent families
  • 2Updatesofficial revisions

1Scrub the outage

full window
Severityofficial state Nov 18, 3 AMNov 18, 4 AMNov 18, 5 AMNov 18, 6 AMNov 18, 7 AMNov 18, 9 AM Official statusNov 18, 3:20 AM PT · Impact begins (vendor-stated)Nov 18, 9:06 AM PT · Mitigated (vendor-stated)Network & routingnothing in this windowEarly signalsnothing in this windowNews & chatternothing in this windowCoincidence (KEV)nothing in this window ▼ startresolved ▼

Drag or press Play to replay what was public at each moment. Each dot links to its evidence. Lanes are kept separate on purpose.

What happened

Cloudflare: Bot Management feature file doubled and crashed traffic-routing software. Scope: Global.

What broke

Cloudflare core proxy / CDN, Workers KV, Cloudflare Access.

Who was hit

14 catalogued services run on Cloudflare (inferred). Hit: Global.

How it recovered

Resolved after 5h 46m.

2Blast radius

Cloudflare DNS (1.1.1.1) · Degraded / minor incidentCloudflare DNS …Cloudflare Zero Trust · Degraded / minor incidentCloudflare Zero…Canva · OperationalCanvaClerk · OperationalClerkDiscord · OperationalDiscordDocker Hub · OperationalDocker HubKinsta · OperationalKinstaNotion · OperationalNotionnpm · OperationalnpmOpenAI (ChatGPT & API) · OperationalOpenAI (ChatGPT…Shopify · OperationalShopifyVercel · OperationalVercelWebflow · OperationalWebflowOpenRouter · no official feed / staleOpenRouterCloudflare14 dependents

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.

3Blast map

North America · vendor-stated scope: globalSouth America · vendor-stated scope: globalEurope · vendor-stated scope: globalAfrica · vendor-stated scope: globalMiddle East · vendor-stated scope: globalAsia · vendor-stated scope: globalOceania · vendor-stated scope: global
  1. North America
  2. South America
  3. Europe
  4. Africa
  5. Middle East
  6. Asia
  7. Oceania

Places come from names in the public text (cities, PoP codes, countries, regions). Approximate.

4Failure-mode fingerprint

RetriesControl planeConfig pushCascadeCapacity
  • Config propagationvendor post-incident report (Meltdown Index)
  • Dependency cascadevendor post-incident report (Meltdown Index)
  • Capacity exhaustionvendor post-incident report (Meltdown Index)
  • Retry amplificationno sign
  • Control-plane couplingno sign

Failure modes as stated in the vendor's own post-incident report (Meltdown Index).

5Evidence matrix

Official statusOfficial status · Nov 17, 9:20 PM PT: 0 itemsOfficial status · Nov 17, 9:49 PM PT: 0 itemsOfficial status · Nov 17, 10:18 PM PT: 0 itemsOfficial status · Nov 17, 10:48 PM PT: 0 itemsOfficial status · Nov 17, 11:17 PM PT: 0 itemsOfficial status · Nov 17, 11:47 PM PT: 0 itemsOfficial status · Nov 18, 12:16 AM PT: 0 itemsOfficial status · Nov 18, 12:45 AM PT: 0 itemsOfficial status · Nov 18, 1:15 AM PT: 0 itemsOfficial status · Nov 18, 1:44 AM PT: 0 itemsOfficial status · Nov 18, 2:14 AM PT: 0 itemsOfficial status · Nov 18, 2:43 AM PT: 0 itemsOfficial status · Nov 18, 3:13 AM PT: 1 itemOfficial status · Nov 18, 3:42 AM PT: 0 itemsOfficial status · Nov 18, 4:11 AM PT: 0 itemsOfficial status · Nov 18, 4:41 AM PT: 0 itemsOfficial status · Nov 18, 5:10 AM PT: 0 itemsOfficial status · Nov 18, 5:40 AM PT: 0 itemsOfficial status · Nov 18, 6:09 AM PT: 0 itemsOfficial status · Nov 18, 6:38 AM PT: 0 itemsOfficial status · Nov 18, 7:08 AM PT: 0 itemsOfficial status · Nov 18, 7:37 AM PT: 0 itemsOfficial status · Nov 18, 8:07 AM PT: 0 itemsOfficial status · Nov 18, 8:36 AM PT: 0 itemsNetwork & routingNetwork & routing · Nov 17, 9:20 PM PT: 0 itemsNetwork & routing · Nov 17, 9:49 PM PT: 0 itemsNetwork & routing · Nov 17, 10:18 PM PT: 0 itemsNetwork & routing · Nov 17, 10:48 PM PT: 0 itemsNetwork & routing · Nov 17, 11:17 PM PT: 0 itemsNetwork & routing · Nov 17, 11:47 PM PT: 0 itemsNetwork & routing · Nov 18, 12:16 AM PT: 0 itemsNetwork & routing · Nov 18, 12:45 AM PT: 0 itemsNetwork & routing · Nov 18, 1:15 AM PT: 0 itemsNetwork & routing · Nov 18, 1:44 AM PT: 0 itemsNetwork & routing · Nov 18, 2:14 AM PT: 0 itemsNetwork & routing · Nov 18, 2:43 AM PT: 0 itemsNetwork & routing · Nov 18, 3:13 AM PT: 0 itemsNetwork & routing · Nov 18, 3:42 AM PT: 0 itemsNetwork & routing · Nov 18, 4:11 AM PT: 0 itemsNetwork & routing · Nov 18, 4:41 AM PT: 0 itemsNetwork & routing · Nov 18, 5:10 AM PT: 0 itemsNetwork & routing · Nov 18, 5:40 AM PT: 0 itemsNetwork & routing · Nov 18, 6:09 AM PT: 0 itemsNetwork & routing · Nov 18, 6:38 AM PT: 0 itemsNetwork & routing · Nov 18, 7:08 AM PT: 0 itemsNetwork & routing · Nov 18, 7:37 AM PT: 0 itemsNetwork & routing · Nov 18, 8:07 AM PT: 0 itemsNetwork & routing · Nov 18, 8:36 AM PT: 0 itemsEarly signalsEarly signals · Nov 17, 9:20 PM PT: 0 itemsEarly signals · Nov 17, 9:49 PM PT: 0 itemsEarly signals · Nov 17, 10:18 PM PT: 0 itemsEarly signals · Nov 17, 10:48 PM PT: 0 itemsEarly signals · Nov 17, 11:17 PM PT: 0 itemsEarly signals · Nov 17, 11:47 PM PT: 0 itemsEarly signals · Nov 18, 12:16 AM PT: 0 itemsEarly signals · Nov 18, 12:45 AM PT: 0 itemsEarly signals · Nov 18, 1:15 AM PT: 0 itemsEarly signals · Nov 18, 1:44 AM PT: 0 itemsEarly signals · Nov 18, 2:14 AM PT: 0 itemsEarly signals · Nov 18, 2:43 AM PT: 0 itemsEarly signals · Nov 18, 3:13 AM PT: 0 itemsEarly signals · Nov 18, 3:42 AM PT: 0 itemsEarly signals · Nov 18, 4:11 AM PT: 0 itemsEarly signals · Nov 18, 4:41 AM PT: 0 itemsEarly signals · Nov 18, 5:10 AM PT: 0 itemsEarly signals · Nov 18, 5:40 AM PT: 0 itemsEarly signals · Nov 18, 6:09 AM PT: 0 itemsEarly signals · Nov 18, 6:38 AM PT: 0 itemsEarly signals · Nov 18, 7:08 AM PT: 0 itemsEarly signals · Nov 18, 7:37 AM PT: 0 itemsEarly signals · Nov 18, 8:07 AM PT: 0 itemsEarly signals · Nov 18, 8:36 AM PT: 0 itemsNews & chatterNews & chatter · Nov 17, 9:20 PM PT: 0 itemsNews & chatter · Nov 17, 9:49 PM PT: 0 itemsNews & chatter · Nov 17, 10:18 PM PT: 0 itemsNews & chatter · Nov 17, 10:48 PM PT: 0 itemsNews & chatter · Nov 17, 11:17 PM PT: 0 itemsNews & chatter · Nov 17, 11:47 PM PT: 0 itemsNews & chatter · Nov 18, 12:16 AM PT: 0 itemsNews & chatter · Nov 18, 12:45 AM PT: 0 itemsNews & chatter · Nov 18, 1:15 AM PT: 0 itemsNews & chatter · Nov 18, 1:44 AM PT: 0 itemsNews & chatter · Nov 18, 2:14 AM PT: 0 itemsNews & chatter · Nov 18, 2:43 AM PT: 0 itemsNews & chatter · Nov 18, 3:13 AM PT: 0 itemsNews & chatter · Nov 18, 3:42 AM PT: 0 itemsNews & chatter · Nov 18, 4:11 AM PT: 0 itemsNews & chatter · Nov 18, 4:41 AM PT: 0 itemsNews & chatter · Nov 18, 5:10 AM PT: 0 itemsNews & chatter · Nov 18, 5:40 AM PT: 0 itemsNews & chatter · Nov 18, 6:09 AM PT: 0 itemsNews & chatter · Nov 18, 6:38 AM PT: 0 itemsNews & chatter · Nov 18, 7:08 AM PT: 0 itemsNews & chatter · Nov 18, 7:37 AM PT: 0 itemsNews & chatter · Nov 18, 8:07 AM PT: 0 itemsNews & chatter · Nov 18, 8:36 AM PT: 0 itemsCoincidence (KEV)Coincidence (KEV) · Nov 17, 9:20 PM PT: 0 itemsCoincidence (KEV) · Nov 17, 9:49 PM PT: 0 itemsCoincidence (KEV) · Nov 17, 10:18 PM PT: 0 itemsCoincidence (KEV) · Nov 17, 10:48 PM PT: 0 itemsCoincidence (KEV) · Nov 17, 11:17 PM PT: 0 itemsCoincidence (KEV) · Nov 17, 11:47 PM PT: 0 itemsCoincidence (KEV) · Nov 18, 12:16 AM PT: 0 itemsCoincidence (KEV) · Nov 18, 12:45 AM PT: 0 itemsCoincidence (KEV) · Nov 18, 1:15 AM PT: 0 itemsCoincidence (KEV) · Nov 18, 1:44 AM PT: 0 itemsCoincidence (KEV) · Nov 18, 2:14 AM PT: 0 itemsCoincidence (KEV) · Nov 18, 2:43 AM PT: 0 itemsCoincidence (KEV) · Nov 18, 3:13 AM PT: 0 itemsCoincidence (KEV) · Nov 18, 3:42 AM PT: 0 itemsCoincidence (KEV) · Nov 18, 4:11 AM PT: 0 itemsCoincidence (KEV) · Nov 18, 4:41 AM PT: 0 itemsCoincidence (KEV) · Nov 18, 5:10 AM PT: 0 itemsCoincidence (KEV) · Nov 18, 5:40 AM PT: 0 itemsCoincidence (KEV) · Nov 18, 6:09 AM PT: 0 itemsCoincidence (KEV) · Nov 18, 6:38 AM PT: 0 itemsCoincidence (KEV) · Nov 18, 7:08 AM PT: 0 itemsCoincidence (KEV) · Nov 18, 7:37 AM PT: 0 itemsCoincidence (KEV) · Nov 18, 8:07 AM PT: 0 itemsCoincidence (KEV) · Nov 18, 8:36 AM PT: 0 itemsNov 17, 9:20 PM PTNov 18, 9:06 AM PT

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.

6In the vendor's words

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.

7Historical twins

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.

Cloudy_Day take

  • A change went wider, faster than its safety net. Staged rollouts and kill switches exist for exactly this.
  • Longer than 10 of 19 indexed control-plane meltdowns with a stated duration.

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.

8Dissection capsule

Share card for this dissection

Everything above as one shareable, citable capsule with a content hash.

JSON capsuleMarkdownShare card (SVG)

Open Cloudflare in the War Room →Status page →

Embed this card
<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>

Sources & limits

  • Taken from the vendor's own post-incident report; quotes are verbatim excerpts.
  • Dependents are today's inferred catalogue, not who was affected on the day.
  • Correlation is not causation. Lanes are kept apart so overlap never reads as cause.
  • ORBIT is passive: it never contacts the provider or probes its systems. Independent researcher, not affiliated.