A power failure at one of Google Cloud’s London data centre zones knocked out banking apps, card payments and public services across the UK on Tuesday, October 20, 2026. Revolut, Lloyds, Halifax and HSBC customers were among those who couldn’t log in, pay or move money for several hours. Services have since been restored, and the banks say customers’ money and data were never at risk. Below is what happened, who was affected, what you can claim if the outage cost you money, and how to make sure the next one doesn’t leave you stuck at a till.
What happened in the Google Cloud outage?
Google said the disruption was caused by a “power event” at a third-party facility in its europe-west2 cloud region, the London-based cluster of data centres that serves customers across the UK and Europe. The problem was traced to one of the region’s smaller zones, europe-west2-b, according to BBC News.
The incident began just after 6 a.m. London time, The Journal reported, citing Google’s service health updates. Google’s own Cloud status dashboard lists the incident as closed, with a total duration of 7 hours and 52 minutes and more than 35 Google Cloud products affected in the region.
Recovery came in stages. Google said most workloads were recovering just after midday, and The Guardian reported that services were back for most customers by around 3 p.m. Some apps that depend on Google Cloud took longer to fully catch up. Google has said it will publish an analysis of the incident once its internal investigation is complete.
Which banks and services were affected?
Because so many companies run their apps and back-end systems on the same cloud provider, one failure spread to dozens of seemingly unrelated services. Reports included:
- Revolut: sign-up, sign-in, card payments, transfers, ATM withdrawals and crypto services were disrupted. More than 1,500 reports of problems were logged on an outage tracker shortly after 8 a.m. BST, per the BBC. As late as 5 p.m., Revolut’s status page still showed only six of 27 listed services working normally, according to The Guardian.
- Lloyds and Halifax: some customers couldn’t log in to the app or online banking. Halifax confirmed the login problems on X.
- HSBC: customers reported trouble getting into their accounts. The bank later said its services had “returned to normal.”
- Courts: the Cloud Video Platform used for remote hearings in England and Wales failed throughout the morning, which is believed to have delayed several hearings.
- Other services: Downdetector showed problem reports for Rightmove, DPD, Royal Mail and NHS England, Reuters reported. Royal Mail said letter and parcel deliveries weren’t affected.
The human side was very ordinary and very frustrating. One Revolut customer from Glasgow told the BBC she couldn’t pay for parking at a shopping centre because her account wasn’t working, and couldn’t see a payment a relative had sent her.
Is my money safe after the Revolut outage?
Yes. An outage like this is an access problem, not a problem with your balance. Revolut said “all our customers’ money and data are safe,” and later told the BBC that services were “fully restored” and that money and data “remained safe throughout.” Lloyds and HSBC also said their services had returned to normal.
Your money also keeps its usual legal protections during an outage. At UK banks, eligible deposits are covered by the Financial Services Compensation Scheme (FSCS) up to £120,000 per person, per bank. E-money accounts work differently: instead of FSCS cover, providers must keep customers’ funds safeguarded in separate accounts. If you’re not sure which applies to you, your account details or your provider’s terms will say.
Can I get compensation for the outage?
Don’t expect a payout just for the inconvenience. But if the outage cost you actual money, you can ask your bank to put it right. The Financial Conduct Authority (FCA) said in a statement: “People need to be able to access their money and make payments, so we expect firms to fix issues quickly, keep their customers informed and ensure no one is left out of pocket.”
Examples of losses worth raising include:
- A late-payment fee because a bill or rent payment couldn’t go through
- A failed Direct Debit that triggered a charge
- Extra fees for using a different card or withdrawing cash abroad
- Costs from a missed booking or deadline you can link directly to the outage
How to make a claim
- Collect evidence: screenshots of error messages, receipts, fee notices and the times things failed.
- Raise a formal complaint through your bank’s app, website or phone line, and say clearly what it cost you.
- Escalate if needed. If you’re unhappy with the response, or haven’t had a final answer within eight weeks, you can take the complaint to the free Financial Ombudsman Service.
Why one data centre took down so much
Most of the apps you use every day don’t run on their own computers. They rent capacity from a handful of giant cloud companies, mainly Amazon Web Services, Microsoft and Google. That’s efficient, but it means one fault can hit many brands at once. If you want the business case for why companies do this, our explainer on cloud-managed services in modern business operations covers the basics.
Regulators already saw this risk coming. In July, the UK brought Google Cloud, Microsoft, Amazon Web Services and Oracle under direct oversight as “critical third parties” to the financial sector, Reuters reported, specifically because one outage could disrupt many firms together. Tuesday’s incident is the first major test of that regime. The FCA and the Bank of England’s Prudential Regulation Authority are talking to Google, and Meg Hillier, chair of the Treasury Committee, has written to the regulators asking how they responded and what the total impact was, with an initial reply requested by November 4.
It isn’t the first cascade, either. Almost exactly a year ago, an Amazon Web Services failure in its us-east-1 region lasted about 15 hours and disrupted services worldwide, The Guardian noted. Internet infrastructure expert Michał Woźniak told the paper: “Hyperscalers have become too big to not fail.”
How to protect yourself the next time your bank app goes down
You can’t stop a data centre losing power, but a few low-effort habits mean an outage becomes an annoyance rather than a crisis:
- Carry a backup card from a different provider. Two cards from banks that may share the same cloud supplier aren’t much of a backup, so spread them out if you can.
- Keep a little cash. Enough for fuel, parking, a taxi or a meal can get you through a few bad hours, especially when travelling.
- Don’t leave big payments to the last minute. Send rent, bills and deposits a day or two before they’re due so a short outage doesn’t make you late.
- Keep your emergency savings reachable. Having an emergency fund somewhere other than your everyday spending account means one app going dark doesn’t freeze everything. Our guide to balancing immediate needs and future financial goals has more on building that cushion.
- Check official status pages first. Bank status pages and their official social accounts are the fastest way to confirm an outage. Be wary of anyone who contacts you during an outage offering to “fix” your account.
- Write down important numbers. Keep your bank’s phone number and card-blocking line saved somewhere that isn’t the app itself.
Small steps like these are part of the wider sense of financial confidence that makes surprises easier to handle.
Google Cloud and Revolut outage FAQ
Is Revolut down right now?
No. Revolut told the BBC that services were fully restored after Tuesday’s disruption, and its system status page is the best place to check live status.
What caused the Google Cloud outage?
Google blamed a “power event” at a third-party facility in its europe-west2 (London) cloud region, affecting the europe-west2-b zone. A full analysis is expected on Google’s status dashboard.
How long did the outage last?
Google’s status dashboard lists the incident at 7 hours and 52 minutes. It started just after 6 a.m. London time, and most services were back by mid-afternoon, though some apps took longer to fully recover.
Will I get compensation for the outage?
Not for inconvenience alone, but you can claim back direct costs such as late fees or failed-payment charges. Complain to your bank first, then go to the Financial Ombudsman Service if you’re not satisfied after eight weeks.
Featured photo: Aerial view of a Google data center in Council Bluffs, Iowa (illustrative; not the London facility involved), by Chad Davis, via Wikimedia Commons, licensed CC BY 2.0.
