Cloudflare network traffic outage
A configuration change made while mitigating an industry-wide vulnerability caused a portion of Cloudflare’s network to experience significant request failures.
Incident summary
A configuration change made while mitigating an industry-wide vulnerability caused a portion of Cloudflare’s network to experience significant request failures.
The provider reported that customers accounting for approximately 28% of HTTP traffic served by Cloudflare were affected. The incident began at 08:47 UTC and was resolved at 09:12 UTC.
What the provider reported
Cloudflare traced the event to configuration changes made as part of mitigation work for a newly disclosed React Server Components vulnerability. The provider stated that the incident was not caused by an attack.
Editorial note: This is a concise summary of the provider’s public explanation, not an independent technical investigation.
Services and systems
Reported scope: Global · subset of customer traffic
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).
- 08:47 UTC Local conversion unavailable: source time is not normalized
Impact begins
A portion of the network begins experiencing significant failures.
- 09:12 UTC Local conversion unavailable: source time is not normalized
Service restored
Cloudflare reports that all services are fully restored; total duration approximately 25 minutes.
- No source clock time published
Provider postmortem published
Cloudflare publishes its explanation of the mitigation configuration change; no publication clock time was provided.
What did this incident feel like?
React anonymously. Counts are shared across visitors and are not a measure of the number of customers affected.