Incident Library
Applied filters FactorNo staged rolloutOrganisationSkyscannerClear 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

    On 25 August 2021, skyscanner.net was unavailable and the Skyscanner mobile apps could not work, for travellers and business partners everywhere at the same time. The full global outage lasted four and a half hours.

    Trigger

    A peer-reviewed change to a rarely changed root-level file of the cells templating configuration, intended as a no-op, that left out the {{ }} delimiters; it was submitted around 15:30 GMT, merged to master and rolled out automatically to every region at once.

    Root cause
    Component
    Contributing factor
    Remediation
    • restored the correct configuration for each cluster and let Argo CD reconcile the cluster back to it
    • restored services through the backup and restoration process
    • brought one region back first with the critical services and served all traffic from it from around 20:30 GMT
    • restored and verified the remaining regions and non-critical services over Thursday and Friday
    Action items
    • Avoid global configuration deploys, including rare change paths like this one
    • Treat templated configuration as code and add testing and linting
    • Plan and wargame more drastic failure scenarios in runbooks
    • Verify backup and restore processes, including access to the backups and the loss of a region
    • Refactor runbooks so they are clear and, where appropriate, idempotent for a stressed engineer in the early morning
    • Reconsider how much configuration is templated across regions, weighing configuration drift against automated global rollout
    Lessons

    Global configuration changes had been prevented in many cases, but not in this rarely used path. Configuration that gains templating and logic has become code and needs tests and at least linting. The failure scenarios and runbooks were not pessimistic enough, a backup only counts once it has been restored, and runbooks need care so they work for a stressed engineer at night. Automation that templates configuration across regions trades drift for the risk of rolling one mistake out everywhere. An experienced incident commander who kept the response calm and blameless made a large difference.

Check your cluster for this

This case involves Argo CD and Configuration templating. 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