Google Cloud Outage disrupted several essential services across the United Kingdom on Tuesday, October 20, 2026, affecting banks, delivery companies, court hearings, and small businesses. Google Cloud later confirmed that services had been restored after a power-related incident at a third-party facility in its London cloud region.
The disruption highlighted how heavily modern businesses and public services depend on cloud infrastructure. When a major cloud provider experiences technical problems, the consequences can extend beyond websites and applications, affecting payments, customer orders, business operations, and access to essential digital services.
Google said the incident affected its europe-west2 region, which serves London. The company apologised to affected customers and said it would publish a detailed analysis through its service health dashboard.
Among the organisations reporting problems were Revolut, Lloyds Banking Group services, Royal Mail, DPD, and HM Courts and Tribunals Service. Smaller companies also faced operational difficulties, demonstrating that cloud outages can create financial pressure for businesses of every size.
In this article, we examine the Google Cloud Outage, its reported cause, the services affected, its consequences for businesses, and the lessons organisations can learn from the incident.
Table of Contents
What Happened During the Google Cloud Outage?
The Google Cloud Outage affected multiple services operating through Google’s London cloud infrastructure early on Tuesday. Google initially reported elevated error rates and intermittent network failures across several cloud products in its europe-west2 region.
The disruption affected organisations that rely on cloud infrastructure to operate websites, applications, digital transactions, and internal systems.
Google later confirmed that the incident had been resolved. According to the company, a power event at a third-party facility caused the disruption within its London cloud region.
The company apologised to customers who experienced service interruptions and said it would provide a more detailed incident analysis on its service health dashboard.
Although Google reported that services had been restored, individual businesses still needed to confirm that their own systems were operating normally.
Which services were affected?
Several types of services experienced problems during the incident.
- Banking services: Revolut users reported difficulties accessing services, while customers of Lloyds Banking Group brands reported online banking problems.
- Postal and delivery operations: Royal Mail and DPD were among the services affected by the disruption.
- Court hearings: HM Courts and Tribunals Service reported problems with the video platform used for remote hearings.
- Small businesses: Some companies could not access websites, retrieve customer orders, or arrange deliveries.
- Digital applications: Google reported errors and intermittent network failures affecting multiple cloud products in the London region.
The incident demonstrated that an infrastructure problem can affect different industries at the same time when their services depend on shared technology.
What Caused the Google Cloud Outage?
Google attributed the disruption to a power event at a third-party facility serving its europe-west2 cloud region in London.
The company later identified europe-west2-b as the affected zone. A cloud region is a geographic location containing infrastructure used to host applications, store data, and deliver online services. Regions can contain multiple zones designed to support cloud workloads.
However, having several zones does not automatically guarantee uninterrupted service. The way applications are deployed, how dependencies are configured, and whether workloads can move to alternative infrastructure all influence resilience.
Understanding the power-related incident
Cloud data centres require dependable electrical infrastructure to support servers, networking equipment, storage systems, and cooling systems. Power disruptions can affect the availability of these resources even when a cloud provider operates large facilities with multiple protective measures.
Google’s statement linked the incident to a power event at a third-party facility. The available information does not establish every technical detail of the failure, so further conclusions about the precise equipment involved or the full sequence of events would be premature.
The incident also illustrates the importance of understanding dependencies outside a cloud provider’s immediate control. Facilities, power systems, networking arrangements, and other infrastructure can all influence service availability.
Why did the problem affect multiple services?
Many organisations use cloud platforms as the foundation for applications that customers access every day. These applications may support account access, payment processing, order management, communications, or document handling.
If a critical cloud service becomes unavailable, applications that depend on it may stop working or experience intermittent errors.
The consequences depend on each organisation’s technical architecture. A business that distributes its workloads across independent locations and has tested recovery procedures may be better positioned to maintain operations than one relying on a single deployment.
For updates on cloud service availability, users and businesses can consult the official Google Cloud Service Health dashboard.
Banks and Digital Payments Faced Disruptions
Financial services were among the most visible sectors affected by the Google Cloud Outage. Revolut, Lloyds Bank, Halifax, and Bank of Scotland customers reported difficulties accessing online services during the disruption.
These reports highlighted how dependent everyday financial activities have become on digital platforms.
Customers increasingly use mobile applications and online banking for payments, transfers, account balances, and other routine transactions. When a service becomes unavailable, even a temporary interruption can create practical difficulties.
Revolut confirmed service disruption
Revolut confirmed that some of its services had been disrupted by the Google Cloud incident. The company later said its services had been fully restored.
Revolut also stated that customer money and data remained safe throughout the incident.
More than 1,500 reports involving Revolut were recorded during the affected period, according to the supplied reporting. These reports indicated widespread user difficulties, although outage-reporting figures do not necessarily represent the total number of affected customers.
The disruption had practical consequences for some users. One customer, Rachael Ellen from Glasgow, told BBC News that she could not pay for parking because she could not access her money. She also could not see an incoming transaction from a relative.
The example demonstrates how a technology incident can interfere with ordinary activities, even when the underlying issue is not a confirmed loss of funds.
Lloyds Banking Group customers also reported problems
Customers of Lloyds Bank, Halifax, and Bank of Scotland also reported difficulties with online banking.
Lloyds Banking Group did not confirm that Google Cloud caused its reported disruption. The bank said the underlying issues had been resolved and that services were expected to return to normal.
This distinction is important because separate organisations can experience service problems around the same time without every incident necessarily sharing the same cause.
Customers experiencing banking disruptions should check their bank’s official communications before repeating a suspected cause or assuming that an account has been compromised.
What should banking customers do during an outage?
Customers can take several practical steps when a banking application becomes unavailable.
- Check the bank’s official website or verified social media accounts for service updates.
- Avoid repeatedly submitting the same payment if its status is unclear.
- Review transaction history when services return to confirm whether a payment was completed.
- Use an alternative payment method where appropriate and available.
- Never share passwords, one-time verification codes, or banking credentials with people claiming to offer outage assistance.
A service outage does not automatically mean that customer funds or personal information have been compromised. However, customers should rely on verified information from their financial institution.
Courts and Delivery Services Were Also Affected
The Google Cloud Outage extended beyond financial services, affecting parts of the UK’s delivery and public-service infrastructure.
Royal Mail, DPD, Forest, and HM Courts and Tribunals Service were among the organisations reporting problems.
These disruptions show how cloud infrastructure can support activities that people may not immediately associate with cloud computing.
Remote court hearings experienced problems
HM Courts and Tribunals Service reported difficulties with the video platform used for remote hearings.
Remote hearings allow participants to attend proceedings through digital communication systems rather than travelling to a physical courtroom. They can help improve access and reduce travel requirements, but they also depend on reliable technology.
When a video platform becomes unavailable, participants may experience delays, technical difficulties, or the need to rearrange proceedings.
The reported incident highlights the importance of contingency arrangements for digital public services. Organisations that rely on remote hearings need clear procedures for communicating disruptions and managing affected appointments.
The available information does not establish how many hearings were delayed or whether all affected proceedings were rescheduled.
Delivery services faced operational difficulties
Royal Mail and DPD were also among the services affected by the incident.
Modern delivery operations depend on connected systems for booking parcels, managing orders, tracking shipments, and communicating with customers. A disruption to one part of this process can create delays elsewhere in the delivery chain.
For example, a business that cannot create a shipping label may be unable to dispatch an order even when the parcel is already packed and ready.
Similarly, customers may have difficulty accessing tracking information or receiving timely updates if the systems supporting these functions are unavailable.
The precise impact varies by organisation and service. Nevertheless, the incident illustrates why delivery companies and their business customers need backup procedures for essential shipping tasks.
Small Businesses Faced Financial Challenges
The Google Cloud Outage also affected smaller businesses that rely on online systems to manage orders and serve customers.
One example was The Veg Box Company, a family-run fresh produce business. Guy Baybutt, who works for the company, told the BBC that the business could not access its website to download and process customer orders.
The company also experienced difficulties booking parcels through DPD, creating a risk of delivery delays. Customers were unable to place new orders while the website was inaccessible.
Why a short outage can be expensive
For a small company, a website is often more than a marketing tool. It may be the primary channel through which customers browse products, place orders, make payments, and receive information.
If the website becomes unavailable, the business may lose sales during the interruption.
Operational problems can continue even after the website returns. Staff may need to recover outstanding orders, contact customers, arrange delayed deliveries, and reconcile transactions that were not completed.
Businesses dealing with perishable goods face additional pressure because delays can affect product quality and delivery schedules.
Unlike larger companies, smaller businesses may have fewer resources to absorb unexpected losses or maintain alternative systems.
How businesses can reduce the impact
Companies can prepare for infrastructure disruptions by developing a practical continuity plan.
Useful measures include maintaining secure backups, keeping customer contact information accessible through appropriate alternative systems, documenting manual order-processing procedures, and ensuring staff know how to communicate service interruptions.
Businesses should also identify which systems are essential to daily operations and whether those systems depend on a single cloud region or external provider.
A backup website alone may not be sufficient if order databases, payment processing, or delivery integrations remain unavailable. Resilience requires understanding the complete chain of dependencies.
Why Cloud Infrastructure Outages Matter
The Google Cloud incident highlights the concentration of digital services around a relatively small number of major infrastructure providers.
Google Cloud, Amazon Web Services, and Microsoft Azure provide cloud computing services used by organisations across numerous industries.
Cloud platforms allow businesses to access computing capacity, storage, databases, networking, and managed software without having to operate every underlying component themselves.
This model offers significant benefits, including scalability, access to advanced technology, and the ability to deploy services across multiple locations.
However, widespread reliance on a shared infrastructure provider can create a common point of disruption.
The risks of relying on a single cloud region
A company may host its website and supporting applications in one geographic region because doing so is straightforward or cost-effective.
If a regional incident affects a critical service, the company may have limited alternatives unless it has designed and tested a recovery strategy.
Deploying applications across multiple zones can improve resilience against certain failures, but regional incidents may require a different level of preparation.
Depending on business requirements, organisations may consider cross-region backups, replicated databases, alternative service configurations, and documented disaster-recovery procedures.
These measures can introduce additional costs and complexity. Businesses should therefore evaluate their needs according to the importance of each service, the potential financial impact of downtime, and the time required to restore operations.
What industry experts say
Professor Feng Li, associate dean for research and innovation at Bayes Business School, said the incident demonstrated how heavily modern economies depend on a small number of major cloud providers.
He also emphasised that failures in large cloud systems are unavoidable, making the scale of disruption, speed of recovery, and availability of alternatives particularly important.
The point is not that cloud technology should be avoided. Rather, organisations need to understand that outsourcing infrastructure does not remove the need for operational risk management.
Businesses remain responsible for deciding how their applications are configured, how data is protected, and what happens when a service becomes unavailable.
A reminder of the AWS outage
The incident also came exactly one year after an outage at Amazon Web Services’ largest cloud site disrupted more than 1,000 websites, including UK banks, for several hours, according to the supplied report.
The comparison highlights a recurring challenge in modern digital infrastructure: a technical incident at a major provider can affect organisations that might otherwise appear to operate independently.
As cloud adoption grows, businesses must balance the advantages of shared infrastructure with the need for reliable recovery arrangements.
Lessons Businesses Can Learn From the Google Cloud Outage
The incident offers several practical lessons for organisations of different sizes.
1. Develop a disaster-recovery plan
Businesses should document how essential operations will continue if a cloud service becomes unavailable.
The plan should identify responsible staff, recovery priorities, backup systems, communication channels, and procedures for restoring operations.
A plan is most useful when employees have tested it rather than simply stored it in a document.
2. Identify critical dependencies
Companies should map the services required to keep their websites, applications, payments, and order systems operating.
These dependencies may include cloud databases, authentication services, external APIs, delivery integrations, and payment providers.
Understanding these relationships helps organisations identify where a single failure could interrupt several business functions.
3. Maintain reliable backups
Backups should be protected against accidental deletion, unauthorised access, and failures affecting the primary environment.
Businesses should regularly test whether backed-up data can actually be restored and whether the recovered information is complete.
A backup that cannot be restored quickly may provide less protection than expected.
4. Consider multi-region resilience where necessary
For services that cannot tolerate extended downtime, deploying selected workloads across multiple regions may improve availability.
However, multi-region infrastructure is not automatically failproof. Data replication, application dependencies, security controls, and failover procedures all require careful design.
Companies should choose an approach that matches their operational needs and budget.
5. Communicate clearly with customers
During an outage, customers need accurate information about unavailable services, expected next steps, and alternative ways to complete important tasks.
Businesses should avoid promising a restoration time unless they have reliable information to support that estimate.
Clear updates can reduce confusion and help preserve customer trust.
6. Review service-level agreements
Organisations should understand the availability commitments and remedies offered by their cloud providers.
They should also review whether contractual terms address the specific services they depend on and what support is available during an incident.
A service-level agreement cannot prevent every outage, but it can help businesses understand their rights and responsibilities.
7. Review incidents after recovery
When normal operations resume, businesses should evaluate what failed, how long the interruption lasted, and which contingency measures worked.
The review should identify improvements rather than focus only on assigning blame.
Organisations can then update their continuity plans and test the revised procedures.
Final Thoughts
The Google Cloud Outage demonstrated how a power-related incident at a third-party facility can disrupt digital services across multiple industries.
Although Google confirmed that services had been restored, the incident affected banking access, delivery operations, remote court hearings, and the ability of smaller companies to process customer orders.
The broader lesson is that cloud computing provides valuable infrastructure, but no provider can guarantee that every service will remain available at all times.
Businesses need to understand their technology dependencies, protect essential data, prepare alternative operating procedures, and communicate effectively when problems occur.
For customers, checking official service updates and avoiding unverified claims can help reduce confusion during an outage.
As organisations become more dependent on cloud platforms, reliable recovery plans and resilient digital infrastructure will remain essential to keeping everyday services running.
