Platforms · Software · Providers · Markets
Revolut confirmed a disruption on Tuesday 20 October 2026, with customers reporting trouble accessing the app and paying by card. The company said customer money and data were safe, and that engineers were working to restore service.
Reports came from users in the UK, France and Spain, as well as customers in Romania and Ireland. Downdetector recorded more than 1,500 reports around 8 am, according to City AM. Yahoo Finance UK reported that some users could not use physical cards in shops.
Revolut's status page listed problems with sign-ins, card payments and transfers, alongside other services. The breadth of the listed functions points to an incident affecting more than one customer-facing path, but the company has not described the underlying fault.
Cloud errors leave cause unclear
Google Cloud separately reported elevated errors and intermittent network failures in its London region, europe-west2. Its status page identified Google Kubernetes Engine and Cloud Filestore among affected services. The incident started at 23:08 US Pacific time on 19 October (06:08 UTC on 20 October); Google said its engineers were investigating and offered no workaround.
Google Cloud's notice did not name Revolut, and Revolut has not attributed its disruption to a cloud provider. The two companies have a partnership, but that alone does not establish a connection between the incidents.
The company puts its personal-customer count above 80 million and its business-customer base above 800,000; it estimates 13 million customers in the UK. Finance Magnates previously reported a Revolut technical issue in June 2020 that affected registration, account verification and balance top-ups. The company said that issue was not caused by a hack; it had more than eight million customers at the time.
What an operations team should check
Operators should compare their own sign-in, card-payment and transfer monitoring against the disruption window, then check whether any failed requests need replay or reconciliation. The reported service list does not show which internal components failed, so confirm which customer journeys and downstream processes were affected before treating the status page as a complete incident picture.
For firms using Google Cloud, check whether workloads depend on services in europe-west2 and whether the reported errors overlap with local alerts. Ask providers what recovery path and workaround apply to the systems in use, and whether any transactions require review. Revolut has not identified a cause, so the available information does not establish that its disruption was related to Google's regional incident.
