Key Takeaways
- Google Cloud reported a power event affecting its London region on October 19 and 20, 2026.
- The disruption caused service unavailability and intermittent errors across affected cloud services.
- Google marked the incident closed but said further analysis would follow its internal investigation.
Google Cloud Restores London Services After Power Disruption Affects Multiple Platforms
Google Cloud said a power event caused an outage in the europe-west2-b zone of its London region, disrupting multiple services. Its status page reported that services were recovering for most workloads, while the final update said a very small number of customers could still be affected.
What Happened in Google's London Region?
According to Google's official Cloud Service Health incident report, the disruption affected the europe-west2-b zone in its London region. Google documented service unavailability in that zone, while some services across the wider europe-west2 region experienced elevated errors and intermittent network issues.
The event began at 23:08 Pacific time on October 19, 2026, and continued into October 20. Google's status record lists the incident as ending at 07:00 Pacific time on October 20, a span of seven hours and 52 minutes.
At 05:44 Pacific time, Google said it had seen recovery for most workloads in europe-west2 from 05:10. In its 07:03 update, the company said the issue had been mitigated for most customers but was believed to be affecting a very small number. Google said it would publish an analysis once its internal investigation was complete.
Why Cloud Disruptions Matter
Google's incident page listed a broad group of affected products, including Compute Engine, Google Kubernetes Engine, Cloud Storage, Cloud SQL, BigQuery, Cloud Run and Virtual Private Cloud. The page also listed services such as AlloyDB for PostgreSQL, Cloud Spanner, Cloud Pub/Sub and Persistent Disk.
The reported impact was limited to the London region and, in particular, included unavailability in europe-west2-b. Google said some services elsewhere in europe-west2 could experience elevated errors and intermittent network issues. It separately noted that Looker Studio was not affected.
For customers able to do so, Google's stated workaround during the incident was to migrate affected workloads to another available zone or region. Earlier updates said customers might not yet be able to create new workloads while recovery work was under way.
TwikUp's Perspective
Google's updates show that the reported effects differed by location and workload: services were unavailable in one zone, while the wider region saw intermittent errors and network issues. The company's recommended workaround focused on moving affected workloads to another available location where feasible.
The status page identifies a power event as the cause of the outage in europe-west2-b, but it does not provide a more detailed technical explanation. Google's planned incident analysis may provide further information after its internal investigation is complete.
Until that analysis is published, the documented power event is the appropriate explanation, without speculation about the underlying equipment failure or wider consequences.