Revolut confirmed a service interruption today that left users in several European countries, including Spain, the UK and France, unable to use the app normally. People reported login errors, no access to balances or transfers, and in some cases cards that stopped working for payments.
A few details stand out for anyone who runs production systems:
- Status page vs. real experience. According to the reports, Revolut's status site showed normal indicators at some points while users were still locked out. If your health checks don't reflect what a customer actually does (log in, see a balance, pay), your status page can tell a different story from your support queue.
- The client can't fix a backend failure. Reinstalling or clearing the app doesn't help when the problem sits in the provider's infrastructure, so clear in-app messaging matters.
- Root cause is still unconfirmed. Some reports point to a Google Cloud issue in a London region, but Revolut hasn't confirmed this or given a recovery timeline. Worth waiting for a post-incident report before drawing conclusions.
For users, the practical advice is simple: keep a second payment method (cash or a card from another bank) and follow the company's official channels.
The full report, with what is confirmed and what isn't, is on Tadna: Revolut outage: users without access to accounts and payments
Top comments (0)