Incident Library
Applied filters Root causeConfiguration changeSymptomHigh latencyFactorHarmful manual actionClear 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

Cases2 cases

1 to 2 of 2

  1. IL-0561 DigitalOcean's Cloud Control Panel and Public API returned up to 25% errors in two windows as authorization timed out
    DigitalOcean2026
    Symptoms

    From 16:56 UTC on 24 August 2026, requests to DigitalOcean's Cloud Control Panel, Public API and the product management systems that depend on them failed at elevated rates. Automated monitoring flagged abnormal error rates and latency at 16:58. Running Droplets, network routing and block storage Volumes kept working.

    High error rateHigh latency
    Trigger

    A planned migration of the database layer behind DigitalOcean's identity, authentication and authorization services made one critical authorization query run much slower than its historical baseline.

    Root cause
    Configuration change
    Component
    DatabaseIdentity and access service
    Contributing factor
    Retry stormHarmful manual action
    Detection

    Automated monitoring detected abnormal error rates and latency at 16:58 UTC, two minutes after the authorization query slowed down.

    Remediation
    • Rerouted authorization traffic onto a single healthy processing path
    • Temporarily disabled hedged retries for the primary callers
    • Disabled the retry and amplification behaviour across the remaining affected services
    • Added read capacity for the slow authorization query
    Action items
    • Deploy circuit breakers in upstream services that detect a degraded downstream dependency and suppress hedged requests and retries
    • Audit the architecture so retry suppression and circuit breaking are enforced the same way in every control plane service
    • Add fast-fail load shedding so request queues do not saturate while a dependency is slow
    • Add telemetry alerts that spot queues backing up before customers are affected
    • Let critical authorization components run in a degraded mode on asynchronous, eventually consistent database replicas when the primary database is slow
    View case
  2. IL-0225 An IGP purge command made every Microsoft WAN router recompute routes, causing global latency, timeouts and packet loss
    Microsoft Azure2023
    Symptoms

    From 07:08 UTC on 25 January 2023, customers saw long network latency and timeouts when connecting to resources in Azure regions and to other Microsoft services such as Microsoft 365 and Power Platform. Microsoft's monitoring detected DNS and WAN issues from 07:11 UTC.

    High latencyIntermittent timeoutsIntermittent connection failuresPacket lossNetwork unreachable
    Trigger

    A network engineer adding capacity to the global WAN in Madrid ran a step of a recently changed standard operating procedure that purged the IGP database; on the router manufacturer involved, that command runs on all IGP-joined routers instead of only the local one.

    Root cause
    Configuration change
    Component
    Backbone network (WAN)Interior routing (IGP)BGP routing
    Contributing factor
    No configuration testsUnverified assumptionExcessive blast radiusHarmful manual action
    Detection

    Monitoring detected DNS and WAN issues from 07:11 UTC and alerted the on-call engineers within 5 minutes of the command being run. The team reviewed all recent changes and identified the command by 08:20 UTC. The engineer making the change was not informed of the alerts because of the unqualified changes to the SOP.

    Remediation
    • Restarted by hand the paused WAN health and traffic engineering systems, which ended the remaining packet loss
    Action items
    • Audit and block similar widespread-impact commands across all three vendors for all WAN router roles
    • Give on-call engineers real-time visibility of approved and unqualified activity on network devices
    • Run regular mandatory operational training and attestation of following all SOPs
    • Have the Change Advisory Board review all SOPs still pending qualification within 30 days
    View case
Check your cluster for this

These 2 cases involve Backbone network (WAN) and BGP routing. 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.

Open kubegap

By root cause1

Configuration change2 cases

Component
Backbone network (WAN)1BGP routing1Database1Identity and access service1Interior routing (IGP)1
Contributing factor
Harmful manual action2Unverified assumption1Excessive blast radius1No configuration tests1Retry storm1
Organisation
DigitalOcean1Microsoft Azure1
  1. IL-0561 DigitalOcean's Cloud Control Panel and Public API returned up to 25% errors in two windows as authorization timed out
    DigitalOcean2026
  2. IL-0225 An IGP purge command made every Microsoft WAN router recompute routes, causing global latency, timeouts and packet loss
    Microsoft Azure2023