Revolut Outage Disrupts Online Banking Services Worldwide

What happened during the Revolut outage

In the early hours of today, Revolut experienced a system failure that rendered most of its core services unavailable. Users reported being unable to log in, view balances, make payments, or withdraw cash. The disruption spread across the company’s mobile app, web portal and API endpoints, affecting customers in Europe, North America, Asia and Oceania.

Timeline of the incident

02:15 UTC – Monitoring systems flagged abnormal latency in transaction processing.
02:30 UTC – Customer support began receiving a surge of tickets reporting login failures.
03:00 UTC – Revolut issued a brief statement acknowledging a technical issue and that engineers were investigating.
04:45 UTC – Partial functionality was restored for balance queries, but payments remained blocked.
06:20 UTC – Full service resumed after a series of database rollbacks and server restarts.

The company continued to post updates on its status page and social channels throughout the event.

Impact on users and businesses

More than 15 million active users rely on Revolut for everyday banking tasks. The outage prevented them from paying bills, receiving salaries, and completing e‑commerce transactions. Small businesses that use Revolut for invoicing reported delayed cash flow, while freelancers were unable to receive client payments.

Banking services affected

Account login and balance display.
Domestic and international money transfers.
Card payments, both online and in‑store.
Currency exchange and crypto trading features.
Automated savings and budgeting tools.

Financial news outlets highlighted the ripple effect on partner platforms that integrate Revolut APIs for payment processing.

Technical root causes and response

Revolut’s engineering team traced the outage to a cascade of failures in its cloud‑based infrastructure. A scheduled update to a load‑balancing component introduced a misconfiguration that overwhelmed database connections. When the connection pool exhausted, authentication services timed out, causing a chain reaction across dependent micro‑services.

How Revolut addressed the issue

After identifying the misconfiguration, the team executed a rollback to the previous stable version. They then performed a series of health checks, cleared stale connections, and gradually restored traffic to avoid a repeat of the overload. Post‑mortem documentation, which the company promised to publish, will detail the steps taken and the safeguards to be implemented.

Regulatory and security implications

Outages of this magnitude attract scrutiny from financial regulators who oversee the stability of digital banking providers. In the United Kingdom, the Financial Conduct Authority (FCA) requires firms to maintain robust operational resilience. A similar framework exists in the European Union under the Digital Operational Resilience Act (DORA).

What regulators say

The FCA’s guidance emphasizes the need for real time monitoring, clear incident communication and compensation mechanisms for affected customers. Official FCA website outlines expectations for fintech firms during service disruptions. In Europe, the European Banking Authority has published a technical standard on cloud service continuity, which highlights the importance of automated failover testing. European Banking Authority provides detailed recommendations that align with Revolut’s recent resilience investments.

Lessons for fintech resilience

The Revolut incident underscores several key lessons for the broader financial technology sector. First, complex micro‑service architectures demand rigorous change management and automated rollback capabilities. Second, transparent communication with customers can mitigate reputational damage during crises. Third, regular stress testing of critical pathways, especially those handling authentication and transaction routing, is essential.

Best practices for future stability

Implement blue‑green deployments to isolate new code from production traffic.
Maintain redundant database clusters with automatic failover.
Adopt industry‑standard monitoring tools that trigger alerts before latency reaches user‑visible thresholds.
Publish real‑time status dashboards that provide clear updates and estimated restoration times.
Conduct quarterly tabletop exercises with regulatory bodies to align on incident response protocols.

By integrating these measures, fintech firms can reduce the likelihood of prolonged outages and protect both consumer confidence and market stability.

Revolut’s rapid restoration of services demonstrates the company’s technical competence, yet the episode serves as a reminder that even well funded digital banks must continuously invest in operational resilience. As the fintech landscape evolves, regulators, providers and users will all benefit from heightened focus on system robustness and transparent communication.