So how did a power failure in one zone disrupt services across the region?
Pollar Films
21 October
Synthetic voice (AI).
How it works
Watch 2:57
Preparing
2:57 left
Replay
Watch 2:57
From the story
Google Cloud London outage disrupts Revolut, Lloyds and HSBC services across the UK
Transcript
On Tuesday morning in Britain, Revolut's card payments,
transfers and cash withdrawals were disrupted for hours.
Revolut told the BBC it was the result of an outage at Google's cloud in London.
A cloud is rented computers in data centres.
Google splits its London cloud into 3 zones, in separate data centres.
It says it designs zones
so a power, cooling or network failure in one is unlikely to hit the others.
Its database Spanner, Google says, keeps working if one zone fails.
At 7:08 on Tuesday morning, a power problem caused an outage in zone B.
Google later said it happened at a third-party facility.
But the trouble didn't stay in zone B.
Google's own status page warned of errors across the London region,
and listed 38 of its products as affected.
Revolut told customers about the problem at 7:35.
Google's first public update came 2 hours later.
It named the cause just after noon.
Some Lloyds, Halifax and HSBC customers also reported online banking problems.
Lloyds and HSBC said other organisations were affected, without naming Google.
Google closed the outage at 3 pm, after 7 hours and 52 minutes.
Revolut said its services were fully back that evening.
So how did a power failure in one zone disrupt services across the region?
Google hasn't explained it yet.
It has promised an analysis.
It has explained failures like this before.
July 2022, this same London region.
In a heatwave, the cooling failed in one zone.
At the start, Google accidentally routed its own internal traffic away
from all 3 zones, not just that one.
By Google's own record, that outage lasted almost 39 hours.
April 2023, Paris.
A water leak led to a fire that shut one data centre building.
Google found that copies of Spanner,
the database that runs most of the region's controls,
hadn't been spread correctly across the 3 buildings.
Both times, one zone failed, and the reason it spread was inside Google.
Tuesday's answer could be different.
And the banks?
British rules say a bank must keep each of its most important services within a limit,
even when a supplier fails.
Each bank sets that limit itself,
including a time limit before the disruption causes intolerable harm.
Whether Tuesday broke any of those limits hasn't been publicly established.
Parliament's Treasury Committee has asked regulators what caused this,
and how many firms were affected.
The first answers are due on 4 November.
2 answers are owed.
Google's, on how a failure in one zone disrupted the region.
And the banks', on whether they stayed within their own limits.
More films
2:47
2:47
2:47
Until those are public, the only record of why is an empty box.
19 October
2:56
2:56
2:56
So who ordered it?
17 October
2:58
2:58
2:58
From July, either the tax gets paid, or the drinks change.
14 October
2:54
2:54
2:54
We watched from orbit what happened before, and after.
13 October
2:48
2:48
2:48
Is oil the reason?
12 October
2:47
2:47
2:47
In October, drones hit 3 of Yandex's data centres in 4 days.
11 October
2:58
2:58
2:58
So who decides how much arrives?
10 October
2:52
2:52
2:52
So which missing lessons does that bring back?
9 October
Home
Brief
Live
Threads
Search