Incident Library
Applied filters FactorChange with a delayed effectOrganisationCloudflareClear allEvery case under the filters, with no sentence; newest first.
Suggested filters Search, and the values found in your words appear here.

Graph

  • Root cause
  • Component
  • Symptom
  • Contributing factor
  • Case

Cases1 case

1 to 1 of 1

  1. Symptoms

    From 21:38 UTC on 21 March 2025, Cloudflare R2 object storage returned errors for 1 hour and 7 minutes: all object writes failed and about 35% of object reads failed globally. R2 global availability alerts fired at 21:45 UTC, at a 2% error budget burn rate.

    Trigger

    During a routine rotation of the credentials the R2 Gateway Worker uses to authenticate with the storage infrastructure, the new credentials were deployed to the Worker of the default environment instead of the production Worker, and the old credentials were then removed from the storage infrastructure at 20:37 UTC.

    Root cause
    Component
    Contributing factor
    Detection

    R2 global availability alerts fired at 21:45 UTC, seven minutes after impact began, at a 2% error budget burn rate, and the R2 engineering team turned to operational dashboards and logs.

    Remediation
    • Deployed the new credentials to the production R2 Gateway Worker, which restored R2 availability
    Action items
    • Add logging tags with the suffix of the credential ID the R2 Gateway Worker uses
    • Require confirmation that the new token ID suffix matches storage infrastructure logs before deleting the old token
    • Run key rotation through the hotfix release tooling, which enforces the environment, instead of manual wrangler commands
    • Write the two-person validation of these changes into the standard operating procedures
    • Extend the closed loop health check system to test new keys, report their status through alerting and confirm global propagation before releasing the gateway Worker
    • Add observability views of upstream success rates that bypass caching
    Lessons

    Because the deletion of the old credentials took effect gradually, availability metrics were a poor way to confirm the change. Cloudflare said the team should have checked directly which token the R2 Gateway service was using to authenticate with the storage infrastructure instead of relying on those metrics.

Check your cluster for this

This case involves Object storage. kubegap audits a Kubernetes cluster for gaps like these, read-only, from Claude Code or Codex; its checks cite public reports like the ones in this library.

By root cause1