Skip to main content
gcpdown

Is Google Cloud down right now?

Know before it hits your SLAs.

All Services Operational

Data from the official Google Cloud Service Health · independent, not affiliated with Google.

Post-mortems

The latest outage analyses

What actually broke, why, and what it means for your platform - every major Google Cloud incident, explained clearly.

Cloud IAMcritical

The June 2025 Google Cloud Global Outage: How Service Control Crash-Looped

A policy update containing unintended blank fields reached a code path in Service Control - the global layer that checks quota and policy on nearly every Google Cloud API call - that had a null-pointer defect and no feature-flag protection. Service Control crash-looped globally, returning 503s across dozens of products for roughly three hours; us-central1 took longest to recover due to a retry herd.

9 min read

Cloud Load Balancingcritical

The November 2021 Google Cloud Load Balancer Outage: A Config Race Condition

A race condition in the pipeline that propagates Google Cloud Load Balancer configuration caused a corrupt configuration to be pushed globally. Requests to sites fronted by GCLB began returning 404 errors even though the backends were healthy - taking down high-profile sites for roughly two hours until the configuration was rolled back.

7 min read

Google Kubernetes Enginemajor

GKE Control-Plane Outages: When the API Server Fails but Your Pods Keep Running

GKE control-plane incidents are the classic split-brain outage: the Google-managed control plane - the Kubernetes API server, scheduler, and controller manager - becomes unreachable or unhealthy in a region, so kubectl, deployments, autoscaling, and self-healing all stall. Meanwhile the nodes and pods you already had running keep serving traffic, because the data plane runs independently of the control plane. You cannot deploy, scale, or recover from node failures until the control plane returns, but existing workloads generally stay up.

8 min read

Cloud IAMcritical

The December 2020 Google Authentication Outage: When Identity Ran Out of Quota

A migration to a new quota system left Google's central User ID Service with a near-zero storage quota. The identity service could not read the account data it needed, so requests that required authentication failed globally. Anything that had to log a user in - Gmail, YouTube, Docs, and the Google Cloud Console and APIs that authenticate through the same identity layer - returned errors for roughly 47 minutes of core impact.

8 min read

Virtual Private Cloudcritical

The June 2019 Google Cloud Network Congestion Event

A routine maintenance configuration change was applied to a far wider scope than intended, descheduling the network control-plane jobs in several US regions. The network fell back to preserving only high-priority traffic (like the control plane’s own signaling) while starving everything else, so Compute Engine, YouTube, Gmail, and Snapchat degraded severely for about four hours - worst in the US East.

8 min read

Cloud Storagemajor

The March 2019 Google Cloud Storage Outage: An Internal Blob Failure

Degradation in an internal blob-storage service that underpins Google Cloud Storage caused elevated error rates and latency for GCS operations, and for Google’s own products that store objects on the same layer - Gmail and Photos attachments among them - for roughly four hours.

6 min read

Browse the full post-mortem archive →

Guides

Build for the next outage

Evergreen platform-engineering playbooks written from real incident patterns.

Architecture

GCP Load Balancing and Multi-Region Failover

How the global HTTP(S) load balancer routes traffic to the nearest healthy region, how to configure health checks and failover, and its global-dependency risk.

9 min read

Know before your customers do

Instant email alerts the moment a Google Cloud incident is detected - with the affected services and regions, not a vague status tweet.