Cloudflare outage: Workers KV storage fails, taking Zero Trust and other products with it
Storage behind Cloudflare's Workers KV failed when a third-party cloud provider it relies on had an outage, disrupting Access, WARP, Gateway and other products that depend on KV.
- Security:
- Explicitly ruled out
- Started
- Jun 12, 2025, 17:52 UTC
- Impact end
- Jun 12, 2025, 20:28 UTC
- Duration
- 2 h 36 min
- Full recovery
- Complete
- Geographic scope
- Global
- Last verified
- 1 source
What happened
- Systems and services affected
- Workers KVCloudflare AccessWARPGatewayWorkers AITurnstile and ChallengesImagesStreamCloudflare Dashboard (parts)
- Kind of failure
- Software defect
- Sector
- Internet infrastructure
- Provider report
- Published
- Status and recovery
- Resolved. Cloudflare's timeline marks impact end at 20:28 UTC.[1]
Cloudflare's report says the outage lasted 2 hours 28 minutes; its own timeline from incident start (17:52) to impact end (20:28) spans 2 hours 36 minutes.
What caused it?
Root cause: ConfirmedA failure in the storage infrastructure used by Workers KV. Cloudflare says part of that infrastructure "is backed by a third-party cloud provider, which experienced an outage today." Many Cloudflare products depend on KV for configuration and data.[1]
Provider report: Published. Cloudflare published its report on June 12, 2025.[1]
Was it malicious?
Explicitly ruled outCloudflare: "This was not the result of an attack or other security event."[1]
How the failure happened
- 1TriggerThird-party cloud provider outage
- 2FailureWorkers KV storage failed
- 3SpreadProducts depending on KV failed
- Affected9 services and systems
Evidence for each step
- 1
- 2Workers KV storage failed. Part of its storage is backed by that provider[1]Led from step 1: Stated in a provider report or official record.
- 3Products depending on KV failed. They use KV for configuration and data[1]Led from step 2: Stated in a provider report or official record.
Only steps the sources state are drawn. Affected services are listed under What happened.
Explanation
Both versions summarize the sourced claims on this page. Our own interpretation appears only under Independent analysis.
Plain language: what happened and why people were affected.
On June 12, 2025, several Cloudflare services, including its tools for securely connecting employees to company apps, failed for over two hours.
Many of those services store settings in a Cloudflare system called Workers KV. Part of the storage behind Workers KV runs on another company's cloud, and that cloud had an outage.
When KV became unavailable, every product that relied on it failed too.
Confirmed and unknown
Confirmed
Sources disagree
- DisputedThe outage lasted 2 hours 28 minutes, though the timeline's start and impact-end times are 2 hours 36 minutes apart.[1]Said by: Cloudflare · Evidence: Official
Denied
- DeniedIt was an attack or other security event.[1]Said by: Cloudflare · Evidence: Official
Still unknown
No open questions: the provider has published a full account.
Timeline
Times in UTC. Dates without a time mean the sources give no time. Only events a source documents are listed.
- First observedJun 12, 2025, 17:52 UTC
- AcknowledgedNot documented
- MitigationNot documented
- RecoveryNot documented
- ResolvedJun 12, 2025, 20:28 UTC
- Incident reportJun 12, 2025
Evidence and sources
Grouped by type of evidence. Numbers match the citations above.
Primary: provider and official sources
Published by the provider or agency itself: incident reports, status records, advisories, statements.
- 1.Cloudflare service outage June 12, 2025 (opens in a new tab)Cloudflare · Provider report · Published · Accessed
Last verified against these sources on Nov 14, 2026.