The Briefing
- A power failure inside a single zone of Google Cloud's London data center disrupted approximately 30 to 36 services on Tuesday, October 20, freezing card payments, ATM withdrawals, and account logins for Revolut, HSBC, Lloyds, Halifax, the NHS, Royal Mail, and dozens of other platforms.
- Revolut — which now serves more than 70 million customers in 40-plus countries, including active operations in the U.S., Mexico, and Brazil — confirmed multiple services were partially or fully unavailable, with customers blocked from signing into the app entirely.
- The outage landed just weeks after Revolut received conditional OCC approval to become a U.S. national bank, intensifying questions about cloud resilience and domestic failover planning ahead of a targeted 2027 American launch.
A power event inside a single London zone of Google Cloud's infrastructure triggered a cascade of failures across the United Kingdom on Tuesday, October 20, knocking out approximately 30 to 36 cloud-hosted services and blocking card transactions, ATM access, and account sign-ins for customers of Revolut, HSBC, Lloyds, and Halifax. The disruption stretched well beyond the financial sector: the NHS, Royal Mail, parcel carrier DPD, and UK court video links all reported impact before the day was done.
The Outage Timeline
Google Cloud's status page and independent incident trackers place the start of the disruption at approximately 07:08 BST on October 20 — or 2:08 a.m. Eastern time — when elevated errors and intermittent network failures began spreading across the company's europe-west2 region, its only data center footprint in the United Kingdom. Google's public explanation fit in a single line: the company had suffered an outage due to a power event inside the europe-west2-b zone. No root cause was identified, no restoration window was committed to, and no acknowledgment that bank customers were about to find themselves locked out of their funds was included in the initial communication. By early afternoon, Google reported recovery was underway across most services, with full restoration confirmed later Tuesday.
Far More Than a Handful of Services
Infrastructure monitoring sources documented approximately 30 to 36 distinct Google Cloud products experiencing elevated error rates or full failures — Compute Engine and BigQuery among them — a number substantially higher than initial public reporting suggested. Among the affected services was Google Kubernetes Engine (GKE), the managed container platform that handles transaction processing, fraud detection, and real-time account updates for the majority of major neobanks. When GKE goes offline, the entire customer-facing experience dependent on it collapses simultaneously — payments, transfers, and balance displays — regardless of how operationally prepared an individual bank's own team might be. Google Cloud classified the incident at a medium-severity level, reflecting the breadth of products involved.
Revolut at the Center of the Disruption
Revolut, which now serves over 70 million customers across more than 40 countries, posted to X that "all our customers' money and data are safe" even as its own status page showed card payments, ATM withdrawals, bank card top-ups, and currency exchange as partially or fully unavailable. A source familiar with the matter confirmed to Reuters that the Revolut outage was directly connected to the Google Cloud infrastructure failure. The company later issued a public statement saying it had been "working to fix the issue since it was identified this morning" and expressed regret to affected customers. What made the incident particularly significant was that the outage did not merely disrupt transactions — it prevented customers from logging into the app at all, removing any ability to check their own balances while the disruption was ongoing.
The Americas Were Not Watching From the Sidelines
While the power failure originated in a single London data center zone, its effects were transatlantic. Revolut now operates in more than 40 countries, and Latin America has become a central pillar of its global expansion push. The company began operations in Brazil in May 2023 and opened full banking services in Mexico on January 27, 2026, through Revolut Bank S.A. — the first independent digital bank in that country to secure a full license through a direct regulatory application to the CNBV, which granted its authorization in October 2025. Revolut has also received authorization to establish Revolut Bank Colombia S.A., with a full public launch targeted for later in 2026 pending completion of the pre-operative regulatory phase required by Colombian banking regulators. The company has additionally been building its presence in Argentina. Taken together, Tuesday's outage hit users across an entire hemisphere that Revolut has staked significant capital on.
A U.S. Charter Now Holding Conditional Approval—and Under New Scrutiny
The outage arrived at a particularly sensitive moment for Revolut's American ambitions. The company filed applications with the OCC and FDIC on March 5, 2026, to establish Revolut Bank US, N.A., committing $500 million to the U.S. market and naming a former Visa executive as its American CEO. Then, on September 3, 2026, the OCC issued preliminary conditional approval for the charter — a significant regulatory green light that places Revolut on track to open Revolut Bank US, N.A. in Stamford, Connecticut, targeting a 2027 launch. Final approval still requires FDIC deposit insurance, Federal Reserve authorization, and completion of all OCC pre-opening conditions. The October 20 outage puts a sharp point on a question regulators may well raise before those approvals are granted: if a power event in England can prevent American customers from accessing their accounts with no domestic failover, what does the applicant's cloud resilience documentation actually say?
London Has Been Here Before
Tuesday's disruption was not the first time a power failure has frozen Google Cloud's London region. On August 12, 2024, a substation switchgear failure knocked out primary and backup power at a Google Point of Presence in the same europe-west2 area, disrupting Cloud CDN, Cloud Load Balancing, and Hybrid Connectivity. According to Google's own post-incident report, power was restored to affected networking equipment roughly 23 minutes after the initial failure — but complete service restoration across all disrupted products did not occur until more than two hours later. Tuesday's event appears to have been broader in both the range of products affected and the scale of customer impact.
What Regulators May Ask Next
The pattern surfaces a structural question the cloud and fintech industries have long deferred: as neobanks absorb customers from traditional institutions by promising around-the-clock digital access, what concrete safeguards exist against cloud concentration risk in a single provider or region? Revolut's Tuesday disruption eliminated not just payment functionality but the ability to check account balances — the most basic act of financial visibility a bank customer can perform. With Revolut now holding conditional OCC approval and scaling licensed banking operations across Latin America, that question may need formal answers in regulatory filings before too long. The European Banking Authority had already been gathering momentum toward cloud resilience reporting requirements before Tuesday's events gave the conversation new and immediate weight.
© {{Year}} Latin Times. All rights reserved. Do not reproduce without permission.