Documented incidentIncident 2022-04-05AtlassianEngineering postmortem

Deletion script given site IDs instead of app IDs removes 775 customers' sites (Atlassian, 2022)

A script meant to retire a deprecated app was given IDs for entire customer sites and did not check whether an ID referred to the app or the whole site.

What happened

  • It deleted 883 sites belonging to 775 customers within about 23 minutes; restoration took up to 14 days for a subset of customers.Post-Incident Review: April 2022 Atlassian outage

The failure pattern

Watch the pattern: Destructive operation without verified recovery

Safeguards that address it

CollectSEA's engineering analysis of what would have prevented or contained this failure.

  • Validate the scope of every ID in destructive scriptsCheck whether an ID refers to an app or an entire site and require a dry-run and review before deleting.
  • Soft-delete and rehearse large-scale restoreDelay permanent deletion and practise restoring many customers at once.

Related standards

CollectSEA's mapping through this incident's failure pattern; not an official determination by the standards bodies.

Building something similar?

Describe your design and see every precedent that applies, with safeguards you can hand to your coding agent.

Analyze your design
Security advisory2026-06-18

Security issue reported in Enterprise

Splunk Enterprise contains a missing authentication for critical function vulnerability which could allow an unauthenticated user to create or truncate arbitrary files through a PostgreSQL sidecar service endpoint.

Destructive operation without verified recoveryadvisory.splunk.com