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

Cases1 case

1 to 1 of 1

  1. Symptoms

    From 02:36 UTC on 15 May 2023, Atlassian products with services hosted in the us-west-1 region could not store or retrieve data assets such as media, attachments and build artifacts. Automated monitoring detected it within three minutes, and the status page reported intermittent errors.

    Trigger

    An internal service was migrated to a new network segment as part of an initiative to harden the partitions between network segments, and the old network stack was then removed.

    Root cause
    Component
    Contributing factor
    Detection

    Automated monitoring detected the incident within three minutes.

    Remediation
    • Rolled back the network migration change, returning Atlassian systems to a known good state
    Action items
    • Review the systems that decommission service stacks and check that customer traffic is no longer served before a stack is decommissioned
    • Add steps to the service network migration process that identify associated DNS records needing attention
    Lessons

    Atlassian said the migration used blue/green deployment to limit this kind of risk, but adequate verification was not run before the old stack was decommissioned, and moving services between network segments is rare and hard to replicate in test.

Check your cluster for this

This case involves Authoritative DNS servers and records. 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