A power failure inside a single Google Cloud data center in London reached across seven European countries on Tuesday, October 20, 2026, freezing card payments, ATM withdrawals, transfers and app sign-in for customers of digital bank Revolut. The incident, which Google Cloud attributed to a “power event” inside its europe-west2 region, became one of the clearest public demonstrations yet of how a single cloud provider’s regional outage can cascade directly into consumers’ ability to pay for groceries, pull cash from a machine, or even open their banking app.
Revolut, which serves millions of customers across Europe, confirmed that card payments, ATM withdrawals, transfers, and app sign-in were among the services hit. A person familiar with the matter told Reuters that the Revolut disruption was tied to the Google Cloud incident, according to reporting cited by The Register. Revolut said customers’ money and data remained safe throughout the disruption, even as the outage rippled through its payment rails for hours.
Don't miss new tech stories on Google
Add Tech Insider once in the Google app and our stories appear in your news suggestions.
What Happened: The Google Cloud Power Event Behind the Revolut Blackout
Google Cloud’s own status messaging pinned the root cause on infrastructure, not software. The company told customers that “Google Cloud services are unavailable in europe-west2-b zone,” identifying the europe-west2-b availability zone, one of several zones that make up the London region, as the point of failure. Google Cloud attributed the incident to a power event, the kind of physical infrastructure failure that, unlike a software bug, can’t be patched remotely in minutes. It has to be fixed at the facility level, which tends to stretch outages from minutes into hours.
Google Cloud later said service availability had been restored or was in the process of recovering, a sequence of events described by The Irish Times. For a company the size of Google, a single-zone power event sounds like it should be a contained, almost routine failure. For Revolut, whose banking infrastructure apparently leaned on that specific zone, it meant hours of customers unable to tap a card at checkout or sign into the app to check their balance. It’s a distinct, bank-specific sequel to the broader Google Cloud UK outage that disrupted nine services in the same region earlier the same day.
This is the core tension at the heart of the story. Cloud providers build redundancy into their own infrastructure, spreading workloads across zones and regions specifically so that one physical failure doesn’t take down an entire service. But that redundancy only works if the customer running on top of the cloud, in this case a regulated bank serving millions of people, has also architected its own systems to fail over cleanly when one zone goes dark. When it doesn’t, a localized power problem in one London data hall turns into a continent-wide banking disruption.
Revolut’s Outage, Country by Country
Reports identified affected Revolut customers in the United Kingdom, Ireland, France, Spain, Romania, Germany, and Luxembourg, a span of markets that reflects just how deeply Revolut’s digital-first banking model has penetrated the continent. In Ireland alone, Revolut’s 3.4 million customers were affected, according to reporting cited by The Irish Times. That figure alone is a useful proxy for scale: Ireland has a population of roughly 5.3 million, meaning a sizable share of the country’s adult population holds a Revolut account and was, for some stretch of Tuesday, unable to reliably use it.
Luxembourg’s exposure was flagged separately by the Luxembourg Times, underscoring that this wasn’t confined to Revolut’s largest markets. Smaller banking populations in Luxembourg felt the same card-payment and app-access problems as customers in London or Paris. The exact number of countries affected worldwide, and the exact number of Revolut customers affected globally, have not been independently confirmed, and this article does not treat either figure as established. What is confirmed is the list of seven countries named above, along with the Irish customer count.
It’s worth noting that Revolut operates well beyond those seven markets, with a footprint that extends into the Americas, Asia-Pacific, and other European countries not named in current reporting. Whether those additional markets experienced any disruption is simply not something that’s been verified yet, and readers should treat any claim of a fully global Revolut outage with caution until official confirmation arrives.
Which Revolut Services Went Down
The disruption wasn’t limited to one corner of Revolut’s app. Reports from Silicon Republic and other outlets described partial unavailability spanning several distinct functions that customers rely on daily.
- Card payments at point of sale
- ATM cash withdrawals
- Money transfers between accounts and to other banks
- App sign-in and authentication
- Other in-app services tied to the affected backend
That combination is particularly painful for a digital-only bank. A traditional high-street bank that suffers an app outage still has physical branches and, in many cases, card networks that keep functioning independently of the bank’s own servers for some transaction types. Revolut, built as a mobile-first neobank, doesn’t have that fallback layer in the same way. When the backend that authenticates a card swipe or validates a transfer sits behind a cloud region that just lost power, there’s no branch teller to paper over the gap.
Revolut was explicit that the outage did not put customer money or data at risk. The company said customers’ money and data remained safe, a distinction that matters: an availability failure, where systems simply can’t be reached, is a very different (and generally less severe) problem than a breach or data-integrity failure. Still, for someone standing at a supermarket checkout with a declined card, the distinction between “your money is safe but inaccessible” and “your money is at risk” is cold comfort in the moment.
Why a Single Cloud Zone Can Take Down a Bank
The structural reason this keeps happening comes down to how modern neobanks are built. Unlike legacy banks running decades-old mainframe cores, Revolut and its peers were built cloud-native from day one, leaning on providers like Google Cloud, AWS, or Microsoft Azure for compute, storage, and increasingly for core banking logic itself. That architecture is faster to build, cheaper to scale, and easier to update than legacy infrastructure. It also means the bank inherits every outage its cloud provider has, unless it has specifically engineered multi-zone or multi-region failover for every critical payment path. The gap between providers on this front isn’t trivial either, as a recent AWS vs Azure vs GCP pricing and infrastructure comparison illustrates for teams weighing where to put critical workloads.
Multi-region failover sounds simple in a slide deck. In practice, it requires replicating databases in real time across geographically separate zones, routing traffic intelligently when one region degrades, and testing that failover regularly enough to trust it during a real incident. Many companies, including sophisticated ones, treat multi-region resilience as a lower priority than it deserves, in part because testing it is disruptive and expensive, and in part because major cloud regions genuinely do fail only rarely. Tuesday’s event is a reminder that “rarely” is not “never,” and when a payments company is the one caught out, the blast radius lands directly on ordinary people trying to buy things.
This is also where the “power event” framing matters. Software bugs can often be rolled back. A botched configuration push can be reverted in minutes. A physical power failure at a data center, by contrast, has to be fixed by people physically restoring electricity, bringing cooling and hardware back online in sequence, and then letting services warm back up, which is part of why this class of outage tends to run longer than a typical software incident.
Market Impact: What This Means for Fintech and Cloud Concentration Risk
The immediate market reaction to a single-day outage, even one affecting millions of customers across seven countries, is rarely visible in a neobank’s valuation the next morning. Revolut is privately held, so there’s no stock price to watch tick down. The more durable impact shows up in a different place: regulatory scrutiny and the conversations happening inside every other fintech’s risk and infrastructure teams this week.
European regulators have spent the past several years pushing financial institutions toward stronger operational resilience requirements, including rules that specifically address third-party technology concentration risk. An incident where a single cloud zone’s power failure knocks out card payments for a bank serving millions of customers across seven countries is exactly the kind of event those rules were written to prevent, or at least to force institutions to plan for. Expect this outage to become a reference case in regulatory conversations about how much of Europe’s retail banking infrastructure now sits on a small number of hyperscale cloud providers.
There’s a second-order effect worth watching too. Every fintech competing with Revolut, from Monzo to N26 to Wise, now has a concrete, dated, multi-country example to point to internally when arguing for budget to build out redundant infrastructure across more than one cloud provider or region. That kind of spending is historically hard to justify to a board when nothing has gone wrong yet. Tuesday’s outage removes that excuse, at least for a while. It’s the same budget argument that has pushed some IT buyers toward cloud repatriation onto dedicated servers to cut both cost and single-provider exposure.
Competitive Comparison: How Exposed Are Revolut’s Rivals?
Revolut isn’t unique in leaning on a single hyperscale cloud provider for critical infrastructure. Most of the current generation of digital-first banks made similar architectural choices for similar reasons: speed, cost, and the ability to scale a banking product globally without building physical data centers. The table below lays out what’s publicly known about each major neobank’s general cloud posture, based on company statements and industry reporting, rather than claiming precise, verified figures for each.
| Digital Bank | Primary Cloud Approach | Markets Served | October 20 Outage Impact |
|---|---|---|---|
| Revolut | Google Cloud-hosted infrastructure, including europe-west2 region | UK, Ireland, France, Spain, Romania, Germany, Luxembourg (confirmed affected) | Card payments, ATM withdrawals, transfers, sign-in disrupted |
| Monzo | Not implicated in this incident | UK-focused | No disruption reported in connection with this event |
| N26 | Not implicated in this incident | EU-wide | No disruption reported in connection with this event |
| Wise | Not implicated in this incident | Global | No disruption reported in connection with this event |
| Starling Bank | Not implicated in this incident | UK-focused | No disruption reported in connection with this event |
The table above should be read carefully: the absence of reported disruption at Monzo, N26, Wise, or Starling on October 20 does not mean those institutions are immune to a similar failure, nor does it mean they avoid Google Cloud’s europe-west2 region entirely. It simply reflects that, as of current reporting, no outage was attributed to those providers in connection with this specific power event. Cloud outages tend to expose whichever customers happen to have critical workloads concentrated in the exact zone that fails, which is partly a matter of architecture and partly a matter of which zone a company’s infrastructure team picked years ago. Choosing the right backing service for stateful workloads matters here too, a point underscored by a recent comparison of Durable Objects, DynamoDB and Firestore for resilient data storage.
Historical Context: Cloud Outages Keep Hitting Critical Services
Tuesday’s event fits a pattern that’s become familiar over the past several years: a single hyperscale cloud provider suffers a regional or zonal failure, and the damage shows up not at the cloud company itself but at the businesses and public services running on top of it. Major cloud outages at AWS, Microsoft Azure, and Google Cloud have, at various points over the past few years, disrupted everything from airline check-in systems to streaming services to government websites, because so much of the modern internet’s backend now runs on a small number of hyperscale providers. Public-sector cloud dependency has drawn similar scrutiny, including after Microsoft’s exit from a major UK data center deal raised questions about grid capacity and provider concentration in Britain.
What makes the Revolut case distinct within that pattern is the directness of the consumer impact. A streaming outage is an inconvenience. A banking outage that blocks card payments and ATM withdrawals touches people’s ability to buy food or access cash in the moment, which is why this incident drew coverage from financial outlets like Finance Magnates alongside general technology press. It’s a reminder that as banking has moved from branches to apps, the infrastructure dependencies sitting underneath those apps have become systemically important in a way they weren’t a decade ago.
Revolut itself has grown rapidly since its founding, expanding from a currency-exchange app into a full banking platform serving tens of millions of customers across dozens of countries. That growth has been part of the company’s pitch to customers and investors alike: fast, cheap, mobile-first banking that doesn’t carry the overhead of a traditional bank’s branch network. Tuesday’s outage is the flip side of that same pitch. The infrastructure that lets Revolut scale quickly and cheaply is the same infrastructure that, when a single zone loses power, leaves the company with fewer physical fallback options than a legacy bank would have.
Google Cloud’s europe-west2 Region: What We Know
Google Cloud’s europe-west2 region, based in London, is one of the company’s established European regions, split into multiple availability zones so that customers can design applications to survive the loss of any single zone. The zone implicated in Tuesday’s incident, europe-west2-b, is one of those zones. Google Cloud’s statement that “Google Cloud services are unavailable in europe-west2-b zone” was specific to that single zone rather than describing a region-wide failure across all of europe-west2’s infrastructure.
That distinction matters for understanding why this played out the way it did. If Revolut’s systems had been architected to automatically shift traffic away from europe-west2-b and onto a healthy zone the moment problems were detected, the outage customers experienced might have been measured in minutes rather than hours. The fact that customers across seven countries experienced sustained disruption to card payments, ATM withdrawals, transfers, and sign-in suggests that at least some critical path in Revolut’s infrastructure did not fail over cleanly, though the company has not published a detailed technical post-mortem as of this writing.
Google Cloud later said service availability had been restored or was recovering, language that’s consistent with how major cloud providers typically communicate the tail end of an infrastructure incident: first confirming the root cause, then confirming mitigation, then confirming recovery as monitoring data comes back to normal across affected customers.
What Revolut Customers Should Know
For Revolut customers directly affected by Tuesday’s disruption, the most important confirmed fact is that the company stated money and data remained safe throughout the incident. That’s a meaningfully different situation from a security breach, where customer funds or personal information could be directly at risk. An availability outage, however frustrating in the moment, is generally a question of access rather than loss. That’s a different threat model than the one facing banks when attackers, not power grids, are the problem, an area covered in a recent comparison of CrowdStrike, Microsoft Defender and SentinelOne endpoint protection.
That said, customers who attempted and failed to complete payments, withdrawals, or transfers during the window of disruption should check their transaction history once service is confirmed restored, since partial transaction failures during an infrastructure incident can sometimes require manual reconciliation. Customers in the seven confirmed affected countries, the UK, Ireland, France, Spain, Romania, Germany, and Luxembourg, are the ones most likely to have experienced direct disruption, based on current reporting.
The Regulatory Angle: Operational Resilience Rules in the Spotlight
European financial regulators have increasingly treated technology outages as a core prudential risk rather than a purely technical inconvenience. Rules already in force or being phased in across the EU and UK require banks and payment firms to map their dependencies on critical third-party technology providers, including cloud vendors, and to demonstrate they can maintain essential services even if one of those providers suffers a major failure.
An incident with the scale and visibility of Tuesday’s Revolut disruption, hitting card payments and ATM access for customers across seven countries including 3.4 million people in Ireland alone, is precisely the sort of event that regulators point to when justifying stricter resilience requirements. It would not be surprising to see this outage referenced directly in future regulatory guidance or in follow-up questions directed at Revolut and other neobanks about their cloud concentration risk and failover testing practices.
Cloud Dependency by the Numbers
The table below summarizes the confirmed facts of Tuesday’s incident in one place, distinguishing what has been verified from what remains unconfirmed as of this writing.
| Data Point | Status | Detail |
|---|---|---|
| Date of incident | Confirmed | Tuesday, October 20, 2026 |
| Root cause | Confirmed | Power event in Google Cloud’s europe-west2-b zone |
| Affected Revolut services | Confirmed | Card payments, ATM withdrawals, transfers, app sign-in, other services |
| Confirmed affected countries | Confirmed | UK, Ireland, France, Spain, Romania, Germany, Luxembourg |
| Irish customers affected | Confirmed | 3.4 million |
| Customer funds/data at risk | Confirmed | No, per Revolut statement |
| Global customer count affected | Unconfirmed | Not independently verified |
| Total countries affected worldwide | Unconfirmed | Not independently verified |
Predictions: Where This Story Goes Next
Several outcomes look likely in the coming weeks and months based on how similar cloud-outage stories have played out in the past.
- Revolut will likely publish a post-incident statement or technical summary addressing what failed in its failover architecture and what changes it plans to make, following the pattern set by other companies after high-visibility cloud outages.
- Expect renewed public debate over whether banks and payment firms should be required to run active multi-cloud or multi-region architectures for their most critical payment paths, rather than relying on a single provider’s internal redundancy.
- Rival neobanks, including Monzo, N26, Wise, and Starling, will likely face questions from customers and press about their own cloud dependencies and failover testing, even though none were implicated in Tuesday’s specific incident.
- Google Cloud will likely face continued scrutiny over the frequency and transparency of its incident reporting, particularly given that this is not the first europe-west2-related disruption to draw public attention this year.
- Expect this incident to surface in discussions among EU and UK financial regulators about operational resilience and third-party technology concentration risk, given the scale of the confirmed impact in Ireland and across six other countries.
The Bigger Picture: Banking’s Cloud Dependency Problem
Tuesday’s outage lands at a moment when the financial sector’s reliance on a handful of hyperscale cloud providers has never been higher, and when the services built on top of that infrastructure have never touched more people’s daily lives. Revolut’s growth into a mass-market bank serving millions of customers across Europe is itself a product of cloud infrastructure that made that scale achievable in the first place. The same infrastructure, when a single zone loses power, can take the whole experience down at once across every market that zone happens to serve.
That’s not an argument against cloud banking. It’s an argument for taking resilience as seriously as the growth that cloud infrastructure enables. The firms that treat multi-zone and multi-region failover as a genuine engineering priority, tested regularly rather than assumed to work, will be the ones that avoid becoming the next Tuesday-morning headline when a data center somewhere loses power.
Frequently Asked Questions
What caused the Revolut outage on October 20, 2026?
Revolut’s disruption was linked to a Google Cloud outage in the europe-west2 region, specifically the europe-west2-b zone, which Google Cloud attributed to a power event.
Which Revolut services were affected?
Reports confirmed disruption to card payments, ATM withdrawals, transfers, app sign-in, and other services within the Revolut app.
Which countries were affected by the Revolut outage?
Reports identified affected customers in the United Kingdom, Ireland, France, Spain, Romania, Germany, and Luxembourg. The exact number of countries affected worldwide has not been independently confirmed.
Was Revolut customer money or data at risk?
No. Revolut stated that customers’ money and data remained safe throughout the incident. This was an availability disruption, not a security breach.
How many Revolut customers were affected in Ireland?
Revolut’s 3.4 million customers in Ireland were affected, according to reporting from The Irish Times.
Is Google Cloud confirmed as the sole cause of the Revolut outage?
A person familiar with the matter told Reuters that the Revolut outage was related to the Google Cloud disruption. Reports have not established Google Cloud as the sole or definitive cause of every Revolut service failure during the incident.
Has Google Cloud’s europe-west2 region recovered?
Yes. Google Cloud said service availability had been restored or was recovering following the power event.
Could this kind of outage happen to other digital banks?
Any institution relying heavily on a single cloud provider’s region without robust multi-zone or multi-region failover is exposed to similar risk. No other major neobank was implicated in this specific incident as of current reporting.
