Incident 2026-03-14: orders API outage
Three hours of syslog from web-1, web-2, db-1 and backup-1, with the investigation on top: the cause, the outage and what the on-call engineer did. A made-up incident for the logs video.
2,297 moments · 2026-03-14T01:30:00Z CE – 2026-03-14T04:29:57.914461Z CE · by @athan · @athan
Moments
- GET /api/orders 200 89ms
- GET /api/orders 200 51ms
- GET /api/orders 200 68ms
- GET /api/orders 200 80ms
- GET /api/orders 200 61ms
- checkpoint complete
- GET /api/orders 200 77ms
- GET /api/orders 200 86ms
- GET /api/orders 200 94ms
- Accepted publickey for deploy
- GET /api/orders 200 99ms
- GET /api/orders 200 35ms
- GET /api/orders 200 62ms
- GET /api/orders 200 73ms
- GET /api/orders 200 30ms
- GET /api/orders 200 66ms
- GET /api/orders 200 72ms
- GET /api/orders 200 83ms
- GET /api/orders 200 65ms
- GET /api/orders 200 28ms
- Accepted publickey for deploy
- GET /api/orders 200 54ms
- GET /api/orders 200 28ms
- GET /api/orders 200 57ms
- GET /api/orders 200 46ms
- GET /api/orders 200 50ms
- GET /api/orders 200 72ms
- GET /api/orders 200 88ms
- GET /api/orders 200 35ms
- GET /api/orders 200 45ms
- GET /api/orders 200 35ms
- GET /api/orders 200 22ms
- GET /api/orders 200 59ms
- GET /api/orders 200 68ms
- GET /api/orders 200 27ms
- GET /api/orders 200 26ms
- GET /api/orders 200 59ms
- GET /api/orders 200 42ms
- GET /api/orders 200 95ms
- checkpoint complete
- GET /api/orders 200 71ms
- Accepted publickey for deploy
- GET /api/orders 200 46ms
- GET /api/orders 200 71ms
- GET /api/orders 200 44ms
- GET /api/orders 200 63ms
- GET /api/orders 200 68ms
- GET /api/orders 200 91ms
- GET /api/orders 200 55ms
- GET /api/orders 200 76ms