logo

Cloudflare incident on March 21, 2025

ID: fc4baa6a-f000-50f5-89e1-fe18429db514

STIX ID: report--fc4baa6a-f000-50f5-89e1-fe18429db514

Feed Name: Cloudflare Blog

Date Published: 2025-03-25

Date Updated: 2026-04-27

Author: Phillip Jones

...
...

Cloudflare reports a 1h07m outage (21:38–22:45 UTC, Mar 21, 2025) affecting R2 and dependent services after new storage credentials were mistakenly deployed to a non‑production Worker during key rotation, leaving production unable to authenticate; this caused 100% write failures and ~35% read failures globally (with varied downstream impact to Cache Reserve, Images, Stream, Vectorize, Billing, etc.), but no data loss. Root cause was omission of the --env parameter in wrangler commands; service recovered after deploying the correct credentials, and Cloudflare committed to improved logging/validation, enforced deployment tooling, stronger SOPs, and enhanced observability and health checks.

Your team is not currently subscribed to this feed. You must subscribe to it in order to see this post.