Affects Backups
Last night's backup has not checked in yet. Data is safe; we are looking into the storage queue.
The backup is running again and should finish within the hour.
A stuck storage queue worker held the job. We restarted it.
Acme Cloud
Live status for the Acme Cloud API, dashboard and data pipeline. Updates land here first, or read the incident handbook.
| 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 | Responding (Operational) | 99.84%, response 41 ms | 41 ms (fast) | steady | |
| Backups | Not responding (Degraded)Minor incident | 96.70% reliability | — | steady | |
| Edge | |||||
| CDN | Responding (Operational) | 99.84%, response 60 ms | 60 ms (fast) | steady | |
| Webhooks | Responding (Operational) | 99.80%, response 273 ms | 273 ms (fast) | worsening | |
| Level | Time | Source | Event |
|---|---|---|---|
| Incident | Status page | Nightly backups running late [Identified] | |
| 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.
|