Pause screenIn progress
Database upgrade
We are moving the primary database to a larger instance. Reads stay available; writes may queue for a few seconds.
Lives: 6 of 7 services up
Longest run: 66 days
Current run: 23 days
Paused for scheduled maintenance
Next pause, scheduled works: 1
- – Network provider maintenance
Boss fights
High score
| Rank | Player | Score | Best | Spd (response time) | Acc (90-day uptime) | Status |
|---|---|---|---|---|---|---|
| Stage 1 · Core platform | ||||||
| 1ST | Auth | 60 days, steady | 60 days | 157 ms | 99.8% | Alive (Operational) |
| 2ND | Dashboard | 41 days, steady | 41 days | 334 ms | 99.8% | Alive (Operational) |
| 3RD | API | 23 days, steady | 34 days | 190 ms | 99.8% | Alive (Operational) |
| Stage 2 · Data | ||||||
| 1ST | Backups | 59 days, steady | 59 days | -- | 96.7% | Alive (Operational) |
| 2ND | Postgres primary | 41 days, steady | 41 days | 41 ms | 99.8% | Paused (Maintenance) |
| Stage 3 · Edge | ||||||
| 1ST | Webhooks | 48 days, steady | 48 days | 273 ms | 99.8% | Alive (Operational) |
| 2ND | CDN | 43 days, steady | 43 days | 60 ms | 99.8% | Alive (Operational) |
| CTP9999Cabinet by Crontap | ||||||
Replay
Nov 8, 2026
Oct 16, 2026
- BOSSElevated error ratesResolved
2 automatic events
- API recovered
- API went down
Details
A bad deploy raised error rates for about 45 minutes. We rolled it back and added a canary stage.
Error rates are back to normal. This incident is resolved.
We found a faulty deploy and are rolling it back.