A power event in Google Cloud’s europe-west2-b zone disrupted multiple services in its London region on 20 October, with Google’s status page describing elevated errors, intermittent network failures and unavailable services before saying the event was mitigated and workloads were recovering. CX Today reported that affected services included banking apps and websites; Euronews said the FCA was in touch with Google and affected firms. Revolut reported interruptions to payments and other app functions during the disruption; readers can see our related coverage of Revolut’s Gibraltar approval.Google identifies europe-west2 as its London region, comprising multiple zones. Its incident notice says the event began at 23:08 Pacific time on 19 October and affected zone europe-west2-b; it initially warned that customers might not be able to create new workloads while existing ones recovered. The company later said engineering had restored full availability. Google described an infrastructure and power event, not a cyberattack; its public account does not yet provide a final root-cause analysis.
Cloud Growth Is the Investor Context
In its Q2 2026 results, Alphabet reported Google Cloud revenue of $24.8 billion, up 82% year over year, with operating income of $8.8 billion. Cloud is now a sizeable growth engine, not a peripheral hosting business: investors are assessing whether the AI infrastructure boom can sustain revenue growth and improve margins as Alphabet expands capacity. The outage puts reliability alongside compute, storage and AI services in Alphabet’s enterprise sales proposition.The incident is also a reminder that regional architecture determines whether a local failure stays local. Google’s London region has multiple zones, but affected customers experienced problems across a range of services after a single-zone power event. A final technical report will help explain the dependency chain and how the disruption crossed service boundaries. Dr Amro Al-Said Ahmad, a computer science lecturer at Keele University, told The Register that resilience requires multi-region deployments, workload portability and tested recovery. The investor question is whether customers can build that resilience, and at what cost in duplicated capacity, data movement and engineering.
Credits Are Not the Same as Lost Revenue
Google Cloud’s service-level agreements generally measure uptime over a billing month, define eligible downtime service by service, and offer credits against future bills when thresholds are missed. Under the current Compute Engine SLA, qualifying customers must request credits and meet documentation requirements; credits are capped and are not cash compensation for customer losses. Terms vary by product and deployment configuration, so a multi-hour incident does not translate mechanically into a fixed percentage of Google’s quarterly revenue.More consequential costs are harder to quantify: incident response, remediation, customer concessions, possible churn, and the expense customers incur to test or rebuild resilience. Alphabet does not disclose a standalone outage charge in advance, and there is no basis to estimate one from public facts. The post-incident report and any customer disclosures will be more revealing than a speculative credit calculation.
Regulation Adds a Second Test
The UK’s critical third-party regime is newly operational. From 13 July 2026, the Treasury-designated providers, including Google Cloud EMEA Limited, came under direct oversight by the Bank of England, Prudential Regulation Authority and FCA. The regulators can set resilience requirements, request information, conduct testing and require remediation for services deemed critical to financial firms. This complements, rather than replaces, each bank’s responsibility to manage outsourcing and operational resilience.The FCA’s statement that it was engaging Google and affected firms makes this incident an early test of the regime’s information-gathering function. It does mean the incident can feed into supervisory questions about concentration, recovery time, customer communications and firms’ exit or contingency plans. The Bank of England’s critical-third-party framework is designed to address systemic dependencies that individual customer contracts cannot fully capture.
What Google Stock Investors May Watch on 28 October
Alphabet’s investor relations announcement lists its Q3 results for 28 October. Management may be asked about customer response, reliability investment and effects on demand or infrastructure costs. Investors will also compare Cloud’s growth and margins with the unusually strong Q2 baseline.For Google stock, this is a risk signal rather than a standalone earnings forecast. If customers remain confident and the technical explanation shows a contained failure with credible remediation, the dominant story may remain growth. If the review reveals a broader dependency or if supervisory scrutiny points to costly changes, reliability could become part of the margin and retention debate. Investors need evidence on recovery and prevention, not only outage duration.