Google Cloud had a regional outage on 20 October 2026 that ran for 5h 32m, starting at 08:35 UTC. Twelve named services, including App Engine, Compute Engine and Cloud Storage, were listed as affected in the europe-west2 region, and the fault sat with Google's infrastructure, not yours.
Started
08:35 UTC
Duration
Lasted 5h 32m
Source
IsDown
Next time
Google Cloud is degraded. Is your product working?
An incident on their side does not always mean an outage on yours, and the only way to know is to already be watching your own endpoints. Set that up in under a minute and you will be notified the next time your own site is affected. And there will be a next time.
50 monitors for your own websites. No card.
Affected components: Google App Engine, Google Compute Engine, Google Cloud Storage, Google BigQuery, Google Cloud Dataproc, Cloud Data Fusion, Cloud Filestore, Cloud Firestore, Cloud Memorystore, Google Cloud Pub/Sub, Cloud Run, Cloud Spanner, Google Cloud SQL, Google Cloud Composer, Google Cloud Dataflow, Google Kubernetes Engine, Google Cloud Bigtable, Cloud Load Balancing, Cloud Load Balancing (europe-west2), Google Cloud Pub/Sub (europe-west2), Network Connectivity Center, Network Connectivity Center (europe-west2), Speech-to-Text, Speech-to-Text (europe-west2), Storage Transfer Service, Storage Transfer Service (europe-west2), Virtual Private Cloud (VPC), Virtual Private Cloud (VPC) (europe-west2), AlloyDB for PostgreSQL, AlloyDB for PostgreSQL (europe-west2), Apigee, Apigee (europe-west2), BigQuery Data Transfer Service, BigQuery Data Transfer Service (europe-west2), Cloud Data Fusion (europe-west2), Cloud Filestore (europe-west2), Cloud Firestore (europe-west2), Cloud Memorystore (europe-west2), Cloud NAT, Cloud NAT (europe-west2), Cloud Run (europe-west2), Cloud Spanner (europe-west2), Cloud Workstations, Cloud Workstations (europe-west2), Datastream, Datastream (europe-west2), Google App Engine (europe-west2), Google BigQuery (europe-west2), Google Cloud Bigtable (europe-west2), Google Cloud Composer (europe-west2), Google Cloud Dataflow (europe-west2), Google Cloud Dataproc (europe-west2), Google Cloud SQL (europe-west2), Google Cloud Storage (europe-west2), Google Compute Engine (europe-west2), Google Kubernetes Engine (europe-west2), Persistent Disk, Persistent Disk (europe-west2), Private Service Connect, Private Service Connect (europe-west2), VMWare engine, VMWare engine (europe-west2)
What happened?
Google's status page logged one incident on this date, titled "Multiple services are experiencing issues in the europe-west2 region," starting at 08:35 UTC and lasting 5h 32m. The affected list runs to twelve named services on the page, among them Google App Engine, Google Compute Engine, Google Cloud Storage, Google BigQuery, Google Cloud Dataproc, Cloud Data Fusion, Cloud Filestore, Cloud Firestore, Cloud Memorystore, Google Cloud Pub/Sub, Cloud Run and Cloud Spanner, out of 62 components Google tracks in total. That spread points to a shared dependency in that region rather than twelve unrelated failures happening to land on the same day. Google published no updates against this incident, zero in total, so there is no timeline of detection, mitigation or root cause to quote. No user reports were filed during the window, which is unsurprising given europe-west2 is a single region and any disruption would have been concentrated there. The cause is not on the record. Google's own 90 day history shows four incidents with a median duration of 4 hours 23 minutes, so this one ran longer than that median. Over all time Google has logged 961 incidents, averaging 13 a month, which gives this single filing some context: regional incidents of this shape are not rare for Google Cloud. With no updates published, you are left with the title, the start time, the duration and the component list as the only facts Google has put on record for this incident.
Learning
UptimeRobot's own probes, watching compute-global and storage-global from both EU and North America regions, recorded 100% uptime over 24 hours, 7 days and 30 days, and did not register this incident at all. That is not a contradiction. Google's incident was scoped to europe-west2, and global or multi-region probes checking endpoint reachability from outside that region can stay green while customers provisioned specifically into that region see failures across App Engine, Compute Engine, Storage and the rest. This is the general shape of a regional cloud outage: the provider's control plane or networking fails inside one region, global health checks against other regions or global endpoints never see it, and anyone with workloads pinned to that region gets the full impact anyway. Over the last 30 days UptimeRobot logged 2 incidents against Google Cloud, both resolved, with a median duration of 5h 42m, so this kind of regional event is not a one off. If your product runs in europe-west2, a clean dashboard from your own monitoring would have told you nothing was wrong while Google's own services inside that region were down for over five hours. Your monitoring covers your half, UptimeRobot now watches the provider's half too, so next time you know which side broke without guessing.
