Did you know? · No. 26 · Fun fact ·
An Atlassian deletion error left some customers offline for up to 14 days

On April 5, 2022, an Atlassian script meant to remove a legacy app received whole-site IDs instead. It immediately deleted 883 sites belonging to 775 customers. The first customers were restored on April 8, and all sites were progressively restored by April 18. Atlassian said no customer lost more than five minutes of data.
For a smaller website, the lesson is not to fear automation. It is to build guardrails around it. Deletions should be reversible, bulk jobs should validate the type and scope of every ID, and recovery should be practiced before a real emergency. A backup is only useful if you can restore it reliably at the scale you need.
Try this on your site
This week, change destructive deletes to a soft-delete or trash step wherever possible. Test restoring a sample site or database backup, and have a second person check the target list before any bulk script runs.
Share this fact
Each fact is checked against the primary sources listed. Spotted an error? Email the Status Is UP team. Status Is UP helps owners improve their sites; it is not an uptime monitor. For live outage status, see Status Is Down.