Source URL: https://blog.cloudflare.com/cloudflare-service-outage-june-12-2025/
Source: The Cloudflare Blog
Title: Cloudflare service outage June 12, 2025
Feedly Summary: Multiple Cloudflare services, including Workers KV, Access, WARP and the Cloudflare dashboard, experienced an outage for up to 2 hours and 28 minutes on June 12, 2025.
AI Summary and Description: Yes
**Summary:**
This document outlines a significant service outage at Cloudflare on June 12, 2025, affecting critical services reliant on Workers KV due to a failure in underlying storage infrastructure. The incident, lasting over two hours, highlights the impact of dependencies on third-party cloud services and the cascading failures that ensue. Cloudflare’s response and remediation steps emphasize the importance of enhancing resilience against such outages, particularly in cloud computing security contexts.
**Detailed Description:**
The incident report from Cloudflare provides an intricate overview of a major service outage that occurred on June 12, 2025. The failure affected a wide array of critical services and reveals significant insights into infrastructure dependencies, security considerations, and operational resilience.
**Key Points:**
– **Incident Overview:**
– Outage lasted 2 hours and 28 minutes, impacting global Cloudflare customers.
– The main issue stemmed from a failure in the Workers KV underlying storage infrastructure, a crucial service for many other Cloudflare products.
– **Specific Services Affected:**
– **Workers KV:**
– Saw 90.22% of requests failing, impacting service retrieval and configuration delivery.
– **Access:**
– Experienced 100% failure in identity-based logins, highlighting the critical role of Workers KV for application authentication.
– **Gateway and WARP:**
– Disruptions in identity management and device registration due to reliance on Workers KV.
– **Dashboard and API Access:**
– User logins and dashboard functionalities were impaired due to dependencies on multiple services including Turnstile and Workers KV.
– **AI Services:**
– Workers AI requests failed, showing the vulnerability when core dependencies are jeopardized.
– **Nature of the Incident:**
– The failure was not due to a cyber attack but resulted from a third-party vendor outage, causing Cloudflare to reassess its dependency architecture.
– It highlighted a lack of resilience in the service model, where a single point of failure cascaded into widespread operational failure.
– **Remediation Measures:**
– Cloudflare is actively working to improve the redundancy and resilience of their services, specifically:
– Transitioning Workers KV to a more robust infrastructure to prevent future outages.
– Redesigning dependencies to eliminate reliance on single third-party services.
– Implementing robust retry logic and progressive re-enablement for services recovering from similar failures.
– **Implications for Security and Compliance Professionals:**
– Reinforces the need for organizations to evaluate their dependencies on third-party services.
– Stresses the importance of building redundancy into critical services to mitigate risks.
– Provides insights into incident response strategies that can serve as best practices for resilience in cloud computing environments.
Understanding the cascading effects of service dependencies and enhancing infrastructure resilience must become a priority for professionals in cloud computing and security sectors. This incident serves as a critical learning point for improving compliance and best practices around service architecture and incident management.