Revolut back online after Google Cloud London outage

Revolut's UK status page read "All systems are operational" when checked late on 20 October 2026, with sign-in, card payments, transfers and ATM withdrawals all listed as working. That followed disruption earlier the same day to exactly those services, during a Google Cloud incident in the company's London region.

For UK customers, the practical effect was that a card might be declined at a till, a transfer might not go through, a cash machine withdrawal might fail, and the app might not open. ITV News reported that Revolut had flagged problems across those services on 20 October. Reuters separately reported Revolut services showing as unavailable or partially unavailable.

It matters now because the cause points outwards: a person familiar with the matter told Reuters that Revolut's outage was linked to Google Cloud's disruption. Revolut said customers' money and data were safe.

What was affected, and what is only a report

Revolut's own service flags, as reported by ITV and Reuters, indicate that Revolut itself marked the affected services as degraded or unavailable at the time.

User submissions are a different kind of evidence. ITV reported more than 1,500 problem reports for Revolut on Downdetector earlier on 20 October. Downdetector counts people choosing to report a problem. It is not a count of failed transactions, not a count of affected customers, and not a measure of total impact. The exact observation time and the geographical scope of that figure were not specified.

Nothing in the material reviewed establishes that every UK customer, or every transaction, was affected, and there is no verified count of affected UK customers, failed payments or money lost. No source reviewed supplies those figures.

What Google has confirmed

Google said a power event caused an outage in europe-west2-b, a zone within its London region. Services elsewhere in the wider europe-west2 region could see errors and intermittent network problems. This was a London-region incident, not a worldwide Google Cloud failure.

Google's recorded incident ran from 07:08 to 15:00 BST on 20 October 2026, a duration of seven hours and 52 minutes. Those timestamps are Google's own incident boundaries. They are not a measure of how long Revolut's services were disrupted: Revolut's UK disruption has no established start or recovery time, and only a timestamped Revolut incident history or a company statement would settle it.

Google's timestamps are published in US Pacific time, which is why some coverage describes the incident as beginning late on Monday. Converted for a UK reader, the same start is Tuesday morning, 20 October, at 07:08 BST.

Google's dashboard marks the incident closed, but its final detailed update at 15:03 BST said mitigation covered most customers and that a very small number were believed to still be affected, with engineers continuing to work. Closure of an incident record is not the same as confirmation that everyone has recovered. Google said it would publish an incident analysis after its investigation; that analysis was not on the incident page when checked.

Money and data: what Revolut said

Revolut said all its customers' money and data were safe, in statements reproduced by ITV and Reuters.

That is the company's assurance, attributed to the company. It is not an independent security finding, and it does not by itself establish anything about compensation, about deposit protection, or about who bears the cost of a payment that failed at the wrong moment. Those are separate questions, and the material reviewed does not answer them.

No verified information was found on outstanding transfers, reversals, customer compensation, or reimbursement of consequential costs arising from 20 October.

What is not known

Two further gaps in the reviewed sources bear directly on customers:

• The mechanism. Primary status pages do not explain Revolut's specific technical dependency on the affected Google Cloud zone, or how the failure propagated. The Reuters link is attributed to a person familiar with the matter, not to a published technical account.
• The backlog. Whether every delayed transaction has now completed is not established. Revolut's status page carries no visible last-updated timestamp, so an "operational" reading is a point-in-time observation rather than a guarantee of a clean queue behind it.

Earlier reports describing Revolut services as down and a later status page describing them as operational are not in conflict. They are observations at different points in the day.

Where to check, and what comes next

Both companies publish their own service updates, and those pages are the primary record of what each said about 20 October:

• Revolut's UK service status: revolut.com/system-status (opens in a new tab)
• Google Cloud service health: status.cloud.google.com (opens in a new tab)

Two things are worth watching. Whether Revolut publishes a timestamped account of when its UK services failed and recovered, and how it is handling any stuck transactions. And whether Google's promised incident analysis of the europe-west2 power event appears, and what it says about the effects beyond the single affected zone.