Google Cloud incident history

Right now: clear, by Google Cloud's own status page, mirrored every five minutes.

6
incidents kept since 27 Feb 2026
1
in the last 30 days
7h 24m
median time to resolve, once posted
0%
resolved within an hour

How far back this goes: Google Cloud's feed exposed its 50 most recent incidents when we began mirroring on 25 September 2026, so this page covers 210 days so far and grows from here. Impact labels (1 major or critical) are Google Cloud's own. We don't compare providers on this page; the windows aren't equal yet.

What our probes saw

No monitor that declares Google Cloud as a dependency was evaluated during these incidents, so there's nothing to add from our side yet. This fills in as more sites behind Google Cloud are watched.

Which parts of Google Cloud the incidents touched

Google Compute Engine
2
VMWare engine
2
Google Kubernetes Engine
2
Google Cloud Dataflow
2
Hybrid Connectivity
2
Virtual Private Cloud (VPC)
2

Every incident we hold, newest first

Source: Google Cloud's public status page at status.cloud.google.com, mirrored every five minutes. Data as JSON: /upstream/gcp/incidents.json. CC BY 4.0.

If your site depends on Google Cloud, Repose holds the page when the cause is upstream. How the hold decision works →