Google has confirmed that its services are fully operational following a major global outage linked to a failure within its cloud infrastructure. The disruption, which began late on June 12, affected a wide range of both Google-owned and third-party services, including Gmail, Google Search, Drive, Calendar, and third-party platforms such as Spotify and Discord that depend on Google Cloud.
According to Google’s Cloud status page, the root cause of the outage was traced to an issue within its identity and access management (IAM) system. The misconfiguration caused cascading failures across critical infrastructure, resulting in elevated error rates and in some cases, complete service unavailability across multiple regions.
The outage began early Thursday and quickly escalated, impacting core tools in the Google Workspace suite like Meet, Lens, and Calendar. The disruption extended beyond Google’s ecosystem, affecting external platforms reliant on the company’s backend services. Users across the globe reported difficulties accessing basic services, highlighting how deeply intertwined many digital applications have become with cloud providers like Google.
Google engineers issued multiple updates through their status page, confirming that mitigation efforts were underway throughout the incident. By the end of June 13, all affected services were reported as fully restored. In a final statement, the company noted, “Our engineers have identified the root cause and have applied appropriate mitigations. All services are fully recovered. We will publish a detailed analysis once our internal investigation is complete.”
Though resolved, the outage underscores the vulnerability of major cloud-dependent platforms to internal configuration failures—particularly those tied to security and identity systems. IAM systems are critical to authenticating and granting access to users and services; failures in this layer can result in broad-based access denial, even if the underlying services themselves are technically functional.
This incident adds to a growing list of recent cloud service disruptions that have prompted questions about redundancy, transparency, and communication during service failures. For businesses and developers relying on Google Cloud, the event serves as a reminder of the need to build contingency plans even when using infrastructure from industry leaders.
While full operational status has been restored, Google has committed to publishing a post-incident analysis in the coming days, which will likely offer more insights into what triggered the misconfiguration and what steps are being taken to prevent similar disruptions in the future.
