Google Cloud power glitch stalls UK banks and small firms

According to BBC News, a power problem at Google Cloud’s London data centre ("europe‑west2") triggered an outage on Tuesday that knocked out services for several UK banks, couriers and other online platforms. The disruption highlighted how many everyday transactions now depend on a handful of cloud operators.

What went wrong and who felt it

Google said a "power event" caused an "issue with multiple services" at its UK site. By 08:00 BST the outage monitor had logged more than 1,500 reports of trouble with Revolut, and a similar flood of complaints hit Lloyds, HSBC and the HM Courts video platform. Smaller businesses were not immune – a family‑run veg box supplier could not process orders or book parcels on DPD, losing sales while fresh produce risked spoilage.

The technical chain behind a simple tap

A cloud provider rents out computing power, storage and networking so companies can run apps without owning their own servers. When Google’s data centre lost power, the virtual machines and databases that host a bank’s mobile app, a courier’s booking system or a court’s video link all went offline at once. The apps themselves did not fail; the underlying hardware did. Because most of the affected services run on the same Google infrastructure, the problem spread quickly.

How this compares to previous outages

A year earlier, an AWS (Amazon Web Services) outage took down more than 1,000 sites, including several banks. The pattern is the same: a single point of failure in a major cloud hub can ripple through diverse sectors.

What actually changes – the hidden cost of convenience

The headline is that customers could not pay for parking or view a money transfer. The deeper shift is that businesses now operate with far less redundancy. Running a backup data centre or a multi‑cloud strategy (using two providers) costs money and complexity, so many firms accept the risk to keep prices low and launch faster. The trade‑off is clear: lower operational cost in exchange for vulnerability to a provider‑wide glitch.

What to watch next is whether regulators push for mandatory resilience standards, especially for financial institutions. Professor Feng Li of Bayes Business School warned that “failures will happen” and the key is how far they spread. If more banks adopt a “cloud‑only” model, future outages could affect even more of the economy.

Who should care and why

• Consumers should know that a mobile‑banking app is not a direct line to their money; the app is just a front‑end to a cloud‑hosted backend. If the backend goes down, the app shows nothing.
• Small business owners need to ask whether their e‑commerce platform can switch to another host quickly. A simple contract clause for “service continuity” can force a provider to offer a backup route.
• Investors and board members ought to ask for a clear cloud‑risk report. The report should list which services rely on a single provider, the recovery time objective (how quickly they expect to be back), and any contingency plans.
• Policy makers might consider guidelines that require critical public services to have at least a two‑provider setup, reducing the chance that a single power fault shuts down courts or health portals.

Practical steps you can take today

1. Check your bank’s outage communication – see if they publish a status page and whether they explain the root cause. If they only say “technical issue,” ask for more detail.
2. Add a backup payment method – keep a secondary card or a cash reserve for short‑term emergencies.
3. For small business owners: test a manual order‑processing workflow that can run offline (e.g., a spreadsheet) so you can keep taking orders if the website goes down.
4. If you manage IT: map which critical apps sit on a single cloud provider and evaluate the cost of a secondary region or a different vendor.

Sources

• BBC News – Google says services recovering after cloud outage hits UK banks and websites