Hi, I'm SpyFrog — back again with a longer look at something that made headlines this week. Most of the time a story like this is a one-line "it's fixed now" and that's genuinely all you need. But this one is worth a slightly deeper look, because it says something interesting about how much of everyday life — for both individuals and small businesses — now quietly depends on a handful of big tech companies working properly behind the scenes.

The short version, in case you stop reading here

  • A power problem at one of Google's data centres in London caused a multi-hour outage affecting several UK services on Tuesday 20 October.
  • Revolut was hit hardest. Lloyds, Halifax, Bank of Scotland and HSBC also had problems. So did Royal Mail, DPD, Rightmove, and the video system some UK courts use.
  • This was a technical failure, not a hack. No accounts, passwords, or personal data were accessed. Google and the affected companies have confirmed everything is now resolved.
  • The real story here isn't "were you hacked" — it's "how much do ordinary people and small businesses rely on a tiny number of cloud providers without realising it."

Read on for the fuller story.

What actually happened

On Tuesday morning, Google Cloud reported a problem at its London data centre complex, known as "europe-west2" — one of the regional hubs it uses to run services for customers across Europe. The company later confirmed the cause was a "power event" in one of the smaller zones within that complex. The knock-on effect was a few hours of "elevated errors and intermittent network failures" for anything relying on that infrastructure.

Because so many companies — including banks and fintech firms — quietly run parts of their systems on Google Cloud rather than building and maintaining their own data centres, the outage rippled out well beyond Google's own products. Revolut was affected worst: for several hours, customers couldn't reliably log in, make card payments, transfer money, withdraw cash, or use in-app support chat. Lloyds, Halifax and Bank of Scotland (all part of Lloyds Banking Group) and HSBC also reported disruption to some online banking services. By the evening, Google confirmed the issue was resolved, and every affected company confirmed customer money and data remained safe throughout.

The personal impact

For most people, this showed up as a frustrating few hours rather than anything more serious — but "frustrating" undersells it for some. One Revolut customer told the BBC she was left unable to pay for parking at a shopping centre, and couldn't see whether a payment from a relative had gone through, with the in-app support bot unable to help. For anyone who relies on a single banking app with no backup card or cash on hand — which is an increasingly normal way to bank — a few hours of "unreachable" can mean a genuinely stressful gap, even once you know it isn't a security problem.

The business impact

It wasn't just individuals. A small family-run business supplying fresh fruit and vegetables across the UK told the BBC it was "severely affected": its website went down, meaning it couldn't process or download customer orders, and it couldn't book collections with delivery firm DPD — whose own systems were affected by the same outage. Orders that should have gone out that day were at risk of being delayed, and the business said it lost sales from customers who simply couldn't place an order while its website was down. Because the produce involved is fresh and perishable, a delay isn't just an inconvenience — it can mean genuine financial loss, and smaller businesses don't have the same cushion larger companies do to absorb a bad day.

Why this keeps happening

This wasn't a one-off. Almost exactly a year earlier, a separate outage at a different major cloud provider (AWS) knocked more than a thousand sites offline for hours, including UK banks. Experts have pointed out that incidents like this are really a story about concentration: a huge amount of the internet's day-to-day infrastructure — banking apps, delivery firms, property websites, even parts of the justice system — now runs on a small number of large cloud computing providers. As one academic put it, large cloud systems are complex and failures will happen; what matters most is how far they spread, how fast they're fixed, and whether people and businesses have a workable fallback when they don't work.

What to watch out for

Nothing technical here, and nothing to fix — just a couple of things worth keeping in mind whenever a story like this comes around:

  • An outage is not a breach. If your bank app was unreachable this week, that's this story — it's resolved, and there's no need to change a password or "secure your account" because of it.
  • Watch for scam messages that try to blur the two together. It's common for opportunistic scammers to send "your account was compromised, verify now" messages riding on real outage news, even when the actual story was just a technical glitch. Don't click through on anything like that — just treat it as spam and move on.
  • If you run a small business, it's worth knowing what your fallback looks like if a website, payment system, or delivery booking tool goes down for a few hours — even if that's just knowing who to call, or having a manual backup for taking orders.

Why we're writing about this at all

This one isn't really a security story at all — it's an infrastructure-dependency story, and we think those are worth understanding too. It's a useful, low-stakes reminder that "the cloud" is really just other people's computers, running in specific buildings, with the same kinds of physical failure points (like power) as anything else — and that it's worth knowing the difference between "something broke" and "someone broke in," especially once the scam messages inevitably start doing the rounds.

Questions, or something you want to flag? Just ask.