// SUBMIT_FAIL.log
Help us
document failure.
We are not here to shame anyone. Every incident in this archive — no matter how embarrassing — exists because someone made a decision under pressure, with incomplete information, in a complex system. We document these moments so that engineers, managers, and organisations can learn from them. If you know of a failure we haven’t covered, send us a note. You’ll be helping the next team avoid the same mistake.
What to include — share what you know, nothing is required except a description
- Incident titleName of the product, company, or event
- DateApproximate date or year is fine
- CategoryInfrastructure, Security, AI, Product, Startup, Privacy, Legal…
- Source URLNews article, post-mortem, or any public reference
- Affected usersRough number if known
- Estimated damageFinancial loss, fines, or market impact if documented
- What went wrongA short description in your own words
- CreditWhether we may mention your name if we feature the submission
Send a tip
Opens your default mail client with a pre-filled template.
No fail to report? You can also support the archive on Ko-fi.
// THE ARCHIVE SO FAR
171
incidents documented
$3.0T
estimated total damage
744
years of history covered
0
incidents that couldn’t have been prevented