Google Cloud Outage in London: Revolut, Lloyds, HSBC Hit as Power Failure Stops Banking for Hours
For about six hours on Tuesday 20 October 2026, a power failure in a single London data centre showed how much of Britain's daily banking runs through one company's cloud. Google said its Cloud services suffered an outage "due to a power event" at its europe-west2 region near London, beginning at 0608 GMT. By the time most services recovered around 1210 GMT, customers of the digital bank Revolut had been unable to withdraw cash, transfer money or top up cards; Lloyds and HSBC customers had hit broken banking services; and outage trackers were logging problems at Rightmove, delivery firm DPD and Royal Mail. No money was lost - every bank involved says funds and data are safe - but the morning was a live stress test of the UK's dependence on three giant cloud providers. (Sources: AFP and Reuters reporting via Dawn and CNN, 20-21 October 2026.)
![]()
Photo: Marcin Nowak, CC0 - via Wikimedia Commons
The timeline
| Time (GMT, Tue 20 Oct) | What happened |
|---|---|
| 0608 | Incident begins: "power event" at Google Cloud's London (europe-west2) data centre |
| Morning | Google reports elevated errors and intermittent network failures across multiple Cloud services in the region |
| Morning | Revolut services disrupted - ATM withdrawals, bank transfers and card top-ups; Lloyds and HSBC confirm customer issues |
| ~1210 | Google reports recovery for most workloads in europe-west2 |
| Afternoon | Lloyds says root issues resolved and services returning to normal; Google promises a full incident report in coming days |
Downdetector recorded hundreds of problem reports across UK businesses during the window, including the property website Rightmove, parcel firm DPD and Royal Mail - a reminder that a cloud region hosts far more than banks. Separately, ING Germany reported online-banking login problems the same morning; whether they were connected was not established.
Why one data centre can stop a bank
Modern banks - above all app-only banks like Revolut, which has no branch network to fall back on - rent their computing from hyperscale cloud providers instead of running their own server estates. That is efficient until the region fails: card payments, app logins and transfers can all depend on the same infrastructure. A person familiar with the matter told Reuters that Revolut's outage was directly caused by the Google Cloud failure.
The concentration is structural. Only three hyperscalers - Google Cloud, Microsoft Azure and Amazon Web Services - have the infrastructure to handle the vast data loads UK-scale banks require, University of Surrey cybersecurity professor Alan Woodward noted in coverage of the outage. Last year, a global Amazon cloud outage disrupted gaming, business and transport services for hours. Tuesday's incident renews the same regulatory question: whether "too big to fail" now describes cloud providers as much as banks.
![]()
Photo: Juke Schweizer, CC BY-SA 4.0 - via Wikimedia Commons
What customers should do after an outage like this
- Check before you re-send. Failed transfers during an outage usually either complete late or roll back - sending the same payment again the moment the app returns is how duplicate payments happen. Check the transaction list first.
- Keep an emergency fallback. The oldest advice in banking applied on Tuesday: a second account, a small cash reserve, or a card on a different network turns a provider outage from a crisis into an inconvenience. Migrant workers who receive wages and send remittances through a single app felt this hardest - our money-abroad guides return to this diversification point often.
- Beware the scam wave. Outages are followed, reliably, by phishing messages pretending to be the bank "verifying" accounts. Revolut, Lloyds and HSBC will not ask for your PIN or full password by text or email - today or any day.
![]()
Photo: Dunk, CC BY 4.0 - via Wikimedia Commons
What happens next
Google has said it will publish a full incident report in the coming days, which should establish what the "power event" was and why recovery took six hours. Expect the report to be read closely by the Bank of England and the Financial Conduct Authority, which have been tightening operational-resilience rules for exactly this scenario. For customers, the practical position is unchanged from Tuesday afternoon: services restored, money and data confirmed safe by every affected bank, and a fresh data point in the argument that Britain's financial plumbing deserves the same scrutiny as its banks.
Sources
- AFP via Dawn - "Power outage hits Google Cloud services, disrupting UK banks" (published 21 October 2026): timeline, 0608 GMT start, 1210 GMT recovery, Revolut/Lloyds/HSBC statements.
- Reuters via CNN - "Google Cloud services face outage in London, Revolut services down too" (20 October 2026): europe-west2 network failures, Downdetector reports, ING Germany note.
- Analysis cross-checked against Qatar Tribune (Agencies) coverage of the same incident.
FAQ
Was my money at risk in the outage?
No bank reported any loss of funds or data. Revolut stated explicitly that all customers' money and data are safe; Lloyds said root issues were resolved the same afternoon.
What caused it?
Google attributes the outage to a "power event" at its London data centre and has promised a full incident report with the detailed cause.
How long did it last?
About six hours - from 0608 GMT until Google reported recovery for most services at around 1210 GMT on Tuesday 20 October 2026.
Comments
Post a Comment