Skip to content

CDN and DNS · Cloudflare

Cloudflare global outage from oversized Bot Management feature file

Started
Nov 18, 2025, 11:20 UTC
Resolved
Nov 18, 2025, 17:06 UTC
Duration
5h 46m (from provider timestamps)
Affected
Core CDN and security services, Turnstile, Workers KV, Cloudflare Dashboard (login), Cloudflare Access, Email Security (partial)
Cause
Final reviewA ClickHouse permissions change at 11:05 UTC made the query that builds the Bot Management feature file return duplicate rows, more than doubling the file. The file was propagated to every machine, and the core proxy's Bot Management module, which preallocates memory for at most 200 features, failed and served HTTP 5xx errors. Because the cluster was updated gradually, good and bad files alternated every five minutes, so the network recovered and failed repeatedly.
Was it an attack?
No, per the provider or investigators
State
resolved

Anatomy

  1. 1. Trigger

    Configuration change

  2. 2. Already broken

    Hard limit, Missing validation, Latent bug

  3. 3. What made it spread

    Global configuration propagation

  4. 4. Blast radius

    global: Global

  5. 5. Cause category

    Change or deployment

Labels follow the root-cause taxonomy. A person's change is recorded as the trigger and the missing safeguard as what was already broken; “human error” is never a cause here.

How the explanation changed

  1. November 18, 2025 · Final review

    “The issue was not caused, directly or indirectly, by a cyber attack or malicious activity of any kind. Instead, 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.”

    Cloudflare blog: Cloudflare outage on November 18, 2025

What the provider committed to change

  • Harden ingestion of Cloudflare-generated configuration files as if user-generated input
  • Enable more global kill switches for features
  • Stop core dumps and error reports from overwhelming system resources
  • Review failure modes for error conditions across all core proxy modules

Impact, as reported

Every figure is attributed to whoever stated it. Crowd reports are labelled user reports and never treated as users affected.

Attack or not

“The issue was not caused, directly or indirectly, by a cyber attack or malicious activity of any kind.”

Cloudflare (postmortem blog), November 18, 2025 (Cloudflare blog: Cloudflare outage on November 18, 2025)

Post-incident reviews

Other Cloudflare incidents

Sources

  1. Cloudflare blog: Cloudflare outage on November 18, 2025 (provider, read November 17, 2026)

Last verified November 17, 2026. Spot an error? The methodology page says how corrections work.