Cloudflare experienced a 2-hour 28-minute outage due to a failure in its Workers KV service, impacting services like Workers KV, WARP, Access, and Gateway.
Google Cloud suffered issues that cascaded across multiple services, including Search, Meet, Nest, and Workspace, with some services taking up to three hours to recover.
The outages highlighted the fragility of the internet ecosystem and the reliance of many services on a few major hosting providers.
Both Cloudflare and Google Cloud apologized for the disruptions and are taking steps to improve the resiliency of their services.
The Cloudflare outage was attributed to a third-party vendor failure, while Google Cloud cited issues with its API management system.
Why this matters: These outages demonstrate the potential impact of disruptions to major cloud service providers. Businesses and individuals should consider strategies for mitigating the risk of such outages, such as using multiple providers or having backup plans in place.
The June 12, 2025, internet outage was a stark reminder of the interconnectedness and potential vulnerabilities of modern online infrastructure. The outages at Cloudflare and Google Cloud, two major players in the cloud services market, had a cascading effect, impacting numerous downstream services and users.
Cloudflare Outage:
Cloudflare's outage, which lasted 2 hours and 28 minutes, was caused by a failure in the underlying storage infrastructure used by its Workers KV service. This service is a critical dependency for many Cloudflare products, including Workers KV, WARP, Access, Gateway, Images, Stream, Workers AI, Turnstile and Challenges, AutoRAG, Zaraz, and parts of the Cloudflare Dashboard. The failure was traced to a third-party cloud provider, highlighting the risks associated with relying on external dependencies.
Google Cloud Outage:
Google Cloud's outage affected a wide range of services, including Search, Meet, Nest, and Workspace. The issues began around 2 p.m. Eastern and took approximately three hours to resolve for most services. Google Cloud attributed the outage to issues with its API management system. The outage also impacted other services like Discord and Spotify, which rely on Google Cloud infrastructure.
Impact and Response:
Both Cloudflare and Google Cloud apologized for the disruptions and are taking steps to improve the resiliency of their services. Cloudflare is working to improve the redundancy within Workers KV’s storage infrastructure, while Google Cloud is investigating the root cause of the API management system issues. These outages underscore the importance of redundancy, robust monitoring, and incident response planning for cloud service providers and their customers.
How to Prepare:
Diversify Cloud Providers:: Distribute your services across multiple cloud providers to reduce the risk of a single point of failure.
Implement Redundancy:: Ensure your critical applications have redundant systems in place to maintain uptime during outages.
Monitor Service Health:: Use monitoring tools to track the health and performance of your cloud services and dependencies.
Develop Incident Response Plans:: Create detailed plans for responding to outages, including communication strategies and recovery procedures.
Who This Affects Most:
Businesses relying on cloud-based applications and services
Individuals using Google services like Gmail, Drive, and Meet
Developers building applications on Cloudflare and Google Cloud platforms
What caused the Cloudflare outage?
The Cloudflare outage was caused by a failure in the underlying storage infrastructure used by its Workers KV service, which relied on a third-party cloud provider.
What services were affected by the Google Cloud outage?
The Google Cloud outage affected a wide range of services, including Search, Meet, Nest, and Workspace.
How long did the outages last?
The Cloudflare outage lasted 2 hours and 28 minutes, while the Google Cloud outage took approximately three hours to resolve for most services.
What are Cloudflare and Google Cloud doing to prevent future outages?
Both Cloudflare and Google Cloud are taking steps to improve the resiliency of their services, including improving redundancy and investigating the root causes of the outages.
The June 12, 2025, outages at Cloudflare and Google Cloud highlight the importance of cloud service reliability.
Businesses and individuals should consider strategies for mitigating the risk of cloud service outages, such as diversifying providers and implementing redundancy.
Cloud service providers are taking steps to improve the resiliency of their services, but outages can still occur.
Monitoring service health and having incident response plans in place are crucial for minimizing the impact of outages.
Do you think these outages will lead to changes in how businesses approach cloud infrastructure? Share your thoughts in the comments below!
Share this article with others who need to stay ahead of this trend!
Oracle has announced record-breaking financial results for both the fourth quarter and the full fiscal year 2026, largely propelled by an un...
Prosus, a global consumer internet group, is collaborating with Amazon Web Services (AWS) in a three-year deal to scale its artificial intel...
On October 29, 2025, a significant outage struck Microsoft Azure, impacting numerous services and users. The disruption affected key platfor...
Nebius Group (NBIS) is projected to achieve positive adjusted EBITDA in the second half of 2025, driven by growing revenues, global expansio...
⚠ Disclaimer: Yanuki provides article summaries and links for reference only. Yanuki does not endorse, verify, or guarantee the accuracy of third-party sources. Please review original sources and verify information independently. Managed by the Yanuki Data Engine. Full Disclaimer