Last Updated: 26 October 2026
The google cloud outage uk disruption on Tuesday 20 October 2026 showed just how much of everyday British life now runs through a single company’s servers. When a power problem struck Google Cloud’s London data centre region that morning, banking apps faltered, court video hearings were disrupted and delivery networks wobbled — all before most people had finished their breakfast. Here is the full timeline of what happened, who was affected, what Google said, and what the google cloud outage uk incident reveals about our dependence on the cloud.
Cloud outages are rare but never minor. Because so many businesses rent their computing from a handful of giant providers, a single infrastructure failure like the google cloud outage uk one can ripple across banks, retailers, public services and logistics firms within minutes. This guide explains the October outage in plain English, shows you how to check the health of Google’s services yourself, and sets out practical steps for consumers and businesses to stay resilient the next time the cloud goes down.
What caused the google cloud outage uk incident? The google cloud outage uk incident on 20 October 2026 was caused by a power event at a third-party facility serving Google Cloud’s London region (europe-west2), which knocked out services in the europe-west2-b availability zone from just after 7am. Google said the issue was mitigated for most customers later that day and apologised to everyone affected.
What Happened: A Timeline of the Outage
The google cloud outage uk incident unfolded quickly on the morning of Tuesday 20 October 2026. Google’s own status dashboard logged the first signs of trouble at 06:08 UTC, and within the hour it was clear this was not a minor blip. Here is how the day developed:
- Just after 7:00am BST: the europe-west2-b availability zone — one of three zones inside Google’s London cloud region, europe-west2 — loses power, and multiple Google Cloud services begin reporting elevated errors and intermittent network failures.
- 07:54 UTC: Revolut posts a service-disruption statement acknowledging problems affecting multiple banking functions, as customers report being unable to make card payments or withdraw cash.
- Morning: reports of problems spread. The BBC’s live coverage reports Revolut’s acknowledgement and apology, while users of other banks and services flag issues on the outage-tracking site Downdetector.
- Mid-morning: Google confirms the cause — a power event at a third-party facility — and says its teams are working to recover services and prioritise existing workloads.
- Afternoon: most services recover. Google says the incident has been mitigated for most customers, with only a very small number still affected, and apologises to everyone caught up in the disruption.
- Late afternoon: the Ministry of Justice confirms that the courts’ Cloud Video Platform, used for remote hearings, has still not fully recovered — a reminder that restoration is rarely instant for every customer.
Euronews reporting put the start of the incident at about six in the morning GMT, with most services recovering roughly six hours later. Google also promised to publish a full analysis of the google cloud outage uk incident on its service health dashboard once its internal investigation is complete — the standard post-mortem process for major cloud failures.
Who Was Affected: Banks, Websites and Court Hearings
The google cloud outage uk incident reached well beyond Google’s own products, because so many British businesses run their digital services on Google Cloud infrastructure. One important caveat, reported by the BBC: most affected firms did not officially confirm a link to the google cloud outage uk incident, so some of these disruptions were correlated in time rather than proven to share a cause. With that caution in mind, here is what was reported:
- Revolut: the fintech bank acknowledged problems affecting multiple services. Card payments and cash withdrawals were reported as unavailable or only partly available, and its UK status page still showed partial disruption at 14:58 UTC. Reuters reported that a person familiar with the matter linked the disruption to the google cloud outage uk incident. Revolut told customers their money and data were safe and said it had been working on the issue since identifying it that morning.
- Lloyds Banking Group: said its app was functioning normally but acknowledged reports of trouble with some online services. A spokesperson told the BBC: “We are aware of similar issues affecting other organisations and are monitoring the situation closely.” Lloyds later said it expected services to be back to normal soon.
- HSBC: appeared among the services where users were reporting problems on Downdetector, according to Sky News’ live coverage — though, as Sky noted, it was not immediately clear whether all such reports were related to the Google problem.
- HM Courts and Tribunals Service: said it was aware of a problem affecting the video platform used for remote court hearings. The Ministry of Justice later confirmed the Cloud Video Platform had still not fully recovered by late afternoon.
- DPD: the delivery firm reported connection issues during the outage window.
- Royal Mail: also featured among the services with user-reported problems on Downdetector, per Sky’s reporting.
The breadth of that list is the real story. Banking, justice, logistics and communications all felt the same failure within hours — not because they share an owner, but because they share an infrastructure provider. When one building in London lost power, a surprising slice of everyday life froze with it.
What Google Said About the Power Event
Google communicated throughout the incident via its Cloud status dashboard rather than through press statements, which is standard practice for infrastructure failures. The company’s account of the google cloud outage uk incident was concise: “A power event caused an outage within europe-west2-b zone. The power event is mitigated. We are seeing the recovery of services and are prioritising the recovery of existing workloads.”
In practical terms, Google said its UK infrastructure had experienced “elevated errors and intermittent network failures” and that it was investigating further. Later on 20 October, the company said the incident had been “mitigated for most of the customers” and that only a limited number were still believed to be affected. It apologised “to all who are affected by the disruption” and committed to publishing a review of the incident once its internal investigation is finished.
Notably, Google attributed the failure to a power event at a third-party facility — a reminder that even the most sophisticated data centres depend on external power infrastructure. The full technical post-mortem of the google cloud outage uk incident, when published on the status dashboard, should explain exactly how a single facility’s power problem escalated into a multi-service outage.
Why One Power Event Could Cause So Much Disruption
A cloud outage is a period when a cloud provider’s computing, storage or networking services become unavailable or unreliable, preventing the businesses that rent them from serving their own customers. Most outages are brief and invisible. But when they strike a major region, the effects cascade, because thousands of companies — banks, shops, streaming services, government departments — all depend on the same underlying machines.
That is what made the google cloud outage uk incident so disruptive. Google’s London region, known as europe-west2, is the company’s only cloud region in the UK, divided into three availability zones (a, b and c) designed to fail independently. The power event struck zone europe-west2-b. In theory, workloads should shift to the surviving zones; in practice, customers that had not built their systems to spread across zones — or across regions — had nowhere to go. As Computer Weekly’s analysis noted, businesses without multi-region resilience had no second UK location to fail over to.
Professor Feng Li of Bayes Business School summed up the structural problem: “Google Cloud’s outage is a reminder of how deeply our economies depend on just a handful of cloud providers.” Three companies — Amazon, Microsoft and Google — host an enormous share of the world’s digital services. That concentration brings efficiency and scale, but it also means a single point of failure can have national consequences.
How to Check Google Cloud’s Status Yourself
You do not need to wait for news reports to find out whether Google’s services are healthy. The company runs a public status dashboard that is the authoritative source during any google cloud outage uk event. Here is how to use it:
- Visit the dashboard. Go to status.cloud.google.com, Google Cloud’s official service health page, which lists every product and region with a current status indicator.
- Look for the europe-west2 region. UK customers should check the London region specifically. During the October incident, the dashboard showed the europe-west2-b zone with a clear incident banner and a running timeline of updates.
- Read the incident history. Each incident gets a unique ID and a chronological log, from first detection through mitigation to resolution. Google later appends its full post-incident analysis here.
- Cross-check with Downdetector. User-reported outage trackers show whether ordinary customers are experiencing problems, which sometimes surfaces issues before official dashboards do — though reports there are unverified.
- Follow the affected company’s own status page. Banks and large services run their own status pages (Revolut’s, for example, showed partial disruption well into the afternoon), which tell you what matters most: whether your service works.
Bookmarking the status dashboard now will save you guesswork during the next incident. Outages are stressful enough without refreshing social media for rumours; the official timeline is calmer and more accurate.
What Consumers and Businesses Can Do During an Outage
For consumers caught in a google cloud outage uk style event, the advice is practical rather than technical. Keep a backup way to pay: a second bank card from a different provider, or some cash, means a single app failure does not leave you stranded at a till. Avoid repeatedly hammering the app — failed login attempts during an outage sometimes trigger security locks that persist after service returns. And check the company’s official status page before assuming your account specifically has been compromised; during October’s disruption, the fastest reassurance came from Revolut’s own statement that customer money and data were safe.
If you are wondering whether a particular service is down or it is just you, our guide on how to tell if Spotify is down walks through the same checks — status pages, Downdetector and official social channels — that work for almost any online service.
For businesses, the lessons are architectural. Spread critical workloads across multiple availability zones at a minimum, so a single zone failure does not take you offline. Larger organisations should consider multi-region designs, keeping a warm standby outside the primary region for truly critical services. Maintain an incident communication plan — a status page, pre-drafted customer messages and a single decision-maker — because during an outage, silence from a provider is almost as damaging as the outage itself. Finally, rehearse: tabletop exercises that simulate a cloud region failure reveal gaps in runbooks before a real 7am incident does.
The Bigger Picture: When the Cloud Goes Down
The google cloud outage uk incident did not happen in a vacuum. Coverage noted that it coincided with the anniversary of an Amazon Web Services failure in October 2025 that knocked more than a thousand sites offline for hours — a reminder that every major provider has bad days. The same week also brought other tech headaches, including a Google Home speaker data-download bug and Apple teasing a MacBook Pro event, making it a busy few days for anyone keeping score of big tech’s stumbles.
The deeper question is whether concentration itself is the risk. Regulators and resilience experts have been warning for years that the global economy’s dependence on three cloud providers creates systemic fragility — the digital equivalent of every bank keeping its vaults in the same building. The google cloud outage uk incident will likely sharpen those conversations in the UK, particularly around critical national infrastructure: when court hearings cannot proceed because a video platform is unreachable, the outage stops being a tech story and becomes a public-services story.
None of this means the cloud is a bad idea. Centralised, professionally run data centres are still far more reliable than the server cupboards they replaced. But the bargain only works if customers build for failure — assuming, from day one, that any single zone, region or provider can and will go dark. The companies that sailed through the google cloud outage uk disruption on 20 October with barely a flicker will be the ones that designed for exactly that morning.
Conclusion
The google cloud outage uk incident of 20 October 2026 began with a power event in a single London availability zone and ended as a national case study in digital dependence. Banks, courts, couriers and countless websites felt it within hours; most recovered the same day; Google apologised and promised a full analysis. The timeline is now a matter of record — but the lesson is forward-looking.
Whether you are a consumer or a business, the takeaway from the google cloud outage uk incident is the same: hope is not a resilience strategy. Keep a backup payment method, bookmark the Google Cloud status dashboard, and ask your providers — or your IT team — what happens when a zone goes dark. The next outage is a matter of when, not if. If this explainer helped, share it with someone whose business runs in the cloud, and check our service-status guides so you are never left guessing the next time a screen goes blank.
What caused the Google Cloud outage in the UK?
Google said the outage was caused by a power event at a third-party facility serving its London cloud region (europe-west2). The power event knocked out services in the europe-west2-b availability zone from just after 7am BST on 20 October 2026. Google has promised a full post-incident analysis once its internal investigation is complete.
When did the Google Cloud outage happen?
The outage began on Tuesday 20 October 2026. Google’s status dashboard logged the first signs of trouble at 06:08 UTC, and the europe-west2-b zone lost power just after 7:00am BST. Most services had recovered roughly six hours later, although some customers, including the courts’ video platform, took longer to return to normal.
Which banks were affected by the Google Cloud outage?
Revolut acknowledged disruption to card payments, cash withdrawals and other banking functions. Lloyds said its app was functioning normally but acknowledged issues with some online services. HSBC appeared among services with user-reported problems on Downdetector. Note that most affected firms did not officially confirm a link to Google, so some reports were correlated in time rather than proven to share a cause.
Was my money safe during the Google Cloud outage?
Revolut told customers that their money and data were safe during the disruption, describing the problem as a third-party issue it had been working on since identifying it that morning. The outage affected access to services such as payments and withdrawals rather than the security of customer funds.
How can I check if Google Cloud is down?
Visit status.cloud.google.com, Google Cloud’s official service health dashboard, which lists every product and region with a current status indicator and a chronological incident log. UK customers should check the europe-west2 (London) region. You can also cross-check with user-reported trackers such as Downdetector and the affected company’s own status page.
Will Google publish a report on the outage?
Yes. Google said it will publish an analysis of the incident on its service health dashboard once its internal investigation is finished. Major cloud providers routinely release post-mortems explaining the root cause and the steps taken to prevent a repeat.
