At least 30 major Google Cloud services were suffering performance issues or outright failures on Tuesday morning across its London-based europe-west2 region.
Google Cloud said the incident started at 23:08 PT Monday/07:08 BST Tuesday.
The europe-west2 region comprises three “availability zones.”
The incident seems to have affected all of them.
Major services like its BigQuery managed database, Google Compute Engine, Google Kubernetes Engine, Managed Service for Apache Kafka, and 27 others were impacted.
“Multiple Google Cloud services are experiencing elevated errors and intermittent network failures in europe-west2 region,” it said in a status update.
Its latest update at 10:20, London time, three long hours after the incident began, was detail-thin: “Our engineering team continues to investigate the issue.”
Affected customers appeared to include Revolut, which told its 80 million users on Tuesday that it was “experiencing a service disruption affecting multiple services.”
The bank posted on LinkedIn: “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.”
It did not name Google Cloud as the cause, but is a major customer. (In September 2025 it said it would be “leveraging Google Cloud’s secure, scalable infrastructure to power its rapidly growing global systems, ensuring seamless performance.”)
Revolut may want to urgently review its operational resilience and failovers. Its digital-only banking peer Monzo runs a multi-cloud disaster recovery system, with a GCP-based platform “able to take over from our Primary Platform” in AWS as needed.
Cloud outages: A menu of causes
Back in 2019 multiple US regions of Google Cloud also suffered major issues that it blamed on “network congestion.” These were triggered by a series of compounding issues including two “normally-benign misconfigurations”, and a specific software bug in its cluster management software that escalated, as these things, can.
The incident ultimately saw“BGP routing between specific impacted physical locations withdrawn, “resulting in the significant reduction in network capacity observed by our services… and the inaccessibility of some Google Cloud regions.”
More recently, in 2023, over 90 Google Cloud services were knocked offline in its Paris region after a major data centre incident caused by a water leak that then triggered a fire in a battery room of a co-location data centre. In a very bad hair day indeed for the data centre, its fire suppression system then ran out of water.
Revisiting *that* Google outage: Fire, flooding, (then running out of water) and a “regional Spanner” failure
Other hyperscalers, of course, also periodically suffer incidents. Crypto exchance Coinbase was knocked offline earlier this year after a “thermal incident” in AWS’s US-EAST-1 region knocked EC2 instance and other cloud services offline, whilst in July a bug left customers alarmingly inflated multi-billion service bill estimates.
Earlier this month Azure also suffered an incident global in scale.
It said this was due to a borked update to its networking gateway services. These updates are designed to roll out gradually across deployment stages and redundant gateway instances, allowing service health to be evaluated before updates proceed.
“Before this incident, a temporary deployment restriction had paused operating system updates for a group of networking gateways. When this restriction expired, a large number of gateway updates resumed within a short period, generating a surge in gateway restarts and configuration-retrieval requests. At the same time, a previously deployed change had increased the processing time required for configuration operations handled by a shared regional networking control plane service. The combination of increased request volume and longer processing times overwhelmed the control plane, affecting its ability to process requests reliably.”
More from Google when we have it.
