Cloudflare says new R2 Gateway credentials were deployed to a development instance instead of production before the old credentials were removed.
Cloudflare · inspect the source ↗INCIDENT BRIEF / SERVICE OUTAGE
Cloudflare R2 credential incident: verify production use before revocation
A successful secret deployment is not proof that production consumers use it. Require an environment-specific check before revoking the previous credential, with a bounded overlap and rollback plan. Do not retain an old credential indefinitely merely to avoid testing rotation. Use the preserved provider account below to distinguish reported facts from the proposed review exercise.
01 / SOURCE-ATTRIBUTED REPORTING
What the evidence establishes.
The provider reports all object writes and approximately 35% of reads failed globally during the incident window.
Cloudflare · inspect the source ↗Cloudflare says successful in-flight mutations were persisted and no data loss or corruption occurred.
Cloudflare · inspect the source ↗02 / KEEP THE SEQUENCE
A dated record.
Reported incident date
Cloudflare says new R2 Gateway credentials were deployed to a development instance instead of production before the old credentials were removed.
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.
Make rotation completion an observed state
A successful secret deployment is not proof that production consumers use it. Require an environment-specific check before revoking the previous credential, with a bounded overlap and rollback plan. Do not retain an old credential indefinitely merely to avoid testing rotation.
BRING THIS INTO YOUR REVIEW
Open the working guide ↗Rotate a test credential through a representative production-like consumer. Confirm effective credential identity, successful read and write requests, old-key rejection and audit events in that order; record the maximum overlap allowed.
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 incident on March 21, 2025 ↗
Cloudflare · captured 2026-10-17 (UTC)
Inspect preserved provenance
- Source
- dc953ccd-41da-4e34-9aae-cde744ea0257
- Observation
- 092e3c27-fc4e-41c3-9b9b-c2bdca9810a5
- SHA-256
- d454badd4e56f5167905cf6a1f97a74d4f6908df7c372f4186fce6faad3d7005
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 ↗