Google Cloud outage disrupts U.K. banking services, with London region flagged

Multiple U.K. banks said they experienced disruption to customer services, pointing to an outage affecting technology infrastructure connected to Google Cloud. The reports came as Revolut described a widespread impact on payments, transfers and withdrawals, while Lloyds indicated customers were seeing problems as its systems dealt with the incident.

Yahoo Finance’s account of the situation tied the disruptions to “multiple issues” in Google Cloud’s London region. In practice, that means services that depend on cloud-based systems, connectivity, and supporting applications may slow down or fail if the underlying cloud components are degraded.

Revolut, a U.K.-focused digital bank, said customers faced problems with core financial functions including moving money and accessing cash via withdrawals. Such impacts matter operationally because payments and transfer workflows typically require reliable, real-time access to authentication systems, transaction engines, and downstream partners.

Lloyds, one of the U.K.’s largest retail banks, also reported disruption affecting customer access to services. For large banks, even partial cloud or infrastructure instability can force temporary workarounds, such as throttling transactions, delaying non-critical processes, or routing traffic to alternative systems if available.

Alphabet did not provide details in the published report about the outage’s cause, the scope across services, or an estimated timeline for restoration. The account likewise did not specify whether the incident affected all Google Cloud services or a particular subset, such as networking, compute workloads, or managed database components.

The incident underscores how tightly regulated financial services increasingly rely on third-party cloud infrastructure for customer-facing and back-office operations. When regional cloud capacity is affected, banks may need to rebalance transaction flows across systems, which can increase risk controls and customer support workload even after the technical recovery begins.

For customers and businesses, the most immediate concern is the availability of payment rails and withdrawal processing, not just website or app uptime. The report’s emphasis on payments and transfers suggests the disruption likely reached beyond user interfaces into the operational path for completing transactions.

What remains unclear from the available reporting is the duration, whether the incident was fully resolved by the time of publication, and how broadly the disruption mapped to individual bank systems versus shared dependencies within the cloud ecosystem. Alphabet and the banks may later provide more complete post-incident information, including mitigation steps and what changed operationally to prevent recurrence.