A Google Cloud outage caused by a power event disrupted online banking and web services in Britain and parts of Europe on Tuesday. The fault hit the europe-west2 region based in London, leaving millions of mobile banking users unable to open balances or complete electronic payments during the morning rush. Google Cloud confirmed the system failure began late Monday evening Pacific time, prompting quick fixes before repair teams stabilized operations [3].
How the Google Cloud Outage Began
The trouble began just after 2:00 a.m. Eastern, or 6:08 a.m. GMT, on Tuesday, October 20, as reported by Andrew Zinin for Tech Xplore. DownDetector recorded a sharp jump in trouble tickets within minutes as morning traffic climbed. Most user complaints came from London account holders trying to access daily digital banking tools [1].
Google Cloud engineers spotted the problem on their status page, recording that multiple services in the europe-west2 region were suffering degraded response times and high error rates. The platform displayed orange alert flags as technical teams traced the fault to a power event that felled London servers in its main zone. While trouble tickets fell briefly after sunrise, customer reports surged again as British workers opened software tied to the facility. The disruption spread beyond Britain because dozens of international apps rely on London hardware to handle login requests and process payments, showing how closely modern digital tools link to shared remote facilities [3].
Reporting on the failure, tech writer Carly Page explained that Google Cloud pinned the root cause of the breakdown on a power event inside its British network. The company stated that only a small proportion of overall clients suffered direct downtime. The morning disruption linked to the Google Cloud outage caused inconvenience because London acts as a primary European computing hub for retail companies and digital banks alike [2].
Disruptions Across UK Banking Apps
British financial institutions felt the brunt of the downtime. Mobile apps for Lloyds Bank, Halifax, HSBC, and digital lender Revolut failed to load during the morning commute. Frustrated depositors in London and across the U.K. could not send money or check balances [1].
Digital banking provider Revolut moved quickly to reassure worried users about the safety of their accounts after thousands of customers reported locked apps and failed card transfers. “We can confirm that all our customers’ money and data are safe,” a Revolut spokesperson said in an email sent during the disruption, adding that engineers had worked to fix the issue since early morning. The company apologized for the downtime while confirming that the breakdown affected several user services at the same time. The reassurance helped calm fears of a cybersecurity breach, but depositors still faced hours of delays before transaction queues cleared and login portals accepted standard credentials [1].
Lloyds Bank reported later in the day that its mobile app had returned to service. “We understand the root issues have been resolved, so we expect all our services to be back to normal soon,” a Lloyds spokesperson said in an email [1]. The disruption also affected non-banking platforms, including property portal Rightmove and parcel courier DpD, which share the same Google infrastructure in London [3].
Affected Services in the London Zone
Google logs pinpointed the failure to a single availability zone designated as europe-west2-b. That facility houses major data storage and processing engines for European clients. Multiple backend products went dark at once, cutting off data pipelines for businesses that depend on fast server responses [3].
The failure disabled several flagship enterprise products that power large databases and analytics pipelines. Impacted tools included data warehouse service BigQuery, application hosting environment App Engine, business intelligence tool Looker, and Google Cloud SQL databases. Google advised affected clients that they could attempt to shift workloads to another available zone or region if their software permitted manual redirection. Yet many setups cannot switch server locations on short notice because their data stores remain tied to specific local network configurations (a common safeguard for regional data compliance). Consequently, businesses had to wait until Google technicians restored the core zone [3].
During the Google Cloud outage, secondary apps in other European countries suffered network timeouts because many firms choose to host their main data clusters inside London to lower network latency for British consumers. When the power event tripped systems in europe-west2-b, those dependent services experienced delayed responses. Google kept its status page updated every two hours while engineering crews worked on physical electrical hardware inside the London facility [3].
Google Cloud Outage Recovery Timeline
Engineers contained the power problem after several hours of emergency maintenance. Google updated its status advisory to confirm that the electrical event was mitigated and that server recovery was underway. The company said infrastructure services would show partial improvement within 30 minutes [3].
Systems returned in stages as technicians safely brought individual server racks back online without triggering secondary electrical surges. Google Cloud projected that full recovery of existing workloads would wrap up tentatively by 06:00 PDT on Tuesday, which aligned with 1300 UTC according to timeline estimates published by Carly Page [2]. Banking apps and corporate websites began seeing normal latency figures by midday in London, allowing backlogged financial requests to settle. Google said that its staff would keep monitoring system logs until error rates dropped back to baseline levels in all European zones, giving administrators confidence that connections had stabilized [1].
By Tuesday afternoon, Google confirmed that operations had largely recovered. “The issue with impacted GCP products has been mitigated for most of the customers and it is believed to be affecting currently a very small number of customers and our Engineering Team is working on it,” the status update said [3]. Google added that it will conduct a full internal investigation and publish an incident report [1].
Cloud Infrastructure and Redundancy Risks
The sudden breakdown showed the hidden risks of centralizing digital services on a single provider. When cloud facilities fail, consumer services grind to a halt without warning. Cybersecurity researchers warned that businesses must review how their systems respond when a primary vendor suffers a sudden power interruption [3].
Industry specialists noted that the incident revealed an uncomfortable truth about digital banking dependencies. “When a cloud outage leaves people unable to make payments or access everyday services, it exposes how much we depend on infrastructure we never see,” said Marijus Briedis, Chief Technology Officer at NordVPN. Briedis pointed out that while banks and delivery companies seem independent, many rely on the same technology providers behind the scenes. Dr. Pete Membrey, Chief Research Officer at ExpressVPN, added that users should not assume outages stem from cyberattacks: “Most outages like this turn out to be technical faults rather than anything malicious” [3].
The London Google Cloud outage shows that even top technology giants face physical vulnerabilities like power grid disruptions. This incident follows other service updates within Google platforms this season, such as when Google set a December sunset for its Pixel Watch Safety Signal service. Financial regulators in Britain are now reviewing the disruption, while enterprise architects examine whether their backup plans can truly maintain uptime when a single data zone goes dark [1].
- ONLINE NEWS Zinin, A. (2026, October 20). Google Cloud outage hits UK banks. Tech Xplore. [Article Link]
- ONLINE NEWS Page, C. (2026, October 20). Google Cloud says a ‘power event’ caused today’s outage. The Register. [Article Link]
- ONLINE NEWS Moore, M. (2026, October 20). Google Cloud went down after ‘power event’ causes major outage across Europe. TechRadar. [Article Link]
