Fri Jun 13 03:20:00 UTC 2025: **Summary:**

On June 12, 2025, Cloudflare experienced a 2 hour and 28 minute service outage due to a failure in the underlying storage infrastructure of its Workers KV service, a critical component for many of its products. This infrastructure relies partly on a third-party cloud provider who experienced an outage that directly impacted Cloudflare’s KV service. The outage affected services including Workers KV, WARP, Access, Gateway, Images, Stream, Workers AI, Turnstile and Challenges, AutoRAG, Zaraz, and parts of the Cloudflare Dashboard, globally impacting customers. While not a security breach and with no data loss, the incident exposed a vulnerability in Cloudflare’s architecture. Cloudflare is now taking steps to improve service resiliency, focusing on reducing dependencies on external storage infrastructure, improving recovery capabilities, and implementing tools for progressive service restoration during outages.

**News Article:**

**Cloudflare Hit by Major Outage, Affecting Key Services**

*San Francisco, CA – June 13, 2025* – Cloudflare, a leading internet infrastructure and security company, suffered a significant service outage on June 12, 2025, impacting a broad range of its services for over two and a half hours. The company confirmed that the outage stemmed from a failure in the storage infrastructure supporting its Workers KV service, a foundational component for many Cloudflare products.

The disruption, which began at [Insert Start Time based on duration of 2 hr 28 minutes], affected key services including Workers KV, WARP, Access, Gateway, Images, Stream, Workers AI, Turnstile, AutoRAG, and portions of the Cloudflare Dashboard. Cloudflare reports that services like Magic Transit and Magic WAN, DNS, cache, proxy, and WAF were not directly impacted.

According to Cloudflare, the root cause was a third-party cloud provider experiencing an outage, directly impacting the availability of their KV service. “We’re deeply sorry for this outage,” Cloudflare stated in a post-incident report. “This was a failure on our part, and while the proximate cause (or trigger) for this outage was a third-party vendor failure, we are ultimately responsible for our chosen dependencies and how we choose to architect around them.”

While no data loss or security breach was reported, the incident highlighted a reliance on external infrastructure that created a single point of failure. Cloudflare stated that it is now expediting efforts to improve the resiliency of its services, including reducing dependencies on external storage, enhancing recovery capabilities, and implementing tools for phased service restoration during future incidents. These include migrating to their own infrastructure for KV, specifically Cloudflare R2.

The outage comes as a blow to Cloudflare, which provides critical services to businesses of all sizes. The company has promised to take immediate action to prevent similar incidents in the future and is working diligently to improve its service resiliency.

Read More