A Google Cloud outage knocked Revolut’s app offline for part of Tuesday, Oct. 20, 2026, leaving customers of the fintech with failed card payments, stalled transfers and sign-in problems. Revolut’s own status page listed 28 affected services as partially unavailable, and the company later confirmed that everything was restored. The bank serves more than 80 million customers, so a disruption of this kind touches a very large user base.
The day in tech, in one email: TLDR is the daily newsletter with links and TLDRs of the most interesting stories in startups, tech and programming.
We may earn a commission if you sign up.
Twenty-eight services, from card payments to live chat
BleepingComputer, which first reported the disruption early on Oct. 20, said Revolut began by acknowledging that it was “experiencing a service disruption affecting multiple services.” The company added that customer money and data were safe. Thousands of reports piled up on Downdetector from users who could not open the app, move money between accounts or use mobile banking, and the BleepingComputer report on the outage noted that Revolut’s status page marked 28 services as partially unavailable.
The list went well past payments. It covered sign-ins, card payments, transfers, currency exchange, stock trading and live support chat. That last item mattered in practice, because the channel customers would normally use to ask what was wrong was among the things that were degraded.
Revolut’s explanation arrived later in the day. In an update posted on X, the company said that “Due to a recent Google Cloud outage, customers may have experienced temporary service disruption on the Revolut app.” A final statement said the issue had been fixed and services were restored, and BleepingComputer recorded that update at 13:52 EDT. Revolut did not say how many customers were affected, and the figure remains undisclosed. The Revolut system status page is where the company posts service health in real time.
A power event in Google’s London region
Cloud providers divide each geographic region into separate zones so that one failure stays contained, and customers are expected to spread critical workloads across them. Google’s early updates on the incident reflected that design: they suggested moving affected workloads to another zone or region where feasible. A zone-level power failure that still produced errors across the wider europe-west2 region is the harder case, because the redundancy that customers pay for depends on the neighbouring zones holding up.
Google’s own incident record places the fault in London. The Google Cloud incident page says a “power event caused an outage within europe-west2-b zone,” with the problem starting at 23:08 Pacific time on Oct. 19, which is the early morning of Oct. 20 in Britain. Other services in the europe-west2 region saw elevated errors and intermittent network problems, and Google’s final update, at 07:03 Pacific on Oct. 20, said a very small number of customers might still be affected.
The list of impacted Google products was long, and it included Compute Engine, Cloud SQL, Cloud Storage, Kubernetes Engine, Cloud Spanner, BigQuery and Pub/Sub, along with load balancing and networking services. Google said the power problem had been mitigated, though customers might not yet have been able to create new workloads in the affected zone.
BleepingComputer, citing Reuters reporting on the European outage, tied Revolut’s disruption to those continuing problems at the London data center. Neither Google nor Revolut has said publicly which specific Revolut systems ran in the affected zone, so the exact path from one failed zone to 28 degraded services is not documented in the sources reviewed. What the record does establish is the sequence: a power failure in one zone, regional errors, then a customer-facing failure at a company that told users the cause was Google Cloud.
Revolut’s scale and a rough few months for its reputation
Revolut says it serves more than 80 million customers in more than 160 countries and regions, including about 800,000 business customers, which is why a single cloud zone failing can register as a worldwide event. Banks that run on public cloud inherit the provider’s failure modes, and when the provider’s trouble is geographic, the bank’s customers can be hit far from where the hardware sits.
The outage also arrived after another unwelcome headline. In September 2026 Revolut disclosed a data breach in which personal information from an undisclosed number of customers was shared with a threat actor posing as a government agency, as BleepingComputer reported at the time. That incident and this one are unrelated in cause: one was a social-engineering failure, the other an infrastructure failure at a vendor.
For customers, the practical record is short. The disruption began on the morning of Oct. 20, the cause was named as Google Cloud, and Revolut said services were back by the afternoon Eastern time. Whether the company publishes a fuller review of the incident is still unknown. BleepingComputer also pointed to an earlier episode in September 2022, when a breach exposed data on more than 50,000 Revolut customers, as part of the background to scrutiny of the company’s operations.
This article was produced with the assistance of AI and reviewed by Morning Overview editors prior to publication.
The day in tech, in one email: Get TLDR →
We may earn a commission if you sign up.
More from Morning Overview
- Hurricane Hunter radar shows four warning signs that a tropical cyclone is about to strengthen, a University of Miami study found
- Tropical Storm Rachel is dumping up to 12 inches on four Mexican states on its way to major hurricane strength
- The FTC says Lens.com doubled the price shoppers saw in Google ads
- Common allergy, bladder and sleep pills tied to sharply higher dementia odds
