Cloudflare core network outage
A malformed Bot Management feature file propagated across Cloudflare’s network and caused core proxy failures, resulting in widespread HTTP errors and authentication problems.
Incident summary
A malformed Bot Management feature file propagated across Cloudflare’s network and caused core proxy failures, resulting in widespread HTTP errors and authentication problems.
Core traffic was largely flowing normally by 14:30 UTC, while remaining services were restored by 17:06 UTC. Impact included HTTP 5xx errors, Turnstile failures, elevated Workers KV errors, and Cloudflare Access authentication failures.
What the provider reported
A database permissions change caused a query to emit duplicate entries into a Bot Management feature file. The file grew beyond a size limit in the core proxy software and was distributed across the network.
Editorial note: This is a concise summary of the provider’s public explanation, not an independent technical investigation.
Services and systems
Reported scope: Global
Latest source updates
Showing up to the 3 latest updates available in the source record. UTC is fixed; local time is converted in this browser (your local timezone).
- 13:05 UTC Local conversion unavailable: source time is not normalized
Impact reduced
Internal bypasses for Workers KV and Cloudflare Access reduce the impact.
- 14:30 UTC Local conversion unavailable: source time is not normalized
Main impact resolved
A known-good Bot Management configuration is deployed globally and most services operate normally.
- 17:06 UTC Local conversion unavailable: source time is not normalized
All services restored
Downstream services are restarted and all operations return to normal.
What did this incident feel like?
React anonymously. Counts are shared across visitors and are not a measure of the number of customers affected.