Revolut Down: 31 Services Affected, No ETA Yet [2026]

Revolut confirmed a service disruption on the morning of 20 October 2026, leaving some customers unable to make card payments, sign into the app or move money between accounts. The digital bank, which counts around 3.4 million customers in Ireland, said its engineering team was working to restore full service and stressed that no money or personal data had been put at risk. The Revolut outage struck during a Tuesday morning rush, and within hours it had become one of the most searched technology stories of the day across Ireland and the UK.

What makes this incident different from a routine banking-app glitch is where the trouble appears to have started. Irish broadcaster RTE reported that the disruption was tied to a Google Cloud outage, pointing to a wider infrastructure problem rather than a fault inside Revolut’s own code. That detail turns a single company’s bad morning into a case study on how much of modern banking now sits on top of a handful of hyperscale cloud platforms, which is why this story belongs as much in the cloud computing conversation as in the banking pages.

Google · Preferred Sources

Don't miss new tech stories on Google

Add TrendinTech Ireland once in the Google app and our stories appear in your news suggestions.

Add Now

Revolut outage: what happened this morning

Revolut’s first public acknowledgement came through its support account, which told customers the company was “currently experiencing a service disruption affecting multiple services” and added “we can confirm that all our customers’ money and data are safe.” The bank said it had been working to fix the problem since it was identified this morning and apologised to customers caught out by the interruption. A short time later, Revolut posted a follow-up update saying its engineering team was actively working to restore full service as quickly as possible.

According to the Irish Independent, the bank’s updated statement was specifically aimed at reassuring customers that their finances and financial information had not been compromised during the disruption, a distinction that matters a great deal in banking, where an outage and a breach trigger very different levels of regulatory and reputational damage.

The 31 services Revolut confirmed are down

Revolut operates a public system-status page that customers and journalists use to track live issues, and according to TheJournal.ie, that page listed 31 services as partially unavailable on Tuesday morning. The affected list spanned core everyday functions rather than a single obscure feature, which is why the complaints spread so quickly across social media.

Revolut function	Reported status	Source
Card payments	Partially unavailable	TheJournal.ie
Bank transfers	Partially unavailable	TheJournal.ie
ATM withdrawals	Partially unavailable	TheJournal.ie
Account sign-in	Partially unavailable	TheJournal.ie
Premium subscription services	Partially unavailable	TheJournal.ie
Mobile app access	Intermittent, inaccessible for some users	Irish Independent

Revolut has not said how many of its roughly 3.4 million Irish customers were directly affected, nor has it given a timeline for when every one of those 31 services would be fully restored. Both figures remain unconfirmed as of this morning, and readers should treat any specific restoration time circulating online as speculation until Revolut posts an official update.

Ireland’s exposure: 3.4 million customers on one app

Ireland has become one of Revolut’s largest European markets by customer count, and that scale is precisely why a morning outage here generates so much noise. Irish users reported problems both opening the app and tapping to pay at tills, according to reporting that tracked the disruption as it spread through the morning commute. For a country where contactless and app-based payments have become the default for daily spending, even a partial card-payment outage creates immediate friction at checkout counters, in cafes and on public transport.

Ireland’s wider relationship with cloud infrastructure has been a recurring theme this year, not just for fintech but for the national grid and planning system. Our coverage of how data centres now account for roughly a quarter of all electricity demand on the island has tracked growing public unease about how dependent Irish infrastructure, digital and physical, has become on a small number of large cloud operators. A banking outage tied to a cloud region hundreds of kilometres away is the kind of event that keeps that debate alive.

The Google Cloud connection: confirmed and unconfirmed

RTE’s headline on the story, “Revolut services affected due to Google Cloud outage,” put the cloud link front and centre, and other outlets reported similar detail during the morning. Reporting attributed to a person familiar with the matter, cited through Reuters wire coverage, linked Revolut’s disruption to an active incident in Google Cloud’s europe-west2 region, commonly associated with London. Google’s own status tooling reportedly showed elevated errors and intermittent network failures affecting multiple cloud services in that region.

It is important to be precise about what is confirmed here and what is not. Revolut’s own public statements on Tuesday morning confirmed only that a service disruption was underway and that customer money and data were safe. The bank did not, in its own words, name Google Cloud or any other specific supplier as the cause. The connection to a cloud-provider incident comes from third-party reporting and unnamed sourcing rather than a joint statement from Revolut and Google, so the underlying cause of the outage remains officially unconfirmed even as circumstantial evidence points toward a shared infrastructure problem.

That nuance matters for how seriously regulators and customers should weigh the incident. A software bug inside Revolut’s own stack is a company-specific failure. A regional cloud outage that happens to take down Revolut alongside unrelated businesses is a systemic one, and systemic cloud risk is exactly the subject our comparison of AWS, Azure and Google Cloud growth in the Irish market was built to track.

Not just Revolut: Lloyds, DPD and Rightmove also hit

TechRadar’s live blog tracked both Revolut and Lloyds Bank going down for thousands of customers on the same morning, which is the clearest sign yet that this was not an isolated Revolut problem. Separate reporting named parcel delivery firm DPD and property listings site Rightmove among other UK and Ireland-facing businesses that experienced access problems around the same window, consistent with a shared upstream cloud dependency rather than coincidence.

Organisation	Sector	Reported impact	Source
Revolut	Digital banking	31 services partially unavailable	TheJournal.ie
Lloyds Bank	Retail banking	App and online banking access issues	TechRadar
DPD	Parcel delivery	Reported service access issues	UK press reports
Rightmove	Property listings	Reported access issues	UK press reports
Google Cloud europe-west2	Cloud infrastructure	Elevated errors, intermittent network failures	RTE

Seeing a bank, a logistics firm and a property portal struggle at the same time is the clearest real-world argument for the “concentration risk” that cloud architects have been warning about for years: when enough of the economy runs on the same handful of regions, one bad morning for a single provider becomes a bad morning for dozens of unrelated companies and their customers.

Downdetector numbers: treat with caution

Outage-tracking site Downdetector, which aggregates self-reported user complaints rather than official telemetry, reportedly logged more than 1,500 reports tied to Revolut on Tuesday morning, according to The Next Web. That figure has not been confirmed by Revolut and should be read as a rough proxy for public frustration rather than a precise count of affected accounts. Downdetector numbers typically spike quickly once a story starts trending on social media, which can inflate totals well beyond the actual number of people experiencing a problem.

Historical context: fintech’s cloud dependency problem

Revolut is not a traditional bank with its own data centres bolted to a branch network. It is a cloud-native challenger that built its entire stack, from card authorisation to foreign exchange, on top of public cloud infrastructure. That architecture is exactly what let Revolut scale from a London startup to a business serving tens of millions of customers across Europe in roughly a decade, but it also means that when the underlying cloud region stumbles, the bank’s own resilience measures, however well designed, are only as good as the infrastructure sitting beneath them.

That trade-off is not unique to Revolut. Nearly every digital-first bank, neobroker and payments app built in the last ten years has made the same bet on hyperscale cloud economics over owning physical infrastructure. The approach cuts costs and speeds up feature delivery, but it also means a growing share of the banking system now shares a small number of underlying failure points. It is the same dynamic our cost comparison of managed Kubernetes across EKS, GKE and AKS in Ireland flagged when weighing lock-in against flexibility for enterprise workloads.

Market impact: what a morning of downtime actually costs

Precise financial figures for today’s incident have not been published, and any specific euro loss estimate circulating online should be treated as speculation rather than fact. What can be said with confidence is that outages of this kind carry costs on several fronts at once: lost transaction volume while card payments are degraded, customer support strain as complaints spike, and a reputational cost that is harder to measure but real, particularly for a challenger bank whose entire pitch to customers is a faster, more reliable digital experience than incumbent lenders.

There is also a slower-moving cost: every high-profile cloud-linked outage adds weight to the argument that financial regulators and corporate boards should be pricing in cloud concentration risk more explicitly. Insurance, contingency planning and even procurement decisions around which cloud regions and providers underpin critical payment rails are all likely to get a fresh look inside banks and fintechs that were watching today’s events unfold.

Competitive comparison: how resilience strategies differ

Not every financial institution has made the same cloud bet. Traditional banks such as AIB and Bank of Ireland still run significant workloads on their own legacy data centre infrastructure alongside newer cloud deployments, a hybrid approach that is slower to update but less exposed to a single provider’s regional incident. Challenger banks sit at the other end of the spectrum, running almost entirely on public cloud to move fast, and some are now experimenting with alternatives to the big three hyperscalers specifically to reduce that exposure.

UK digital bank Starling has been developing a transaction-focused AI model built and hosted on UK-owned cloud provider Civo rather than a hyperscale platform, a move explicitly framed as a response to concentration risk from depending on a small number of large cloud and AI providers. Whether that approach scales to a bank the size of Revolut is an open question, but it shows that at least some digital banks are treating today’s kind of incident as a design problem to be solved rather than an unavoidable cost of doing business in the cloud. For businesses weighing similar trade-offs between flexibility and lock-in, our look at serverless deployment options beyond the big three cloud providers covers the same tension from an infrastructure-cost angle.

Why resilience tooling matters beyond uptime

Resilience in modern banking is not just about keeping the lights on. It also covers how quickly a company can detect, contain and recover from an incident, which is why backup and disaster-recovery strategy sits so close to the cloud-outage conversation. Our look at how Veeam, Rubrik and Cohesity structure their recovery warranties is relevant background reading for any finance team asking what its own provider guarantees when, not if, a cloud region has a bad morning.

The security dimension of a banking outage

An outage is not the same thing as a breach, but the two get confused quickly in public conversation, which is exactly why Revolut moved so fast to separate the two in its messaging today. Endpoint and identity security tooling, the kind compared in our piece on CrowdStrike, SentinelOne and Microsoft Defender under NIS2 compliance rules, is part of why Revolut was able to state so quickly and so specifically that money and data remained safe even while availability suffered.

Regulatory angle: why “data is safe” is a legally loaded phrase

Revolut’s choice of words today was not accidental. Under European data protection law, a confirmed personal data breach triggers strict notification obligations to regulators and, in serious cases, to affected customers directly. By stating clearly and repeatedly that customer money and data were safe, Revolut was drawing a sharp line between an availability incident, which does not usually trigger those obligations, and a confidentiality or integrity incident, which would. Irish businesses handling a genuine data incident face a very different and far more demanding process, one we walked through in our guide to building a GDPR data breach response plan under the 72-hour notification deadline.

That distinction will matter if, as reporting suggests, the root cause does trace back to a cloud-provider incident rather than anything inside Revolut’s own systems. Liability, customer compensation and regulatory reporting obligations can all shift depending on where exactly in the chain, bank, cloud provider or network layer, a fault actually originated, which is one reason official confirmation of the cause is still pending.

What Revolut and Google Cloud have said about resilience before

The irony of today’s incident is that Revolut has previously held up its Google Cloud partnership as a selling point for reliability, not a risk. In a published Google Cloud customer case study, a Revolut representative identified only as Vlad said “with Google Cloud, we can scale our environment on demand in minutes with zero downtime,” adding that the setup “allows us to support our fast-paced growth and is key for innovation.” The same case study quoted Vlad describing how Revolut’s applications were built to avoid exactly the kind of disruption customers experienced this morning: “we can have each application running multiple instances, so everything is resilient and we don’t have any downtime when we deploy new instances.”

Today’s events do not necessarily contradict those statements, deployment-related redundancy and resilience to a regional infrastructure failure are different engineering problems, but they do illustrate the limits of application-level redundancy when the underlying cloud region itself is the thing misbehaving. Revolut’s own support account struck a far more cautious tone this morning, telling customers simply that “we are currently experiencing a service disruption affecting multiple services. We can confirm that all our customers’ money and data are safe,” before following up to say its “engineering team is actively working to restore full service as quickly as possible.”

Predictions: what happens next

Revolut is likely to publish a fuller post-incident explanation once services are restored, following the pattern most major banks and fintechs use after a public outage of this scale.
Expect renewed scrutiny from EU and Irish financial regulators of how digital banks document and manage cloud concentration risk, particularly where a single region underpins multiple customer-facing functions.
More challenger banks are likely to publicly test or adopt multi-cloud and sovereign-cloud alternatives, echoing the direction Starling has taken with UK provider Civo, as a hedge against exactly this kind of regional incident.
Short-term customer churn and complaint volume will likely rise in Ireland given the bank’s roughly 3.4 million-strong local user base, even if most customers regain full access within the day.
Expect comparison pieces and competitor marketing to seize on today’s outage, with rival banks and fintech apps highlighting their own uptime records in the coming weeks.

What Irish customers should do right now

Revolut has confirmed money and data remain safe, so the practical advice for affected customers is straightforward patience rather than panic. Anyone who cannot complete a card payment should have a backup payment method on hand for the next few hours, and anyone needing to move money urgently should check Revolut’s official status channels before assuming the problem is isolated to their own device. Those seeing delayed transactions should wait for the engineering team’s fix rather than repeatedly retrying, which can sometimes add to backlog during an active incident.

Frequently asked questions

Is Revolut down right now?
Revolut confirmed a service disruption on 20 October 2026 affecting multiple features, with its status page reportedly listing 31 services as partially unavailable. Check Revolut’s official app and support channels for the latest status, since outages of this kind are typically resolved in stages rather than all at once.

Is my money safe during the Revolut outage?
Yes. Revolut stated directly that all customers’ money and data are safe, and this is an availability incident rather than a confirmed security or data breach.

What caused the Revolut outage?
The exact cause has not been officially confirmed by Revolut. RTE and other outlets reported a link to a Google Cloud incident affecting the europe-west2 region, but neither Revolut nor Google has issued a joint statement confirming that cause.

How many Revolut customers are affected in Ireland?
Revolut has around 3.4 million customers in Ireland, but the company has not confirmed how many of them were directly affected by today’s disruption.

Which Revolut services were affected?
Reported categories include card payments, bank transfers, ATM withdrawals, account sign-in and premium subscription services, among the 31 services listed on Revolut’s status page.

Were other companies affected besides Revolut?
Yes. TechRadar reported that Lloyds Bank also experienced access issues for thousands of customers on the same morning, and other reports named additional UK and Ireland-facing businesses with similar access problems around the same time.

Is the Downdetector figure of 1,500 reports accurate?
That figure comes from The Next Web and reflects self-reported user complaints on Downdetector, not an official Revolut count. It has not been confirmed by Revolut and should be treated as a rough indicator of public reaction rather than a precise statistic.

When will Revolut services be fully restored?
No official timeline has been confirmed. Revolut said its engineering team was actively working to restore full service as quickly as possible, but a specific restoration time has not been published.

Revolut Outage: 31 Services Down, Google Cloud Eyed [2026]