A single regional failure inside one Google Cloud data centre in London was enough to knock out card payments, ATM withdrawals and app sign-ins for customers of one of the UK’s largest digital banks on the morning of 20 October 2026. At peak disruption, nearly 1,500 Revolut customers and around 500 Lloyds Bank customers filed reports on Downdetector, with HSBC and Barclays also flagged by users. Understanding the Revolut Google Cloud outage in full requires looking at these details closely.
This article summarises what happened in the Revolut Google Cloud outage, draws on gf6.com’s four-year curated directory of banks and ATMs for context on UK banking infrastructure, and looks at what the incident suggests about concentration risk in the cloud services that increasingly sit behind everyday retail banking.
The finding — what happened on 20 October 2026 — Revolut Google Cloud outage
On the morning of 20 October 2026, Google Cloud suffered a regional failure in its London (europe-west2) data centre beginning at approximately 06:08 GMT, knocking out multiple infrastructure services. UK digital bank Revolut confirmed the outage affected card payments, ATM withdrawals, money transfers, currency exchange, share trading and app sign-in. A source familiar with the matter told Reuters that Revolut’s disruption was directly tied to the Google Cloud incident. These figures put the Revolut Google Cloud outage into clearer perspective.
At peak disruption, nearly 1,500 Revolut customers and around 500 Lloyds Bank customers filed reports on Downdetector, with HSBC and Barclays also flagged by users. Revolut’s status page showed the majority of its services as either fully down or only partly operational. Google’s engineering team investigated the incident and suggested customers shift operations to alternative cloud regions where feasible. This context matters for anyone following the Revolut Google Cloud outage.
A Revolut Bank spokesperson said: “We are currently experiencing a service disruption affecting multiple services. We can confirm that all our customers’ money and data are safe.” It is a central thread in the wider Revolut Google Cloud outage.
The incident was reported by multiple outlets, including CNN, Quartz and TechRadar.
What it means for UK banking resilience
The data point that stands out is not the number of complaints — Downdetector counts in the hundreds and low thousands are not unusual for large outages — but the fact that a single regional cloud failure visibly reached several unrelated UK financial brands at the same time. Revolut was the most severely affected, but reports from Lloyds, HSBC and Barclays users on the same morning point to how widely London-region cloud infrastructure is used across the sector. Such details shaped how the Revolut Google Cloud outage unfolded.
The direct link reported between the Google Cloud europe-west2 failure and Revolut’s disruption is the clearest part of the story. For the other banks named, user reports show that customers experienced problems, but the public record so far does not establish the same direct technical cause — which is an important distinction when interpreting Downdetector spikes. This is one of the defining aspects of the Revolut Google Cloud outage.
This is widely seen as the kind of event regulators have been warning about: when many financial institutions depend on a small number of hyperscale cloud providers, a localised technical fault can cascade into a cross-brand consumer experience of “the banks are down”. The practical impact on 20 October — people unable to tap a card, withdraw cash from an ATM, or sign in to check a balance — is exactly the scenario that cyber-resilience frameworks are designed to limit.
Google’s advice to shift workloads to alternative regions is standard incident guidance, but it also underlines the point: resilience in modern retail banking increasingly depends on how banks architect across cloud regions, not just on their own data centres.
How this fits the UK banking map
The UK has one of the densest retail banking footprints in Europe, combining long-established high-street names such as Lloyds, HSBC and Barclays with app-first challengers like Revolut. You can browse the physical side of that network — branches and ATMs across the country — in gf6.com’s directory of banks in United Kingdom.
What the 20 October incident highlights is the gap between that physical map and the invisible one. A branch or ATM might be open and powered, but if the authorisation and app-login services behind it depend on a cloud region that has failed, the customer experience is the same as if the location were shut. For travellers and residents alike, that makes it worth knowing more than one way to access cash and make payments.
Explore the full data behind this article: bank branches worldwide and ATMs worldwide in the gf6.com directory.
Methodology
gf6.com maintains a worldwide directory of roughly 445,000 bank branches and ATM locations — about 346,000 branches and 99,000 ATMs — built up manually since 2020 and expanded over four years from public sources and ongoing research. The directory is a large but incomplete sample of global financial infrastructure, and coverage varies by country.
For this article, the event facts (timing, affected services, Downdetector report counts, the quoted statement and the attribution of Revolut’s disruption to the Google Cloud europe-west2 failure) come from the cited reporting by CNN, Quartz and TechRadar on 20 October 2026. No figures beyond those explicitly reported have been added. gf6.com’s directory is referenced only for context on the UK banking footprint and is not the source of the outage data.
Frequently asked questions
What caused the Revolut outage on 20 October 2026?
According to reporting, a regional failure in Google Cloud’s London (europe-west2) data centre beginning at approximately 06:08 GMT knocked out multiple infrastructure services. A source familiar with the matter told Reuters that Revolut’s disruption was directly tied to that Google Cloud incident.
Which Revolut services were affected?
Revolut confirmed the outage affected card payments, ATM withdrawals, money transfers, currency exchange, share trading and app sign-in. The company’s status page showed the majority of its services as either fully down or only partly operational.
Were other UK banks hit as well?
At peak disruption, around 500 Lloyds Bank customers filed reports on Downdetector, and HSBC and Barclays were also flagged by users. The public reporting establishes the direct Google Cloud link for Revolut; for the other banks, user reports show problems but do not confirm the same technical cause.
Was customer money or data at risk?
A Revolut Bank spokesperson said: “We are currently experiencing a service disruption affecting multiple services. We can confirm that all our customers’ money and data are safe.”
Why does one cloud outage affect several banks at once?
Many banks and fintechs run critical services on a small number of hyperscale cloud providers and regions. When a single region fails, institutions that depend on it can experience simultaneous disruption — a concentration risk that regulators have been examining for several years.
What should you do during a banking app outage?
Keep a backup payment method such as a card from a different bank or some cash, and avoid repeatedly retrying failed transactions, which can create duplicate pending charges. Check the bank’s official status page or verified social channels for updates rather than relying on rumour.
This article was produced with AI assistance from publicly available sources and is handled under our editorial standards and AI policy.
I have been online since 1995. For many years, I worked in the e-commerce sector, setting up several online shops, and have always been interested in data analysis. In 2007, I moved to the Seychelles to work from there or as a digital nomad. In recent years, I have increasingly specialised in the financial sector. I manage the Seychelles’ Commercial Register and am also very familiar with the offshore world. GF6.com is a project I have been working on for many years. I built and curated the 445,000-entry bank database myself over a period of six years, and for the past two years or so I have also been using AI to achieve better structures.
More from this author →
