What happened
Cloudflare's status page recorded 13 separate incidents between August 7 and August 14, with August 13 and 14 the busiest days at four incidents each. Most were labeled minor, but the cluster touched a wide spread of products: R2 object storage, Durable Objects, Workers KV, Workers AI, and email security, across regions from Istanbul and London to the Eastern US and Queretaro, Mexico. The one major-severity event, on August 12, was an email security disruption tied to a Spamhaus listing that affected outbound delivery. The R2 storage incident on August 7 hit writes for a small number of buckets in eastern North America; most recovered within about a day, but at least one customer reported on Cloudflare's community forum that roughly 67GB of data in an R2 bucket had not been restored days later. Analysis of the streak points to independent subsystem failures rather than one cascading root cause, and reporting on the broader outage cluster notes Cloudflare served as the reverse proxy for about 24 percent of all websites as of July.
Why it matters for your business
Odds are decent your website, DNS, or contact forms pass through Cloudflare even if you never signed up directly, because many hosts and agencies build on it. A streak of minor incidents rarely takes a site fully down, but it can surface as slow pages, failed uploads, or bounced email that gets blamed on your developer or your host.
What to do about it
Three low-effort moves make weeks like this less confusing:
- Ask your web developer or host which services sit in front of your site, and bookmark those status pages before troubleshooting.
- Keep an independent backup of anything stored in a single cloud provider; the unrecovered 67GB report is the cautionary tale.
- If email delivery matters to your sales pipeline, monitor bounces during provider incidents rather than discovering them a week later.