# Google Cloud's status page was the 51st to report its own outage

> A power cut in one London zone took down databases, payments and shipping across Europe on 20 October. Replay the day as 70 companies' status pages told it.

20 October 2026

At 06:08 UTC on Tuesday 20 October, a power event knocked out part of Google Cloud's europe-west2-b zone in London. Google's incident lists 38 products, from Compute Engine to Cloud SQL and BigQuery, and ends at 14:00.

Google's status page said nothing about it until 08:35.

We follow about 9,800 official status pages. That day, 70 of them reported a problem in words that point back to London. Here's the day as they told it:

<div data-embed="london-replay">

![70 status pages as icons, lit when each first reported the outage. At 08:35 UTC, when Google Cloud's page first posted, 50 of them already had.](https://stackpulse.app/blog/google-cloud-london-outage/replay.png)

</div>

## Two and a half hours of silence

Kagi posted "europe-west2 outage" at 06:06, two minutes before the start Google later gave. 16 pages had posted by 07:00, 36 by 08:00, and 50 by the time Google's first update came at 08:35, or 01:35 in California. That update spoke of "elevated errors and intermittent network failures". The power event was only named at 11:12.

<div data-embed="london-first">

![The ten first status pages to report it, from Kagi at 06:06 UTC, 2 h 29 min before Google's page, to Hostinger at 06:49.](https://stackpulse.app/blog/google-cloud-london-outage/first.png)

</div>

## How it spread

<div data-embed="london-web">

![A radial tree with Google Cloud London in the middle. 25 status pages name Google Cloud directly. Dashed branches lead to London or UK regions (15 pages), Revolut (19 partners, among them Tink's pages for four countries and Wero, which Mollie and orderBilly name in turn) and DPD UK (11 shipping tools).](https://stackpulse.app/blog/google-cloud-london-outage/web.png)

</div>

- **25 named Google Cloud.** Databases and queues other companies run on, like Elastic Cloud, Confluent Cloud, Redis, Aiven and Neo4j Aura, and products built on top, like Kagi and Atlan.
- **15 named London or the UK.** Kinsta's and Cloudways' London data centres, Bloomreach's UK region, Akeneo's London customers.
- **19 named Revolut**, which news reports put among the companies hit: open banking in four countries through Tink, card payments through Curve, even the UK government's GOV.UK Pay. Some went a step further: Mollie and orderBilly named Wero, which named Revolut.
- **11 named DPD UK**, also reported hit. ShipStation, Shippo, Veeqo and eight more couldn't create its labels.

A problem at the same time is a clue, never proof. But for these companies' customers, the outage had a bank's or a parcel carrier's name on it, not Google's.

## What they called it

<div data-embed="london-words">

![What the 70 status pages called it in their incident titles: Google or GCP 21, Revolut 19, UK 12, europe-west2 11, DPD 11, London 7, Europe 4, and cloud provider, third party or upstream 5.](https://stackpulse.app/blog/google-cloud-london-outage/words.png)

</div>

Only 21 of the 70 said "Google" or "GCP". 30 named a bank or a parcel carrier instead. If you watch your cloud's status page alone, most of this outage looked like someone else's.

## Google closed at 14:00. Many didn't

<div data-embed="london-lanes">

![One bar per status page from its first report to its all clear, over Google's incident from 06:08 to 14:00 UTC. Most bars end after 14:00, and 12 were still going at midnight.](https://stackpulse.app/blog/google-cloud-london-outage/lanes.png)

</div>

Google closed its incident at 14:00. Of the 58 pages that finished that day, 43 finished later: Redis at 17:24, Sourcegraph at 17:44, Elastic Cloud at 20:11. And 12 were still reporting a problem when the day ended, 8 of them Revolut's partners.

## What it shows

Your vendors' status pages can know before your cloud's does, here by more than two hours. The outage that reaches you may not say "Google" at all; this time it more often said "Revolut" or "DPD". And the cloud's all clear isn't yours: clusters restart, queues catch up, and partners take their time.

Every one of the 70 is on [the day's outage page](https://stackpulse.app/outages/2026-10-20), with what it said.

<small>We counted a status page when its own words on 20 October named Google Cloud, a London or UK region, Revolut or DPD UK. Pages with problems in the same hours that didn't say why are left out. Times are UTC, when each page first said it.</small>
