Google Cloud UK Outage Disrupts 9 Services [2026]

A Google Cloud outage tied to a power failure in London knocked out banking apps, a property listings site, a parcel courier, and parts of England and Wales’s court video system on Tuesday, October 20, 2026, before engineers brought services back online through the afternoon. The disruption traced back to the europe-west2-b zone inside Google’s London region, and it is already being cited as one of the clearest examples yet of how concentrated a single cloud provider’s regional footprint has become across UK finance and public services.

Google Cloud confirmed the root cause in a status update, stating plainly that a power event had caused the failure and that the event itself had since been mitigated, according to reporting from The Register. What followed was a cascade of user-reported problems at some of Britain’s most recognizable brands, surfaced largely through Downdetector reports rather than official confirmations from every company involved, a distinction that matters for anyone trying to separate verified fact from assumption in the hours after a major cloud event.

What Caused the Google Cloud Outage in the UK

Google Cloud’s own explanation centered on infrastructure, not software. The company said the europe-west2-b availability zone, one of three zones that make up the London region, suffered a power event that cascaded into service errors across the broader europe-west2 region. Google Cloud said the power event had been mitigated and that its engineering teams had restored full service availability, a claim repeated across multiple outlets tracking the incident throughout the day.

The timing matters for how this google cloud outage is being read by IT teams across the UK. Reports describe the disruption beginning either late in the evening of October 19, 2026, or during the morning of October 20, 2026, without a single confirmed timeline agreed across every outlet covering the story. That ambiguity is itself notable. Even hours into recovery, there was no single authoritative minute-by-minute account, only a converging set of independent reports from TechRadar and others pointing to the same zone and the same root cause.

Timeline of the Outage as It Unfolded

While no single source nailed down an exact start time, the shape of the incident is consistent across coverage. User reports of banking app failures, delivery tracking errors, and website slowdowns began climbing on the morning of October 20, with Downdetector spikes appearing for several household names roughly in parallel. That parallel timing is itself evidence of a shared dependency, since companies with no obvious business relationship to one another experiencing outages at the same moment is a strong signal that the common thread sits further down the stack, inside the cloud infrastructure layer rather than in any one company’s own code.

Google Cloud’s statement that the power event had been mitigated came after the morning disruption had already rippled through multiple sectors. The company’s language, framed around mitigation of the underlying power issue rather than a declaration that every downstream customer system had fully recovered, is a reminder that a cloud provider’s own status page can read as resolved well before every affected customer’s systems have caught up, reconnected, and cleared their backlogs.

Revolut, Lloyds and HSBC: Banking Disruption in Detail

Revolut was among the most visible casualties of the google cloud outage, reporting disruption to multiple services including card payments and ATM withdrawals. The digital bank moved quickly to reassure customers on the point that matters most during any fintech disruption, stating: “We can confirm that all our customers’ money and data are safe.”

Lloyds Bank, Bank of Scotland, and HSBC also had user-reported issues surfacing on Downdetector during the same window, according to tracking cited by The Independent. It is worth being precise about what that means. Downdetector aggregates self-reported user complaints, which is a meaningful real-time signal but not the same as an official confirmation from each bank that its systems were directly tied to the europe-west2 region. Several of the companies named in outage trackers have not themselves issued detailed technical post-mortems explaining exactly which Google Cloud services they depend on or how deeply.

That nuance matters for risk teams at financial institutions watching this story unfold. A bank’s core ledger might sit on entirely different infrastructure than its customer-facing mobile app, meaning a cloud region failure can look like a full outage to customers while only touching a narrow slice of the bank’s actual technology stack.

Public Sector Fallout: NHS, Royal Mail and the Courts

The public sector angle is where this google cloud outage becomes a policy story rather than purely a commercial one. NHS England and Royal Mail both had user-reported issues during the disruption window, placing two of the UK’s most essential public-facing services inside the same blast radius as a single commercial cloud region.

The most consequential public sector impact involved HM Courts and Tribunals Service, which experienced issues with its cloud video platform used for court hearings across England and Wales. A justice system function going dark, even partially, because of a regional cloud power event is the kind of single point of failure that tends to attract parliamentary attention well after the outage itself is resolved. Rightmove and DPD rounded out the list of commercial platforms with user-reported issues, spanning property listings and parcel logistics, two sectors with no shared ownership or technical architecture beyond their reliance on the same cloud region.

Google Cloud’s Official Response

Google Cloud’s public communications during the incident were terse but direct. The company’s status page stated: “Due to a power event we had suffered an outage within europe-west2-b zone. The power event is mitigated.” That framing, acknowledging the specific zone and the specific cause without initially speculating on knock-on effects for individual customers, is standard practice for hyperscale cloud providers managing a live incident, where overcommitting to a recovery timeline can create a second wave of reputational damage if the estimate slips.

Google Cloud also indicated that partial mitigation to infrastructure services would be observed within roughly thirty minutes of that update, with remaining services following afterward. Elsewhere in its incident communications, the company stated plainly that engineering teams continued to investigate the issue even as mitigation progressed, and separately offered an apology to those affected by the disruption, language captured in reporting from The Register as the incident moved through its later stages.

By the time Google Cloud said full service availability had been restored, the company’s own account treated this as an infrastructure event with a defined beginning, cause, and resolution, rather than a broader platform-wide failure. That is an important distinction for enterprise customers evaluating their own exposure: a single-zone power event is a different category of risk than a multi-region control-plane failure, even though both can look identical from inside a banking app that simply refuses to load.

Why One Availability Zone Can Take Down So Much

The core engineering lesson from this google cloud outage is about how availability zones are supposed to work versus how dependent customers actually configure their systems. Cloud providers build multiple zones within a region specifically so that a failure in one zone, like the power event in europe-west2-b, should not take down workloads that are properly distributed across zones. In practice, many customers run single-zone deployments for cost or simplicity reasons, especially for non-critical internal tools, and some critical dependencies end up concentrated in a single zone without the customer fully realizing it until an incident like this one exposes the gap.

That is almost certainly part of why services as varied as a banking app, a property portal, and a court video system all surfaced problems at roughly the same time despite having nothing to do with one another organizationally. Each one, somewhere in its stack, had a dependency routed through the affected zone or region, whether that was a managed database, a container runtime, or a background job queue.

Market and Business Impact of the Outage

No confirmed figures for financial losses, total affected customer counts, or precise outage duration have been published by any of the companies involved, and this article will not speculate on numbers that have not been officially reported. What can be said with confidence is that the breadth of sectors affected, banking, property, logistics, healthcare administration, and the justice system, makes this one of the more structurally significant cloud incidents affecting the UK this year, simply because of how many unrelated critical functions touched the same infrastructure layer at once.

Insurance industry coverage of the incident, cited by The Paypers, framed the event as an accumulation risk scenario, the kind of simultaneous multi-sector failure that cyber insurance underwriters have been pricing into their capacity decisions for years precisely because a single infrastructure failure can trigger claims across dozens of unrelated policyholders at once. That framing is likely to resurface in boardroom risk discussions well beyond the companies named in today’s reporting.

Historical Context: A Pattern of Concentrated Cloud Risk

This is not the first time a regional cloud failure has produced headlines disproportionate to the provider’s own market share in a given country. The pattern recurs because modern digital infrastructure in finance, retail, and government increasingly routes through a small number of hyperscale providers, and the UK’s finance and public sectors lean heavily on both Google Cloud and its two largest rivals for core workloads. Every time one of these regions has a bad day, the resulting outage tends to surface the same uncomfortable truth: resilience plans that look solid on paper, with multi-zone redundancy built in, do not always hold up when the underlying power or network infrastructure itself is the failure point rather than a software bug the provider can patch remotely.

Regulators in the UK, including the Bank of England and the Financial Conduct Authority, have spent recent years pushing operational resilience rules specifically aimed at reducing single-provider concentration risk in financial services. A google cloud outage that visibly disrupts multiple regulated banks on the same morning is precisely the kind of event those rules were designed to anticipate, and it will likely be cited in future regulatory reviews of how well banks have actually implemented multi-cloud or multi-region failover in practice rather than just on compliance documentation.

Competitive Comparison: Google Cloud vs AWS vs Azure Reliability

Every major hyperscaler has had its own high-profile regional outages, and no single provider can currently claim a clean record. The comparison that matters for enterprise buyers is less about which provider is immune to failure, since none are, and more about how transparently each one communicates during an incident and how quickly recovery actually tracks against its own public estimates. Google Cloud’s handling of this incident followed a familiar playbook: identify the zone, name the cause, commit to a mitigation timeline, and update as recovery progresses.

Factor	Google Cloud	AWS	Microsoft Azure
UK/London region zones	3 zones (europe-west2)	3 zones (eu-west-2)	3 zones (UK South)
Public status page	status.cloud.google.com	health.aws.amazon.com	status.azure.com
Named UK financial customers	Revolut, Lloyds, HSBC, Bank of Scotland (reported)	Multiple major UK banks (not named in this incident)	Multiple major UK banks (not named in this incident)
Incident cause disclosed today	Power event, europe-west2-b	Not applicable to this incident	Not applicable to this incident
Public acknowledgment of fault	Yes, confirmed and apologized	Not applicable to this incident	Not applicable to this incident

The table above reflects only what is confirmed about today’s specific incident. It is not a judgment on the overall reliability record of AWS or Azure, neither of which was implicated in this particular google cloud outage, but it does illustrate why enterprises increasingly treat zone count and incident transparency as factors in vendor selection rather than price alone.

Affected Services and Sectors at a Glance

Organization	Sector	Reported Impact	Source of Report
Revolut	Digital banking	Card payments, ATM withdrawals, transfers disrupted	Company statement
Lloyds Bank / Bank of Scotland	Retail banking	User-reported service issues	Downdetector / media reports
HSBC	Retail banking	User-reported service issues	Downdetector / media reports
Rightmove	Property listings	User-reported service issues	Downdetector / media reports
DPD	Parcel logistics	User-reported service issues	Downdetector / media reports
Royal Mail	Postal and logistics	User-reported service issues	Downdetector / media reports
NHS England	Public healthcare	User-reported service issues	Downdetector / media reports
HM Courts and Tribunals Service	Public justice system	Cloud video platform issues affecting hearings	Official service confirmation

It is worth repeating that not every entry in this table has been confirmed by the named organization itself as being directly caused by the google cloud outage. Several appear in the table because they surfaced on outage-tracking services like Downdetector during the same window, which is a strong circumstantial signal but not a substitute for each company’s own incident report.

Industry Voices on the Outage

Google Cloud’s own incident communications are the clearest first-hand account available right now, and they are worth quoting directly rather than paraphrasing, since the exact wording shapes how seriously affected customers should weigh the company’s recovery claims. In its status update, Google Cloud stated: “Due to a power event we had suffered an outage within europe-west2-b zone. The power event is mitigated,” a statement published on the company’s Service Health dashboard and echoed across multiple outlets tracking the incident.

On the recovery timeline specifically, Google Cloud told customers: “Partial mitigation to infrastructure services will be observed within the next 30 minutes and the remaining services will be mitigated there after,” a statement that set expectations for a staged return to normal rather than an instant fix. The company’s public posture also included direct accountability language. According to The Register’s coverage of the incident, Google Cloud said: “We apologize to all who are affected by the disruption,” and separately confirmed that “Our engineering team continues to investigate the issue” even as mitigation steps were already underway.

Revolut’s own statement, reassuring customers that “all our customers’ money and data are safe,” rounds out the small set of verifiable, named, on-record statements tied to this specific incident. Any additional analysis attributed to unnamed executives or analysts should be read with appropriate skepticism until those individuals are named and quoted directly by a verifiable outlet.

What This Means for UK Cloud Resilience Policy

The UK has spent the past several years tightening operational resilience expectations for banks and other critical service providers, in part motivated by exactly this kind of scenario: a single infrastructure failure rippling across sectors that regulators consider too important to fail simultaneously. A google cloud outage that visibly touches banking, healthcare administration, and the justice system on the same morning strengthens the argument for mandatory multi-cloud failover testing rather than voluntary best practice.

It also raises a harder question that regulators have been reluctant to force into the open: how many of the UK’s critical services actually have a tested, working failover to a second cloud provider or a second geographic region, versus how many simply assume their existing multi-zone setup within a single provider’s region is sufficient. Today’s incident suggests that assumption deserves renewed scrutiny, particularly for public services like HM Courts and Tribunals Service where an outage has direct consequences for people’s legal proceedings, not just inconvenience.

Predictions: What Comes Next After This Outage

Google Cloud will likely publish a detailed post-incident report in the coming days, naming the specific hardware or power infrastructure failure mode behind the europe-west2-b event, following its standard practice for significant regional incidents.
UK financial regulators will probably reference today’s google cloud outage in upcoming operational resilience guidance, using it as a concrete case study rather than a hypothetical scenario.
Expect renewed enterprise interest in multi-region and multi-cloud architecture reviews across the banking and public sectors named in today’s reports, even though implementing true multi-cloud failover is costly and slow to execute.
Cyber and operational risk insurers are likely to revisit accumulation risk models for UK customers concentrated on a single hyperscale cloud region, building on the framing already appearing in insurance trade coverage of this incident.
Additional affected organizations beyond those named today may surface in the coming days as smaller businesses and public bodies complete their own internal reviews of which systems touched the europe-west2 region during the outage window.

How to Protect Your Business From the Next Regional Cloud Outage

For IT and engineering teams reading this as a wake-up call rather than just news, a few practical steps stand out. First, confirm which of your production workloads actually span multiple availability zones versus which ones quietly depend on a single zone for a managed service, a database replica, or a background job runner. Second, test your documented failover procedures on a schedule, not just after an incident, since a failover plan that has never been exercised under load is a plan with unknown failure modes of its own.

Third, treat your cloud provider’s status page as a starting point for your own incident response, not the final word on whether your specific systems have recovered. Google Cloud’s confirmation that the power event was mitigated did not necessarily mean every downstream customer system had finished reconnecting, clearing queued jobs, and verifying data consistency. Building that distinction into your own incident runbooks will save confusion the next time a major provider has a bad morning.

Frequently Asked Questions

What caused the Google Cloud outage in the UK on October 20, 2026?
Google Cloud said a power event inside its europe-west2-b availability zone, part of the London region, caused the disruption, which led to elevated errors and intermittent network failures across the broader europe-west2 region.

Is the Google Cloud outage fixed now?
Google Cloud said the power event was mitigated and that engineering teams had restored full service availability. Individual customer systems may have continued recovering, reconnecting, and clearing backlogs after that point.

Which banks were affected by the Google Cloud outage?
Revolut confirmed disruption to card payments, ATM withdrawals, and transfers. Lloyds Bank, Bank of Scotland, and HSBC had user-reported issues surface on outage-tracking services during the same window.

Was customer money or data at risk during the outage?
Revolut stated directly that all customer money and data remained safe during the disruption. No reports in official coverage of this incident indicate data loss or unauthorized access tied to the outage.

Did the outage affect UK courts?
HM Courts and Tribunals Service experienced issues with its cloud video platform used for hearings in England and Wales, affecting the ability of some hearings to proceed as scheduled.

Were NHS England and Royal Mail affected too?
Both organizations had user-reported issues appear on outage-tracking services like Downdetector during the same window as the broader google cloud outage, though neither has published a detailed technical statement confirming the exact scope of impact at the time of writing.

Is this the first major Google Cloud regional outage?
No. Hyperscale cloud providers, including Google Cloud, AWS, and Microsoft Azure, have each experienced regional incidents in recent years. What makes today’s event notable is the breadth of unrelated UK sectors, finance, logistics, healthcare administration, and the justice system, that intersected with the same affected region at once.

What should businesses do to avoid being affected by a future cloud outage?
Security and infrastructure teams generally recommend auditing which workloads truly span multiple availability zones, regularly testing documented failover procedures, and avoiding the assumption that single-region redundancy is sufficient for mission-critical systems, particularly in regulated sectors like banking and public services.