Google Cloud outage takes down Revolut, Lloyds, and HSBC
- Published
Revolut, Lloyds, HSBC, and Bank of Scotland experienced service disruptions tied to a Google Cloud problem in London. Revolut later told customers that their money and data were safe while card payments, transfers, and ATM withdrawals were affected.
Key claims & sources
What it means
Google Cloud sits inside the infrastructure layer that many financial apps and banks rely on for everyday services. When a regional cloud problem hits a center such as London’s europe-west2, the visible result is often not a website error alone but broken payments and account access across multiple firms at once. Revolut, Lloyds, HSBC, and Bank of Scotland all appearing in the same incident shows how much of modern retail banking now depends on shared cloud plumbing.
For people using Revolut and the affected banks, the immediate change is simple: payment flows and cash access can stop working even when balances remain intact. Revolut’s message that funds and data were safe is meant to calm users, but it also underlines that access to money and the custody of money are no longer the same thing in day-to-day fintech operations. Banks and fintechs that build on major cloud providers have to plan for disruptions that are outside their own systems and customer interfaces.
The wider issue is concentration risk. A single cloud region outage can interrupt several branded financial services at once, which cuts against the idea that digital finance should be distributed and resilient. The repeat of a cloud-linked banking outage one year after the AWS incident involving Coinbase, Robinhood, and Lloyds Bank keeps that trade-off in view for both regulators and operators.
Market reaction i
The total crypto market rose 1.1% in the 4 hours after the first headline, after a flat 2 hours before.
48 prices, one every 30 minutes
Coverage timeline
Every piece in order, with the time its news medium declares — if it is not believable we use ours and say so — and what it added to what was already known at that point. Arriving first is not the same as adding something.
Other recent incidents
| When | What happened | Figure |
|---|---|---|
| 2 days ago | Initia · Private key leak incident | $615k |
| 3 days ago | Arcus · Accounting bug incident | $2.2M |
| 3 days ago | Ankr Bridge · Cross-Chain Message Spoofing incident | $304.5k |
| 4 days ago | LNbits · Unknown incident | no figure in dollars |
| 4 days ago | ACryptoS · Missing Input Validation incident | $665.4k |
4300 incidents stored