Database upgrade
In progressScheduled to
Affects Postgres primary
We are moving the primary database to a larger instance. Reads stay available; writes may queue for a few seconds.
DemoAcme Cloud · Retro Desktop template
Use this templateLive status for the Acme Cloud API, dashboard and data pipeline. Updates land here first, or read the incident handbook.
Scheduled tasks pending: 1
Defragmenting: Postgres primary
Estimated time remaining: until
| Program | Status | History (90 days) | Uptime (90 days) | CPU (response time) | Trend |
|---|---|---|---|---|---|
| Core platform | |||||
| API | Responding (Operational) | 99.84%, response 190 ms | 190 ms (fast) | steady | |
| Dashboard | Responding (Operational) | 99.84%, response 334 ms | 334 ms (ok) | steady | |
| Auth | Responding (Operational) | 99.84%, response 157 ms | 157 ms (fast) | steady | |
| Data | |||||
| Postgres primary | Defragmenting (Maintenance) | 99.84%, response 41 ms | 41 ms (fast) | steady | |
| Backups | Responding (Operational) | 96.73% reliability | — | steady | |
| Edge | |||||
| CDN | Responding (Operational) | 99.84%, response 60 ms | 60 ms (fast) | steady | |
| Webhooks | Responding (Operational) | 99.84%, response 273 ms | 273 ms (fast) | steady | |
| Level | Time | Source | Event |
|---|---|---|---|
| Maintenance | Scheduled works | Database upgrade [In progress] | |
| Incident | Status page | Elevated error rates [Resolved · 50 min]2 automatic events
DetailsA bad deploy raised error rates for about 45 minutes. We rolled it back and added a canary stage.
|