Platforms · Software · Providers · Markets
Customers described failures across services
Revolut said on Tuesday 20 October 2026 that a disruption was affecting its app and payments, after customers reported trouble signing in and using cards. The company posted on X that engineers were addressing the problem and said customers' money and data were safe.
Downdetector showed a rise in reports around 8 am, with more than 1,500 reports, according to City AM. Customers in the UK, France and Spain described problems, as did users in Romania and Ireland. Some said they saw a "something went wrong" message when trying to log in. Yahoo Finance UK reported that physical cards were also being declined in shops.
Revolut's status page listed disruption to sign-ins, card payments and transfers, among other functions. Its stated customer totals are more than 80 million personal customers and more than 800,000 business customers; the UK estimate is 13 million.
Google Cloud reported London errors
Google Cloud's status page recorded elevated errors and intermittent network failures affecting multiple services in its London region, europe-west2. The listed services included Google Kubernetes Engine and Cloud Filestore. Google placed the start of that incident at 23:08 US Pacific time on 19 October (06:08 UTC on 20 October), said engineers were investigating and gave no workaround.
Revolut has a partnership with Google Cloud, but the cloud provider's notice did not name Revolut, and Revolut has not identified a cause for its own disruption. The available information does not establish a connection between the two incidents.
In June 2020, Finance Magnates reported that a Revolut technical problem had stopped users registering, verifying accounts and adding funds. The company said it was not a hack and later said "everything should be working again". Cloud incidents have also disrupted other trading services: an AWS fault on 20 October 2025 affected Robinhood and Coinbase, while Binance and KuCoin paused withdrawals during an AWS disruption in April 2025.
What this means on the desk
For operations teams, the incident raises practical questions about how customer-facing status reporting maps to individual services. Can monitoring distinguish sign-in failures from card authorisation or transfer problems, and does the incident process show which functions have recovered?
The cause of Revolut's disruption remains undisclosed, and the Google Cloud notice does not connect its London incident to the fintech. Operators should check whether their dependency maps and incident alerts can correlate external provider status with service symptoms, without treating timing alone as proof of cause.
