← Back
App #507 · 🇺🇸 the United States
Disaster score 570Legendary
IT (yes, really) built a deployment button
💀 Direct production access🏛️ Older than the department🕸️ Load bearing
Users67
Departments4
Criticality29%
Money involved€85/yr
“IT would have taken months.”— Katrin, IT (yes, really)
- Reason:
- Mainly because the process has 14 steps, 4 of which are "send an email". With a logo generated at 17:04.
- Built by:
- Katrin, an analyst
- Build time:
- a long Thursday
- Built with:
- Airtable plus four Zapier zaps
- Database:
- a private Slack channel called #data-backup
- Authentication:
- the secret is in README.md
- Deployment:
- deployed by emailing Customers_use-this-one.xlsx to Thomas
- Responsible:
- a vendor whose support contract expired 17 months ago
- Documentation:
- a Confluence page owned by Katrin, who left
- Security situation:
- TLS is disabled because it is "inside the network"
- Future disaster:
- It will trigger a call from the works council.
Accidentally connected to (6)
- → depends on a VPN connection that drops every afternoon
- → logs errors into a text file on the server
- → downloads nightly exports from an SFTP server nobody monitors
- → uses Redis as permanent storage
- → calls the production API with an admin token
- → runs only if the previous job finished before 06:00
⚠️ Removing this app may now destroy the company.
Age: 5.4 years · originally expected to last 3 weeks · 6 owners so far · survived 1 reorganisation · last meaningful change 420 days ago
Rated legendary mostly because: 6 accidental connections, 4 departments depend on it, 67 users.
Current owner
Nobody has taken responsibility for this disaster.
Claim responsibility