Google Cloud’s London Region Is Suffering Errors Across Dozens of Services

Google Cloud says multiple services in its London region, europe-west2, have been hit by elevated errors and intermittent network failures since early on Tuesday 20 October. The problem began at 07:08 BST, according to Google’s Cloud Service Health incident page, and the company has listed 38 affected products, from Compute Engine and Kubernetes Engine to BigQuery and Cloud Storage.

For businesses that run their systems in London, this is a regional disruption rather than a single-product glitch. Google has not said what caused it, and as of 11:44 BST the incident was still open, with the company saying its engineers continue to investigate.

What Google has said so far

Google’s summary is brief: “Multiple services are experiencing issues in the europe-west2 region.” The description adds: “We are experiencing an issue with multiple services in europe-west2 beginning on Monday, 2026-10-19 23:08 PDT.” That is 07:08 BST on Tuesday in the UK.

The symptoms are broad. “Multiple Google Cloud services are experiencing elevated errors and intermittent network failures in europe-west2 region,” Google says. Its latest update, posted at 10:24 BST, says: “Our engineering team continues to investigate the issue.” It promises another update by 04:00 PDT, which is 12:00 BST, and adds: “We apologize to all who are affected by the disruption.”

The incident appeared on the status page at 09:35 BST, about two and a half hours after the start time Google gives. That first notice said there was no workaround “for now”. By 10:24 BST Google had added one, and noted that “Looker Studio is not impacted by this outage.”

Dozens of products, one region

The list of affected services shows how much of Google’s platform sits in a single region. Alongside core computing products such as Compute Engine, Google Kubernetes Engine, Cloud Run and App Engine, the status page names databases including Cloud SQL, Cloud Spanner, AlloyDB for PostgreSQL, Firestore and Bigtable. It also lists BigQuery, Cloud Storage, Persistent Disk, Pub/Sub, Dataflow and several Memorystore products.

Networking is affected too. Cloud Load Balancing, Cloud NAT, Virtual Private Cloud, Private Service Connect and Network Connectivity Center all appear on the list, as do Apigee and Managed Service for Apache Kafka. Google’s status page records only one affected location: London (europe-west2).

Google has not said which customers are affected, or how many. Its advice is to move work elsewhere where possible. “If feasible, the impacted customer may try to migrate their workload impacted to another available location (zone or region),” the status page says. Google does not say how many customers can do that, and the advice is qualified by “if feasible”.

Cloud outages have very different causes. TSN has previously reported on drone strikes that left Yandex Cloud in “limited mode”, a very different incident in which the cause was known. In Google’s case, the cause has not been disclosed.

Our read

This is TSN’s analysis. A disruption that touches 38 products in one region is a reminder that “in the cloud” still means a physical place, and that resilience depends on how many places a business uses. The key questions now are when Google restores service, and whether its eventual incident report explains what failed.

Sources

• Google Cloud Service Health: Multiple services are experiencing issues in the europe-west2 region (incident Xs2XTHzAVC9YnafnPyzj)

Related stories

• Drone Strikes on Three Yandex Datacenters Leave Yandex Cloud in “Limited Mode” and Yandex Pay Offline, The Register Reports