Digital Transformation · 21 October 2026
Google Cloud London zone outage disrupts Lloyds, HSBC, Royal Mail, Revolut
A Google Cloud availability zone in London, europe-west2-b, went down and disrupted several customer-facing services, including Lloyds, HSBC, Royal Mail and Revolut, according to The Register. No recovery time or workaround has been reported.
What happened
A Google Cloud availability zone in London, europe-west2-b, has gone down and taken several customer-facing services with it, including those of Lloyds, HSBC, Royal Mail and Revolut. The Register reports that no recovery time has been given and that no workarounds are currently available to affected customers.
The disruption is reported as affecting multiple services at once rather than a single application. Because the four organisations named are consumer-facing banks, a postal operator and a digital bank, the impact is likely to be felt by members of the public as well as by internal teams, though the report does not detail the specific failures each service experienced.
At the time of writing, the only source available to us is The Register's account. We have not seen an official incident statement from Google Cloud, and the cause of the outage has not been established in the reporting we reviewed.
Why it matters
The story is less about one provider's bad day and more about how deeply a handful of regional cloud zones now underpin the services people use every day. When a bank app, a parcel tracking service and a payments platform fail together, the common dependency becomes the most important fact for both operators and customers. It also shows how quickly a technical incident becomes a service failure: a customer who cannot log in or pay has no interest in which layer of the stack broke.
For leaders in digital transformation, the lesson sits in architecture and operating model. Moving to the cloud has delivered speed and scale, but it has also concentrated risk in places that many organisations only discover during an incident. Where there are no workarounds, the experience depends on decisions made long before the outage, including how services fail over, how staff are equipped to respond, and what customers are told while they wait.
By the numbers
- europe-west2-b: the specific London zone identified in the reporting as the source of the disruption.
- Four named organisations affected in the report: Lloyds, HSBC, Royal Mail and Revolut.
The Renascence take
Most coverage of an outage like this will focus on the provider. The more useful question for a customer-obsessed operator is what its own customers experience when the dependency fails, and whether anyone designed that moment on purpose.
The real failure is the assumption that a cloud zone is a unit of resilience the customer will never see. Customers do not experience europe-west2-b; they experience a banking app that stops responding and a parcel that has no status. Operators should map which customer journeys depend on a single zone, pre-write honest status messages for the moments when no workaround exists, and rehearse the fallback experience as rigorously as they test the primary one.
Sources
This briefing was written by our Newsdesk, synthesising reporting from the outlets below. Follow the links for the original coverage.
FAQ
Questions we get on this topic
More in Digital Transformation
Stay ahead of CX
Get the signal, not the noise.
The stories shaping customer experience — plus the Journal and Experience Loom — in your inbox.


