The Grey Terminal
WHERE CODE MEETS CAPITAL
Loading prices…
Powered by CoinGecko
Business & Venture

Google Cloud Power Fail Knocks Out Revolut, Lloyds and HSBC, Thousands of UK Customers Locked Out of Payments

Thousands of UK customers experienced disruption to banking services on Oct. 20 after a power-related failure at Google Cloud affected Revolut, Lloyds Banking Group and HSBC.

Google Cloud Power Fail Knocks Out Revolut, Lloyds and HSBC, Thousands of UK Customers Locked Out of Payments

The Oct. 20 outage disrupted banking and public services, prompting UK and European authorities to examine the resilience of critical technology providers.

Key Takeaways
  • A Google Cloud London data center power failure knocks out digital payment services for Revolut, Lloyds, and HSBC customers.
  • The outage strikes zone europe-west2-b, disrupting thirteen million UK Revolut accounts alongside Royal Mail and the HM Courts Video Platform.
  • Financial Conduct Authority regulators investigate Google Cloud under critical third-party rules to assess systemic concentration risks across British retail banking.
Listen to this article
READY

Thousands of UK customers experienced disruption to banking services on Oct. 20 after a power-related failure at Google Cloud affected Revolut, Lloyds Banking Group and HSBC. Customers reported problems with card payments, cash withdrawals and account access, while Revolut listed interruptions across several of its services.

The outage began in Google Cloud’s London region and affected multiple cloud products. It also prompted regulatory scrutiny of a provider designated as critical to the UK financial system just three months earlier, bringing questions about cloud resilience into focus through a specific, documented incident.

What Failed and How the Disruption Spread

Google Cloud’s service status dashboard reported elevated errors and intermittent network failures in its europe-west2 region at approximately 7:08 a.m. British Summer Time on Oct. 20. The company attributed the incident to a “power event” at a third-party facility that took the europe-west2-b zone offline.

The disruption affected several products, including Compute Engine, Google Kubernetes Engine, Cloud SQL, Cloud Storage and Cloud Run. Google divides its infrastructure into regions and zones to help isolate failures, but the incident disrupted services beyond the affected zone. The company advised customers to move workloads to another zone or region where feasible. As of Oct. 22, Google had not published its promised detailed analysis of the incident.

Advertisement · Press Release

Have a development worth tracking?

Share product launches, funding announcements, partnerships, research findings and market developments with The Grey Terminal's readership.

→ Submit a Press Release

How the Banks Were Affected and What Customers Experienced

Revolut, which has approximately 13 million UK customers, reported problems with card payments, ATM withdrawals, account logins, transfers, currency exchange and stock trading. Its status page listed several services as partially unavailable. Downdetector, a platform that collects user-submitted outage reports, recorded more than 1,500 reports relating to Revolut early that morning. The figure represents reports, not verified individual customers.

Lloyds Banking Group, which includes Lloyds Bank, Halifax and Bank of Scotland, acknowledged problems with some online services. HSBC also confirmed that some customers had difficulty accessing its services. Neither bank published a consolidated count of affected customers or quantified the financial impact of the disruption.

The effects extended beyond banking. HM Courts & Tribunals Service reported disruption to its Cloud Video Platform, which supports remote court hearings. Royal Mail, DPD and Rightmove also reported problems. The precise technical dependencies linking these organizations to the Google Cloud incident had not been publicly detailed, leaving the extent of the disruption across individual services unclear.

The Regulatory and Concentration-Risk Angle

On July 13, 2026, HM Treasury designated Google Cloud EMEA Limited, Microsoft Ireland Operations Limited, Amazon Web Services EMEA SARL and Oracle Corporation UK Limited as critical third parties under the UK’s financial services oversight regime. The designation gives financial regulators powers to oversee technology providers whose services are important to the financial system. Banks remain responsible for maintaining their own operational resilience.

On Oct. 20, Treasury Committee Chair Dame Meg Hillier wrote to the Bank of England governor and the Financial Conduct Authority’s chief executive seeking details of the outage, its effects on customers and any financial harm. The FCA said it was engaging with Google. The European Banking Authority also contacted Google Cloud to assess the potential impact on financial institutions in the European Union.

The inquiries have not established the total customer impact or financial losses. Nor have regulators published findings on whether the existing safeguards were sufficient to contain the disruption. Those assessments will depend on further evidence from the companies and the authorities’ examination of the incident.

Google Reports Restoration, Full Impact Remains Unclear

Google reported that the disruption had been resolved and services restored. Its updates on Oct. 20 said most affected workloads had recovered by the afternoon, although a very small number of customers remained affected in at least one update. The company said it would publish a detailed analysis of what happened.

Revolut said customer money and data remained safe throughout the outage. Lloyds Banking Group and HSBC acknowledged service problems, but public statements did not establish how many customers were affected at either institution. As of Oct. 22, the banks had not published consolidated figures for customer losses or compensation, and Google’s detailed incident analysis remained outstanding.

TERMINAL LAYER

Activate Terminal Layer

Structural analysis of the systems, pressures, and stakeholders behind this story.

FAQ

Frequently Asked Questions

01

What caused the October 2026 UK banking cloud outage?

The outage stemmed from an electrical failure at a third-party facility hosting Google Cloud infrastructure in London. Technical teams identified an unexpected power incident in zone europe-west2-b that disabled core database and compute clusters. The disruption interrupted downstream services across major financial applications and government platforms.
02

Why does the Google Cloud failure matter for UK banking resilience?

The incident highlights systemic concentration risk across major financial institutions that rely on shared cloud infrastructure providers. Revolut reported severe payment and withdrawal interruptions across its 13 million British account holders. Regulators fear that localized server downtime at single cloud vendors can trigger synchronized failures across retail payment rails.
03

How did the service interruption spread across Google Cloud products?

Errors emerged at 7:08 a.m. British Summer Time on October 20 across Google Kubernetes Engine and Cloud SQL databases. The failure quickly spread beyond the primary facility to affect compute nodes operating across the europe-west2 region. Engineers stabilized the platform by afternoon, but third-party recovery teams required additional hours to restore full banking features.
04

What public services suffered outages alongside Lloyds and HSBC?

The technical failure disabled the Cloud Video Platform used by HM Courts & Tribunals Service to run remote hearings. Logistics networks including Royal Mail and DPD experienced tracking and service portal disruptions throughout the morning. Lloyds Banking Group and HSBC reported that customer records remained protected despite widespread web portal login blackouts.
05

How are British and European regulators supervising critical cloud vendors?

HM Treasury formally designated Google Cloud, Microsoft, Amazon Web Services, and Oracle as critical third parties in July 2026. Treasury Committee Chair Dame Meg Hillier requested formal impact assessments from the Financial Conduct Authority and the Bank of England. The European Banking Authority initiated direct technical inquiries with Google to enforce cross-border operational resilience standards.

You Might Also Like

THE GREY TERMINAL
🛡
Alex Reeve

Alex Reeve is a contributing writer for The Grey Terminal Her articles provide timely insights and analysis across these interconnected industries, including regulatory updates, market trends, token economics, institutional developments, platform innovations, stablecoins, meme coins, policy shifts, and the latest advancements in AI, applications, tools, models, and their broader implications for technology and markets.

○ The views and opinions expressed by the author in this article are her own and do not necessarily reflect the official position of The Grey Terminal, its management, editors, or affiliates. This content is provided for informational and educational purposes only and does not constitute financial, investment, legal, or tax advice. Readers should conduct their own research and consult qualified professionals before making any decisions related to digital assets, cryptocurrencies, or financial matters. The Grey Terminal and its contributors are not responsible for any losses incurred from reliance on this information.