Web, Payments, Bytes & Ventures

WPBV Radio

Tune into tech and money.

Atlassian outage, 5 April 2022

The Atlassian outage of 5 April 2022: what failed, why, and what Atlassian changed, from its own incident report.

Provider
Atlassian
Date
Cause
Other
Regions
Global (775 customers / 883 sites)

Atlassian cloud site deletion outage (775 customers) (5 April 2022).

What happened. While deleting a legacy app (‘Insight - Asset Management’), a team was given the IDs of entire cloud sites instead of app IDs, and the deletion API accepted either without warning. A script run on April 5 immediately deleted 883 sites belonging to 775 customers, some of which took up to 14 days to restore.

What changes. Atlassian committed to universal ‘soft deletes’ across all systems and to accelerate its disaster recovery program to automate multi-site restoration.

Questions

What caused the Atlassian outage in April 2022?

While deleting a legacy app (‘Insight - Asset Management’), a team was given the IDs of entire cloud sites instead of app IDs, and the deletion API accepted either without warning.

Which services were affected?

Atlassian cloud products (Jira, Confluence and others) for affected sites.

Read how shared dependencies spread a failure in why one cloud outage can break unrelated apps, or browse the outage archive.

Started (UTC)
2022-04-05 07:38 UTC
Services affected
Atlassian cloud products (Jira, Confluence and others) for affected sites
Incident report
atlassian.com
Sources
SourceLink
Atlassian incident reporthttps://www.atlassian.com/engineering/post-incident-review-april-2022-outage
WPBV Radio

What are you looking for?

Search by headline, topic or keyword.