Revolut reports normal operations – the outage shows the cloud risk
After the disruption of 20 October, Revolut's Swiss status page shows normal operations again. The Google Cloud problem exposes a dependency that FINMA also warns about.
Revolut reports normal operations again after the outage on Tuesday, 20 October 2026. On the status page for Switzerland, all listed services were shown as operational when accessed on 21 October, including login, card payments, transfers and cash withdrawals. This supersedes the earlier report that only individual services had returned. A status display, however, is no guarantee that every single transaction has already been completed correctly.
The disruption did not affect Revolut alone. The news agency AP also reported problems at several British banks in connection with the Google Cloud outage. For customers, one distinction is therefore crucial: different bank names do not necessarily mean independent technical payment channels.
What Google documents about the incident
Google records an incident for its London cloud region on 20 October, from 8.08 a.m. to 4 p.m. Swiss time. That is seven hours and 52 minutes. This period describes the Google incident, not the duration of the outage for each Revolut service or each customer connection.
According to Google, an event in the power supply triggered an interruption in one availability zone. Several services were unreachable; elsewhere within the region, elevated error rates and temporary network problems could occur. In its last update, the provider said the effects had been resolved for most customers. A small number could still be affected. Google only announced a detailed root-cause analysis.
The documentation thus evidences a concrete technical incident. It does not yet conclusively answer why the effects differed between individual financial services. Nor can a reliable total number of affected Revolut customers in Switzerland be derived from it.
Reachability is not the same as data security
During the disruption, Revolut told AP that customers' money and data were safe. That is a statement by the company, not an independent audit of all systems. Conversely, the unavailability of an app is not in itself proof of stolen data or lost balances.
This separation matters: a payment service can be temporarily unavailable without any financial loss having occurred. Even so, such an interruption can have concrete consequences, for example when an invoice falls due or a card is needed while travelling. What compensation claims exist in an individual case cannot be determined from a general outage notice.
Clarify pending payments first
After an outage, it is worth comparing the status of individual bookings and existing payment records. A card payment shown as pending has not automatically failed. According to Revolut's help page, the amount may already have been authorised while the merchant has not yet completed the payment. The money remains reserved until the payment is completed, cancelled or the authorisation expires.
In the transaction details, Revolut shows an expected cancellation date. According to the company, pending card payments cannot simply be cancelled before that date. For transactions that remain open longer, Revolut first refers customers to the merchant. Anyone who pays again without checking risks at least additional clarification effort. An error message and a demonstrably unexecuted payment are not the same thing.
When filing a complaint, specific details help: amount, time, merchant and the displayed transaction status. This makes it easier to distinguish a single payment from a general access problem. The publicly reported resolution of the outage does not replace this clarification.
A risk beyond individual banks
For Switzerland, the cross-cutting dependency on a few IT providers is not a new question. In its 2025 annual report, FINMA notes that more supervised institutions are outsourcing critical IT to large public cloud providers. Concentrations can mean that one disruption hits several financial institutions at the same time.
Outsourcing does not release supervised companies from their responsibility. FINMA emphasises in particular the selection, monitoring and control of service providers. These general observations are not a supervisory assessment of the current Revolut incident.
In everyday life, an additional, genuinely independent payment option is practical precaution but not complete protection against all disruptions. For providers, the more demanding task lies behind the status display that has turned green again: they must be able to explain which dependencies exist, how fallback routes work and how reliably these can be used in an emergency.
