Incident Library
Applied filters FactorUnpatched known bugOrganisationGoogle CloudClear allEvery case under the filters, with no sentence; newest first.
Suggested filters Search, and the values found in your words appear here.

Graph

  • Root cause
  • Component
  • Symptom
  • Contributing factor
  • Case

Cases1 case

1 to 1 of 1

  1. Symptoms

    From 09:35 to 10:08 PT on 16 November 2021, most endpoints served by Google's global External Proxy Load Balancing (GCLB) returned Google 404 errors to HTTP/S requests. For about another 1 hour and 20 minutes customers could not change their load balancing configuration.

    Trigger

    On 16 November 2021 a race condition in the configuration pipeline occurred in a cluster that patch A had not yet reached, and pushed a corrupted configuration file to GCLB.

    Root cause
    Component
    Contributing factor
    Detection

    Automated alerting notified Google engineers at 09:50 PT, at the same time as customer support requests came in.

    Remediation
    • Rolled back to the last known good configuration, which ended the 404 errors
    • Suspended customer-initiated configuration changes in GCLB
    • Validated the fix and added proctoring and monitoring before resuming changes
    • Resumed customer configuration pushes at 11:28 PT
    Action items
    • Add alerting that reports similar issues much faster
    • Add stronger automated correctness checks on configurations before they are applied
    • Speed up planned architectural changes that improve how such issues are isolated and resolved
Check your cluster for this

This case involves Cloud load balancer and Serverless function platform. kubegap audits a Kubernetes cluster for gaps like these, read-only, from Claude Code or Codex; its checks cite public reports like the ones in this library.

By root cause1