Google Cloud outage disrupts HSBC, Revolut, Lloyds, and more

What happened

A Google Cloud outage centred on the London region, known as europe-west2, caused a wave of disruption across banking, payments, delivery and web services on Tuesday, 20 October 2026. Google’s own service health dashboard listed the incident as active, with a start time of 19 October at 23:08 Pacific time, equivalent to the early morning of 20 October in the UK and Europe [1]. The affected location was London, and Google described the symptoms as elevated errors and intermittent network failures across multiple Google Cloud services in europe-west2 [1].

The timing quickly matched a visible pattern of customer complaints at several banks and consumer platforms. Reuters reported that multiple Google Cloud services were disrupted in the London region while Revolut was also experiencing a service outage, and a person familiar with the matter told Reuters that Revolut’s disruption was related to the Google Cloud incident [2]. Revolut’s own messaging to customers stressed that money and data were safe, even as services such as card payments and ATM withdrawals were unavailable or partially unavailable [2].

The disruption was not limited to one app. Sky News reported spikes or user problems involving Revolut, Lloyds, HSBC, Rightmove, Royal Mail, Bank of Scotland, SiteGround, DPD, Halifax and others during the same incident window [4]. TechRadar separately reported that Revolut and Lloyds Bank issues began at about 6:46am BST, with Downdetector peaks of nearly 1,500 reports for Revolut and around 500 for Lloyds Bank [3]. Those numbers are not a definitive count of affected customers, but they are a useful indicator of how quickly the outage became visible to consumers.

Google’s status: a regional incident with many products involved

Google’s service health page listed a broad set of affected products, including Compute Engine, Google Kubernetes Engine, Cloud Storage, Cloud SQL, BigQuery, Cloud Run, Pub/Sub, Cloud Load Balancing, Virtual Private Cloud and several database, analytics and networking products [1]. That matters because banks and fintechs rarely depend on just one cloud component. A payment app may rely simultaneously on compute capacity, databases, network routing, identity systems, logging, storage and customer support workflows. When multiple layers degrade together, the symptoms can appear to users as failed sign-ins, declined card payments, slow account screens or delayed transfers.

By the latest Google update visible before publication, the company said its engineering team was still investigating and apologised to those affected [1]. Google also changed the practical guidance from “no workaround” to a conditional workaround: affected customers could try, if feasible, to migrate impacted workloads to another available zone or region [1]. That advice is technically sensible but operationally difficult. Moving live financial systems under outage pressure is not like moving a static website. Regulated firms need to protect transaction integrity, customer balances, audit trails and fraud controls while restoring availability.

Google’s wording points to a regional infrastructure problem rather than a named cyber incident. Sky News also reported a separate Google Security Operations incident under investigation, but the core banking and consumer disruption described here was linked to Google Cloud’s europe-west2 service problems [4]. At the time covered by the latest fresh sources, Google had not publicly given a root cause for the London-region failure.

Revolut felt the sharpest consumer impact

Revolut appeared to be among the hardest hit consumer-facing services. Reuters reported that most Revolut services were unavailable or partially unavailable, including card payments and ATM withdrawals [2]. The Guardian reported that customers were unable to access the banking app and that affected services included sign-in, card payments, transfers, ATM withdrawals and cryptocurrency services [5]. BleepingComputer reported that Revolut’s status page showed 28 affected services, including sign-ins, card payments, transfers, currency exchange, stock trading and live support chat [6].

For a digital-first bank, that combination is especially damaging. If a customer cannot sign in, cannot move money, cannot use a card and cannot withdraw cash, the outage becomes more than a temporary inconvenience. It can affect commuting, grocery shopping, travel, small-business cash flow and emergency payments. Revolut’s public statement tried to separate availability from safety: the company said customers’ money and data were safe and that it had been working to fix the issue since it was identified in the morning [5].

The outage also showed the difference between a bank’s balance sheet and a customer’s access to it. A customer’s funds can be safe in the legal and accounting sense while the digital rails needed to use those funds are unavailable. In modern retail banking, availability is not just a technical target; it is part of the customer promise.

Lloyds, HSBC and other UK services also saw disruption

Lloyds and HSBC were repeatedly named in outage reporting and user-tracking data. The Independent reported that the broader internet outage had affected Lloyds Bank, HSBC, Screwfix, DPD and Revolut, while noting that it was not yet clear whether every reported issue was directly caused by Google Cloud [7]. Sky News listed Lloyds, HSBC, Bank of Scotland, Halifax and other non-bank services among those seeing user reports during the Google Cloud disruption [4]. Clubic, covering the story for a French audience, also reported rising reports for Lloyds, HSBC, NatWest, Santander UK, Bank of Scotland, Halifax, Scottish Widows and MBNA, while pointing out that several of those brands sit within the Lloyds Banking Group family [8].

Lloyds took a more measured public position. TechRadar reported a statement from a Lloyds Bank spokesperson saying the app was online and customers could log in normally, although some people were having issues with certain online services; the bank also said it was aware of similar issues affecting other organisations and was monitoring the situation [3]. That distinction is important. Not every bank named in a user-reporting spike was necessarily fully down. Some customers may have been able to log in while others experienced slow performance, failed payments or partial service errors.

HSBC appeared in the same cluster of reported disruptions, but the available fresh reporting was more cautious about directly attributing each HSBC problem to Google Cloud. The safest reading is that HSBC was among the major banks with user-reported issues during the incident, while Google Cloud’s europe-west2 outage was the central infrastructure event occurring at the same time [4][7].

Why one cloud region can affect so many brands

The incident is a case study in cloud concentration. Google Cloud, Amazon Web Services and Microsoft Azure provide the infrastructure behind thousands of consumer-facing services. Companies use cloud providers because the platforms offer scale, resilience tools, data services and global reach that would be expensive and slow to build alone. But the same concentration can make failures look surprisingly broad: unrelated banks, delivery firms and property websites can all falter because they share a supplier, a region or a dependency chain.

The geography also matters. Google’s affected region was europe-west2, the London region [1]. For UK financial services, a London cloud region is attractive because it keeps workloads close to customers, payment systems, regulators and internal teams. Low latency and data residency can be advantages. But if too many critical workloads rely on the same region, and if failover has not been fully automated and tested, the benefit of proximity can turn into a single point of operational stress.

Google’s own workaround language implicitly underlines the resilience challenge. Customers may migrate workloads to another zone or region “if feasible” [1]. The phrase is doing a lot of work. Feasibility depends on prior architecture: replicated databases, tested failover runbooks, traffic management, security policies, data consistency models and staff readiness. A company cannot improvise multi-region resilience in the middle of a live banking outage.

The current state and the lesson

By the latest updates available in the 72-hour window, the Google Cloud incident remained active, though some user-report spikes appeared to be easing. TechRadar reported at 10:19 UTC that some initial surges for Revolut, Lloyds, Rightmove and DPD appeared to be recovering on Downdetector [9]. That does not mean every customer was back to normal, and it does not identify a root cause. It does suggest that the incident was moving from acute public failure toward partial recovery while Google and affected companies continued investigation and remediation.

The immediate lesson is not that cloud is inherently unsafe. Most modern banking would be slower, less scalable and less feature-rich without cloud infrastructure. The lesson is that cloud resilience is not automatic. Buying capacity from a hyperscale provider does not by itself guarantee that an app, a card payment path or a customer-support channel will survive a regional fault.

For banks and fintechs, the hard questions after 20 October will be architectural and operational. Which services truly failed over? Which only looked redundant on paper? Which customer journeys still depended on a single region, a single queue, a single identity path or a single database replica? And how quickly could firms communicate clearly when the customer-facing symptom was inside their app but the root problem sat in someone else’s data centre?

For customers, the outage was simpler: cards failed, apps slowed, logins broke and payments were uncertain. That is why the incident matters. A cloud problem in London did not stay inside the cloud. It arrived at checkouts, cash machines and banking apps across Europe.

Developments

1. Google Cloud Outage Disrupts Revolut and Banks Across EuropeMashable · Oct 20, 2026, 12:40 PM · 8/10
2. Google cloud outage disrupts HSBC, Revolut, Lloyds and moreThe Times · Oct 20, 2026, 12:07 PM · 9/10
3. Google Cloud outage disrupts Revolut and other servicesInvesting.com · Oct 20, 2026, 12:06 PM · 7/10
4. Google Cloud outage disrupts HSBC, Revolut, and othersNeowin · Oct 20, 2026, 12:04 PM · 8/10
5. Google Cloud outage impacts HSBC, Revolut, Lloyds, and more on October 20, 2026The Independent · Oct 20, 2026, 11:37 AM · 8/10
6. Google Cloud London zones experience outage on October 20, 2026The Register · Oct 20, 2026, 11:34 AM · 7/10

Sources from the last 72 hours

1. [1]Google Cloud Service HealthOct 20, 2026, 12:01 PM
2. [2]Google Cloud services face outage in London, Revolut services down tooOct 20, 2026, 11:30 AM
3. [3]Revolut and Lloyds Bank are down for thousands — here's all the latest on the outagesOct 20, 2026, 12:20 PM
4. [4]Google outage latest: Banking, NHS England and bike rentals among dozens of apps hit by Google Cloud issuesservice issuesOct 20, 2026, 12:08 PM
5. [5]Millions unable to use Revolut app or cards as company suffers ‘service disruption’Oct 20, 2026, 11:45 AM
6. [6]Revolut outage disrupts online banking operations worldwideOct 20, 2026, 11:46 AM
7. [7]Why did the internet just break? Google Cloud outage takes down Revolut and othersOct 20, 2026, 11:37 AM
8. [8]Revolut, Lloyds, HSBC… les banques britanniques dans la tourmente, un incident Google Cloud ?Oct 20, 2026, 11:54 AM
9. [9]Google Cloud down - major outage across Europe hits big brands, banking apps and moreOct 20, 2026, 12:19 PM

AI-generated article based on recent web research, then preserved as a dated editorial snapshot.