Database upgrade
Affects Postgres primary
We are moving the primary database to a larger instance. Reads stay available; writes may queue for a few seconds.
Acme Cloud
Live status for the Acme Cloud API, dashboard and data pipeline. Updates land here first, or read the incident handbook.
Watch kept 23 days without a lost contact
| ID (code and bearing) | Name | Status | Range (90-day uptime) | Signal (response time) |
|---|---|---|---|---|
| Sector 1 · Core platform | ||||
| AP 020 | API | Nominal (Operational) | 99.84% uptime, 90 days | Strong · 190 ms |
| DA 060 | Dashboard | Nominal (Operational) | 99.84% uptime, 90 days | Fair · 334 ms |
| AU 097 | Auth | Nominal (Operational) | 99.84% uptime, 90 days | Strong · 157 ms |
| Sector 2 · Data | ||||
| PP 164 | Postgres primary | Silent (Maintenance)until | 99.84% uptime, 90 days | Strong · 41 ms |
| BA 219 | Backups | Nominal (Operational) | 96.73% reliability, 90 days | Ping |
| Sector 3 · Edge | ||||
| CD 288 | CDN | Nominal (Operational) | 99.84% uptime, 90 days | Strong · 60 ms |
| WE 320 | Webhooks | Nominal (Operational) | 99.84% uptime, 90 days | Strong · 273 ms |
| Sonar by Crontap | ||||
Transmissions
Scheduled silence
Scheduled silences ahead: 1
- – Network provider maintenance
Contact log
Nov 8, 2026
- SILENCE · Database upgrade · In progress
Oct 16, 2026
- TX · Elevated error rates · Resolved
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.