Google Cloud's London zones takes a nap, multiple services disrupted

UPDATED Google Cloud customers in Western Europe are waking up to severe disruption affecting multiple services and, as yet, there is no estimated time of recovery.

The europe-west-2-b is one of three local availability zones in the London region, intended to help protect against hardware or regional failures. The downtime began at 0608 UTC, meaning customers need more than a coffee to feel OK about today.

According to Google Cloud's status page: Multiple Google Cloud services are experiencing elevated errors and intermittent network failures in europe-west2 region."

BigQuery Data TransferService, Cloud Filestore, Cloud Run, Google App Engine, Google Cloud NetApp Volumes, Google Kubernetes Engine, and Managed Service for Apache Kafka are all impacted, the tech biz confirmed.

Our engineering team continues to investigate the issue," Google added. We apologize to all who are affected by the disruption."

Techies on Reddit said the interruption was having a cascading affect on multiple suppliers. One said: oh man the classic one zone takes a nap and your non-HA service is in it."

Loads of stuff seems to be down, DNS somewhere," mused another.

Over on the platform formerly known as Twitter, customers weren't any happier - but that's par for the course for people that use Elon Musk's X. Major GCP incident affecting Europe regions, good start to the day," said one.

According to Down Detector, multiple customers are caught up including Lloyds Bank, HSBC, Royal Mail, Rightmove, DPD, BT, Cloudflare, Screwfix and Revolut.

We are currently experiencing a service disruption affecting multiple services. We can confirm that all our customers' money and data are safe. We've been working to fix the issue since it was identified this morning and apologise to anyone affected and for any inconvenience caused," said Revolut.

Workarounds? None for now now," Google said. It plans to update customers at around 0930 UTC. (R)

Updated at 10.18 UTC on October 20, 2026, to add:

Google has updated its status page to say Studio is not impacted by this outage and told customers looking for a workaround: "If feasible, the impacted customer may try to migrate their workload impacted to another available location."