What happened most recently, on one time axis: our own probe readings by surface, how many people reported a problem, and what Google Cloud Platform's own status page declared. Below it, any public chatter we saw about Google Cloud Platform and the extra probe it triggered.
The last 24 hours on one axis: what our probes read for each surface we check, how many people reported a problem, and what Google Cloud Platform's own status page declared. Three records side by side; none of them changes another.
Our probes, web
Our probes, api (primary)
Unverified user reportsNo reports about Google Cloud Platform in the last 24 hours, which is not evidence that nothing is wrong.
Google Cloud Platform's status pageNo incident declared in the last 24 hours.
24h ago18h ago12h ago6h agonow
Each check cell is the worst reading across every region in that quarter hour: one region that did not answer colours the cell, never an average. An amber cell is a reading that answered, but at three times or more its 7-day median for three checks running: slow is not down, and we say which. A filtered reading stays neutral, because a refused check is not a failed check. Report bars count reports as submitted; we do not check who sent them, and they never change our reading. The status-page lane is Google Cloud Platform's own declaration, shown as they made it.
Checks passing is the checks that passed, divided by every check we attempted, per region. Not interpolated, not smoothed, and never computed for a region with zero recorded samples.
Google Cloud Platform's own incident history, taken from their public status feed. This is their account of what happened, not our check reading.
Multiple services were experiencing issues in the europe-west2 region.Minor incident
Oct 20, 2026, 6:00 AM UTC to Oct 20, 2026, 12:08 PM UTC (6h 8m)resolved
their latest update (Nov 4, 2026, 9:15 PM UTC): # Incident Report
## Summary
On Monday, 19 Oct 2026 at 22:53 US/Pacific (Tuesday, 20 Oct 2026, 06:53 BST), a data center facility that hosts europe-west2-b, a zone within the europe-west2 cloud region, experienced an external electrical power disruption. This resulted in service …
Google Cloud Storage (GCS) customers experienced elevated latencies and error rates when performing upload or write operations.Minor incident
Oct 8, 2026, 11:00 AM UTC to Oct 9, 2026, 4:46 PM UTC (1d 5h)resolved
their latest update (Oct 14, 2026, 7:15 AM UTC): ## Incident Report
## Date/Time of the Issue (All time US/Pacific)
**Incident First Occurrence**
Incident Start: 08 October 2026 04:00
Incident End: 08 October 2026 16:30
Duration: 12 hours, 30 minutes
**Incident Recurrence**
Recurrence Start: 09 October 2026 04:05
Recurrence End…
Multiple products in us-central1-b are experiencing network service degradation.Minor incident
Sep 1, 2026, 2:42 PM UTC to Sep 1, 2026, 6:52 PM UTC (4h 10m)resolved
their latest update (Sep 29, 2026, 4:09 PM UTC): ## Addendum to Incident Report
This addendum extends the Detailed Description of Impact from the previous message. Though only two clusters in a datacenter in us-central1-b and us-central1-f experienced network isolation, a few regional products with a dependency on the affected …
We are investigating an issue where customers may experience timeouts, service degradations, errors, and elevated latencies across multiple products in the us-west1 region.Partial outage
Aug 20, 2026, 3:40 PM UTC to Aug 20, 2026, 7:20 PM UTC (3h 40m)resolved
their latest update (Aug 27, 2026, 9:45 PM UTC): # Incident Report
## Summary
On Thursday, 20 August 2026, from 08:00 to 10:22 US/Pacific (15:00 to 17:22 UTC), multiple Google Cloud services in the us-west1 region experienced elevated latency, provisioning failures, increased error rates, and widespread service degradations for…
Google Cloud VMware Engine (GCVE), Google Cloud NetApp Volumes, and Bare Metal Solutions (BMS) services are experiencing a service outage in europe-west4-a due to a cooling failure.Minor incident
Jul 15, 2026, 11:57 PM UTC to Jul 16, 2026, 12:25 PM UTC (12h 28m)resolved
their latest update (Jul 25, 2026, 1:16 PM UTC): ## \# Incident Report
## \#\# Summary
On Wednesday, 15 July 2026, Google Cloud VMware Engine (GCVE), Bare Metal Solution (BMS), and Google Cloud NetApp Volumes (GCNV) experienced service interruptions for a total duration of 14 hours, 55 minutes.
The root cause for this outage is…
Google Cloud VMware Engine (GCVE) Stretched Cluster customers are experiencing zonal outages impacting network connectivity across multiple regions.Minor incident
Jul 14, 2026, 5:00 PM UTC to Jul 15, 2026, 3:40 AM UTC (10h 40m)resolved
their latest update (Jul 24, 2026, 7:10 AM UTC): ## Incident Report
## Summary
On Tuesday, 14 July 2026 10:00 PT, Google Cloud VMware Engine (GCVE) Stretched Cluster customers in the australia-southeast2 and europe-west3 zones experienced inter-site communication failures.
The disruption was traced to a network configuration up…
Network traffic to Google Cloud originating from Delhi, Chennai, Mumbai and surrounding areas is experiencing intermittent periods of elevated latency and possible packet loss.Minor incident
Jun 5, 2026, 7:00 AM UTC to Jun 26, 2026, 7:00 PM UTC (21d 12h)resolved
their latest update (Jun 29, 2026, 11:06 PM UTC): **Summary**
Network traffic to Google Cloud originating from Delhi, Chennai, Mumbai and surrounding areas experienced intermittent periods of elevated latency and possible packet loss.
**Description**
Traffic rerouting from the impacted Delhi facility caused a subset of Hybrid Co…
Vertex AI Gemini API customers experienced increased error rates when accessing the global endpoint.All systems operational
Feb 27, 2026, 12:37 PM UTC to Feb 27, 2026, 2:35 PM UTC (1h 58m)resolved
their latest update (Mar 9, 2026, 5:25 AM UTC): # Incident Report
## Summary
On Friday, 27 February 2026 at 04:37 US/Pacific, customers using Vertex AI Gemini API models experienced increased error rates. Impacted services included Google Cloud Support, Agent Assist, Vertex Gemini API and Dialogflow CX in US regions and the gl…
These entries are Google Cloud Platform's own declarations, taken from their public status feed, shown separately from our own check readings. Their page publishes what they choose to publish: an incident missing here means they did not declare one, not that nothing happened, and an incident here is their account, not our measurement. Neither record ever changes the other.
Google Cloud Platform's own status feed works, so its declared incidents are the record and our probe events are not listed or counted. Our check results by region are above, as a reading beside the statement.