Cloudflare attributes the outage to storage infrastructure underlying Workers KV, including a third-party cloud dependency.
Cloudflare · inspect the source ↗INCIDENT BRIEF / SERVICE OUTAGE
Cloudflare Workers KV outage: trace identity and configuration dependencies
A secondary platform dependency can affect authentication and configuration across several products at once. Ask which emergency access paths depend on the same storage or identity service as production. Any alternate access must preserve scoped permissions and an audit trail. Use the preserved provider account below to distinguish reported facts from the proposed review exercise.
01 / SOURCE-ATTRIBUTED REPORTING
What the evidence establishes.
Cloudflare reports a 2-hour-28-minute global impact for customers using the affected services.
Cloudflare · inspect the source ↗The provider states no data was lost and distinguishes several core services that were not directly affected.
Cloudflare · inspect the source ↗02 / KEEP THE SEQUENCE
A dated record.
Reported incident date
Cloudflare attributes the outage to storage infrastructure underlying Workers KV, including a third-party cloud dependency.
Source reference ↗
Dates and time zones follow the cited report where specified. A report date is distinct from the incident date and from our review.
03 / GOVERNATLAS EDITORIAL ANALYSIS
Make the lesson useful.
These are proposed review and trial activities inspired by the reported event. They are not completed tests or claims that a particular control guarantees prevention.
Map the dependencies of emergency access
A secondary platform dependency can affect authentication and configuration across several products at once. Ask which emergency access paths depend on the same storage or identity service as production. Any alternate access must preserve scoped permissions and an audit trail.
BRING THIS INTO YOUR REVIEW
Open the working guide ↗Rehearse authorized emergency access with the primary configuration dependency unavailable. Record who can act, which credentials and logs remain accessible, and how temporary access is revoked and reconciled afterward.
FROM READING TO A REVIEW YOU CAN OWN
What will you examine next?
A reported failure is a reason to ask a precise question about your own service. It does not establish that your configuration shares the same weakness. Start with the workflow, deployment and dependencies you can identify, then decide which proposed activity is relevant.
For each relevant lesson, name an accountable role, describe the evidence you would request and define an authorized trial before performing it. Keep “not checked” distinct from a recorded observation. If a check reveals a gap, retain its scope and next action rather than converting the observation into a supplier-wide verdict.
Use this portable record in a review, renewal discussion or continuity exercise. A material configuration change, a revised incident account or the completion of an action can trigger your next review. Your entries remain your working notes; publication evidence and your own acceptance decision are separate records.
Use non-sensitive roles and evidence references. Entries stay in this open page and reset on reload; download before leaving. This tool performs no tests and produces no readiness score.
1 unassigned owner · 1 activity not checked
Define a safe, measurable rehearsal
Record the normal result before changing anything. Agree an authorized test boundary, an observable stop condition and who can stop the exercise. Check restored configuration and unfinished work separately. These entries are your plan, not permission to test a service.
04 / LEAVE UNCERTAINTY VISIBLE
What this record does not establish.
This is an attributed review of a preserved provider account, not an independent reconstruction or a finding about current reliability.
Customer-specific losses, exposure and recovery outcomes are not established by these passages. The proposed exercise has not been performed by GovernAtlas.
Geography: The report describes service scope below. No single affected-user location is inferred from infrastructure, company headquarters or routing origin.
05 / THE EVIDENCE RECORD
Sources & editorial review.
Cloudflare service outage June 12, 2025 ↗
Cloudflare · captured 2026-10-17 (UTC)
Inspect preserved provenance
- Source
- c9993d3d-5cef-4a0d-970c-0c168a9a26ed
- Observation
- 3e95d28f-6529-4811-9a56-7df2bf8160a0
- SHA-256
- 1b47abf6348bb54030a4b12751736160e92e55c932e6fffdd9bcc45703010dd8
Reporting and proposed methods by GovernAtlas editorial. Published review: 2026-10-17 (UTC). Revision 1. Preserved source bytes identify the material reviewed; they do not independently verify the provider’s account.
Submit a correction with supporting evidence ↗