β Back
App #795 Β· πΊπΈ the United States
Disaster score 313Common
Customer Support built an incident log nobody logs incidents in
π Direct production accessποΈ Older than the department
Users3
Departments0
Criticality32%
Money involvedβ¬7/yr
βWe'll document it after the quarter.ββ Elena, Customer Support
- Reason:
- Mainly because the documentation starts with "TODO". Presented in a town hall as "innovation".
- Built by:
- Elena, a team lead
- Build time:
- a long Thursday
- Built with:
- Svelte, which nobody else here writes
- Database:
- booleans stored as "yes", "no", "Y", "N" and occasionally "maybe"
- Authentication:
- TLS is optional because it is internal
- Deployment:
- deployed manually because CI/CD "was taking too long"
- Responsible:
- "digital transformation"
- Documentation:
- an architecture diagram with 4 arrows labelled API
- Security situation:
- the firewall rule is 0.0.0.0/0
- Future disaster:
- It will gain 510 users before anyone approves it.
Accidentally connected to (2)
- β calls the production API with an admin token
- β uses the same S3 bucket in test and production
Age: 9.0 years Β· originally expected to last 7 days Β· 5 owners so far Β· survived 2 reorganisations Β· last meaningful change 210 days ago
Rated common mostly because: alive 472x longer than intended, 2 accidental connections, direct production access.
Current owner
Nobody has taken responsibility for this disaster.
Claim responsibility