Cloudflare Outage June 2025: What Went Wrong?
On June 12, 2025, Cloudflare experienced a major global service outage that disrupted several of its core services for approximately 2 hours and 28 minutes. The incident impacted various applications and platforms across the internet, highlighting the deep interconnectedness of today’s digital infrastructure and the risks posed by third-party dependencies.
What Happened?
Around 18:47 UTC, Cloudflare began detecting widespread issues across several of its services. This included failures in Workers KV—a key-value storage service essential for Cloudflare Workers—as well as Durable Objects, Workers AI, WARP, Access, Stream, and parts of the Cloudflare dashboard. Many customers and users encountered access issues, slow performance, or complete service interruptions.
The root cause was traced to a backend failure in the cold storage system powering Workers KV. This storage system, provided by a third-party cloud vendor, suffered an outage that rendered Cloudflare’s edge data services inaccessible. As a result, other dependent services began to fail in a cascading manner.
Notably, this outage was not caused by a cyberattack or security breach. No user data was lost or compromised. Cloudflare emphasized that the fault originated from external infrastructure, but took full responsibility for the disruption, acknowledging its reliance on a single cloud storage vendor as a key architectural vulnerability.
Timeline of Events
- 18:47 UTC – Issues detected across multiple services.
- 19:02 UTC – Workers KV confirmed offline; dependent services affected.
- 20:32 UTC – Partial restoration of KV begins.
- 20:57 UTC – Most services return to operational status.
- 21:31 UTC – Incident fully resolved.
Services Affected
The following services experienced full or partial degradation during the outage:
- Workers KV
- Durable Objects
- Workers AI
- Cloudflare Access
- WARP
- Browser Isolation
- Stream
- AI Gateway
- AutoRAG
- Partial outages in the Cloudflare Dashboard and APIs
Despite the disruption, Cloudflare’s core infrastructure—including DNS, caching, proxy, and security services—continued to operate normally.
Industry-Wide Impact
This outage was made worse by a problem with Google Cloud earlier that same day that affected services like OpenAI, Spotify, and Discord. The two events had nothing to do with each other, but the fact that they happened at the same time caused misunderstanding among users and showed how vulnerable the digital world is to problems with cloud technology.
Looking Ahead
Because of this, Cloudflare has promised to make big changes to the way its system is built. Some of these are rewriting Workers KV to support multi-vendor storage redundancy, making service separation stronger to stop failures from spreading, and improving fallback methods.
Unfortunately, the downtime on June 12 is a stark warning that even the best systems can fail. It makes the need for robustness, design variety, and open communication even stronger, especially in a digital world based on shared cloud technology.
Disclaimer
The information presented in this blog is derived from publicly available sources for general use, including any cited references. While we strive to mention credible sources whenever possible, Web Techneeq –Best Web Design Company in Mumbai does not guarantee the accuracy of the information provided in any way. This article is intended solely for general informational purposes. It should be understood that it does not constitute legal advice and does not aim to serve as such. If any individual(s) make decisions based on the information in this article without verifying the facts, we explicitly reject any liability that may arise as a result. We recommend that readers seek separate guidance regarding any specific information provided here.