{"resourceId":"register-google-cloud-london-europe-west2b-outage-plc-generator-root-cause-20261105","versions":[{"version":"external-1837bf054690069b880664ab041274060fdee8858b99039688650be523237a6c","resource":{"id":"register-google-cloud-london-europe-west2b-outage-plc-generator-root-cause-20261105","title":"The Register: Google's root cause for the Oct. 20 europe-west-2-b outage — a PLC misconfiguration kept generators from starting while one utility feed was out for repair","organization":"The Register (reporting Google Cloud's Nov. 4 service-status incident update)","sector":"Cloud infrastructure resilience","geography":"United Kingdom (London region); applicable to multi-zone design generally","publishedAt":"2026-11-05","publicationDate":"2026-11-05","eventDate":"2026-10-20","sourceName":"The Register","sourceLabel":"Independent technology journalism quoting vendor incident report","sourceUrl":"https://www.theregister.com/off-prem/2026/11/05/when-datacenters-lose-power-generators-should-kick-in-that-didnt-happen-for-google-in-london/5307739","evidenceClass":"independent-reporting","outcomeClass":"cautionary","topics":["infrastructure","operating-model"],"finding":"Source finding: per Google's Nov. 4 status update as reported, an external cable fault cut feeder A while feeder B's breaker was open for repairs after an Oct. 14 generator load test; UPS units ran about five minutes, but a voltage-sensing design flaw and PLC misconfiguration meant the generator plant never received a start signal. Google reprogrammed the PLC, says it tested electrical changes, and listed two actions: automated alert-to-communication for location-impacting incidents and expanded platform-wide testing for infrastructure-level events. Vendor claim vs reporting: the root cause and remediation are Google's own account; The Register adds context on affected organizations.","sledRelevance":"State and local agencies and universities on Google Cloud (or SaaS hosted there) need to assume a single zone can fail during maintenance windows. Paired with the UK MoJ letter in this edition, it shows both the technical cause and a public-sector operational consequence of the same incident.","evidence":"Journalism quoting Google's published incident update; affected organizations named (Lloyds, HSBC, Royal Mail, Revolut). No independent engineering verification; no duration figures beyond the UPS five-minute ride-through.","architectureImplications":"Interpretation: zone-level redundancy inside a provider can be undermined by maintenance states; critical SLED workloads should use multi-zone or multi-region deployment and test failover rather than relying on facility-level power redundancy.","governanceImplications":"Agencies can ask providers for incident post-mortems and maintenance-window risk disclosures; Google's commitment to faster automated customer communication is a vendor claim to verify in future incidents.","securityPrivacyImplications":"Availability incident; no data compromise reported.","caveats":"Secondary reporting of a vendor post-mortem; not an audit; UK facility; impacts on U.S. SLED customers were not reported.","streamIds":["google"],"roles":{"sales":"Sales framing: resilience conversations are more credible when grounded in a provider's own post-mortem. This report explains how Google's London zone lost power when a maintenance state, cable fault and PLC misconfiguration coincided. Use it to discuss multi-zone architecture and incident communications with agency CIOs, not to make comparative reliability claims. It supports a bounded resilience assessment for Google Cloud-hosted SLED workloads.","engineering":"Engineering framing: facility-level 2N power did not prevent a zone outage because the generator start logic misread a de-energized state. For SLED workloads on Google Cloud, design for zone loss: regional managed services, multi-zone instance groups, cross-region backups for critical systems, and exercised failover runbooks. Validate that SaaS suppliers hosted on Google Cloud do the same. The report gives no customer-side architecture data, so recommendations are interpretation.","delivery":"Delivery framing: the operational lesson is to test failover under realistic conditions and to wire provider status signals into the agency's incident process. Delivery teams can subscribe to Google Cloud service health feeds, map critical workloads to zones, and run game-day exercises simulating a zone loss. Ownership sits with the agency cloud operations lead. Treat Google's announced communications improvements as something to verify in the next incident."},"roleDetails":{"sales":{"customerProblem":"Agencies assume hyperscale facility redundancy prevents outages; single-zone designs remain exposed.","stakeholders":["Agency CIOs/CTOs","Cloud center of excellence leads","University research computing directors","Risk and continuity officers"],"discoveryQuestions":["Which critical workloads run in a single zone?","Do you receive Google Cloud service health alerts in your incident tooling?","When did you last test zone failover?","Do your SaaS suppliers disclose zone/region design?"],"valueHypothesis":"Interpretation: a resilience assessment could identify single-zone exposures before an incident; no savings figure is supported.","potentialEngagement":"Bounded: zone-dependency review and one failover game day for a priority Google Cloud workload.","unsupportedClaims":["That Google Cloud is less reliable than competitors","That the fixes eliminate similar failures","Any SLED-specific impact from this incident"]},"engineering":{"fit":"Directly relevant to SLED deployments on Google Cloud, including London-region academic or international workloads.","architectureIntegration":"Regional or multi-zone deployment patterns, cross-region backups, service health integration with agency incident management.","prerequisites":["Workload inventory with zone placement","Defined RTO/RPO","Access to Cloud Service Health notifications"],"constraints":["Cost of multi-region redundancy","Data residency limits","Some managed services are zonal by design"],"security":"Availability; ensure failover paths keep IAM, encryption and logging controls intact.","proofOfValue":["Simulated zone-loss test with measured recovery time","Alert-to-ticket latency measurement","Supplier attestation of multi-zone hosting"]},"delivery":{"work":"Map, harden and exercise zone-failure resilience for critical Google Cloud workloads.","dependencies":["Cloud operations team","Application owners","SaaS suppliers"],"ownership":"Agency cloud operations or platform engineering lead.","skillsAdoption":"Operations staff need game-day and incident-runbook practice specific to zone loss.","governanceCheckpoints":["Architecture review for single-zone critical workloads","Annual failover exercise","Post-incident review of provider communications"],"acceptanceCriteria":["Proposed: no tier-1 workload dependent on a single zone","Proposed: measured failover time within defined RTO","Proposed: provider service-health alerts reach on-call within minutes"],"risks":["Cost pressure leads to single-zone designs","Untested runbooks","Over-trust in vendor remediation claims"]}},"retrievedAt":"2026-11-07T22:09:27-06:00","enrichedAt":"2026-11-07T22:21:45-06:00","enrichmentBasis":"retrieved source","accessibilityWorkforceImplications":"Limited; operations staff skills for failover exercises are the main workforce implication.","procurementImplications":"Contracts and SaaS agreements can require post-mortem disclosure, zone/region redundancy and notification commitments.","operatingModelImplications":"Provider incident signals should feed agency incident management, and failover testing should be routine.","sourceVerification":{"openedUrl":"https://www.theregister.com/off-prem/2026/11/05/when-datacenters-lose-power-generators-should-kick-in-that-didnt-happen-for-google-in-london/5307739","referenceExcerpt":"PLC logic indicated that a healthy utility source was available, even though the primary and secondary distribution feeds were de-energized","promptVersion":"sled-research-v4.0","model":null,"basis":"agent-reported inspection"}}}]}