Google Cloud power event ripples through UK banking, retail and court systems
Google Cloud restored services after a power event at a third-party facility in its europe-west2 region triggered a broad outage across UK banking, commerce and public-sector platforms. The disruption hit some of the country’s most heavily used digital services in a single morning, exposing how much day-to-day activity now depends on a narrow set of cloud infrastructure providers.
Banks were among the clearest casualties. Revolut, Lloyds Bank, Halifax and Bank of Scotland all faced service problems, while users also reported trouble with Royal Mail, DPD and Forest. The outage did not remain a technical abstraction for long; it quickly became a consumer-level interruption affecting payments, access to funds and business operations.
A Google Cloud spokesperson said the disruption had been resolved and services restored after the incident was traced to a power event. The company said it would publish a fuller analysis on its service health dashboard. Even in that short statement, the operational fragility of centralized cloud architecture was obvious: a fault at one facility in one region was enough to send errors through multiple dependent services across the UK.
Banking disruption exposed the most immediate consumer harm
For customers, the outage translated into practical financial friction within minutes. Rachael Ellen, a Revolut customer in Glasgow, said she was unable to pay for parking at a shopping centre because her account was not working properly. She also could not view a transaction from a relative and received misleading reassurance from the app’s help bot that there were no pending incoming transactions.
The consumer effect here was not theoretical. Digital banking now sits at the center of routine spending, and when access fails, the consequences can range from minor inconvenience to genuine distress. A customer who cannot see a balance, confirm a transfer or complete a payment is effectively cut off from a primary financial tool, even when the money itself remains safe in the background.
Revolut said some of its services had been disrupted because of the Google Cloud outage, but that money and data remained safe throughout. More than 1,500 reports of problems were flagged to an outage monitor shortly after 08:00 BST, a sign of how quickly a cloud-level failure can scale into a mass user event.
Lloyds Banking Group customers also reported disruption affecting online banking services. A Lloyds spokesperson did not confirm the cause at first, but later said the root issues had been resolved and the company expected services to return to normal soon. For customers trying to move money, check accounts or complete time-sensitive transactions, even a short interruption can be enough to derail plans for the day.
Small businesses absorbed the operational shock
The outage also hit companies that sit downstream from the cloud but depend on it for basic trading. Guy Baybutt, who works for The Veg Box Company in Preston, said the business could not access its website to download and process customer orders while the technical problems persisted. It was also unable to book parcels onto DPD’s system for collection, creating the risk that same-day dispatches would be delayed.
For a company handling fresh produce, the breakdown had a very different character from a stalled online payment. Perishable inventory imposes a hard deadline: if orders are not processed, packed and moved quickly, products lose value and customer trust weakens. Baybutt said the outage caused lost sales because customers could not place new orders, and he described the incident as one with serious financial consequences for smaller firms that do not have the cushion to absorb lost revenue.
A single failure in cloud infrastructure can cascade through multiple layers of commerce at once. Website access, logistics platforms, payment flows and customer service systems often sit on shared digital foundations, so one interruption can knock out the full chain from order placement to delivery.
Court hearings and public services were caught in the same dependency chain
The disruption extended beyond banks and retailers. The HM Courts and Tribunals Service said it was aware of an issue affecting the video platform used for remote hearings. That detail matters because court video systems are now part of the machinery of justice, not an optional extra. When the underlying platform wobbles, hearings can be delayed, rescheduled or pushed into contingency arrangements that are harder to manage for staff, lawyers and litigants alike.
Google Cloud said the trouble began in its London data centre complex within the europe-west2 region and later identified the issue as stemming from a power event in one of its smaller zones, europe-west2-b. The company had earlier described “elevated errors and intermittent network failures” across services in the region. In practical terms, that meant failures were not limited to a single app or one isolated customer interface; the platform layer itself was unstable.
Cloud concentration leaves little room for error
The outage arrived exactly one year after more than 1,000 sites, including UK banks, were knocked offline during a separate AWS outage. The timing reinforced a hard truth about modern digital infrastructure: many organisations have concentrated critical services in a small number of hyperscale providers, then built their customer experience, payment rails and operational systems on top of those providers’ regional networks.
Prof Feng Li, associate dean for research and innovation at Bayes Business School, said the episode was a reminder of how deeply economies depend on only a handful of cloud operators. He added that it was not yet clear what caused the power problem identified by Google Cloud. Large cloud systems are complex, and failures will happen, but the real operational question is how far the disruption spreads and how quickly services recover.
That issue is becoming more visible because cloud dependency now reaches into banking, logistics, courts and basic consumer access. The more services migrate into centralized cloud regions, the more a localized infrastructure fault can resemble a broad public outage. Redundancy, failover planning and multi-region architecture are no longer technical luxuries; they are the only meaningful defense against a fault that can paralyze unrelated services at the same time.
Google Cloud said it would publish a more detailed analysis of the incident on its service health dashboard. Until that postmortem appears, the outage stands as a concrete example of how fragile a connected economy can become when too many essential services share the same underlying digital plumbing.