DemoAcme Cloud · Cyberpunk template
Use this templatecrontap.page/acme-cloud
Live status for the Acme Cloud API, dashboard and data pipeline. Updates land here first, or read the incident handbook.
ALERT // MINOR IMPACTIdentified
Started ·
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.
| State | System | Uptime | Signal | 90 days |
|---|---|---|---|---|
| Online (Operational) | API | 99.84% 90-day uptime | Average response 190 ms, fast | |
| Online (Operational) | Dashboard | 99.84% 90-day uptime | Average response 334 ms, normal | |
| Online (Operational) | Auth | 99.84% 90-day uptime | Average response 157 ms, fast |
| State | System | Uptime | Signal | 90 days |
|---|---|---|---|---|
| Online (Operational) | Postgres primary | 99.84% 90-day uptime | Average response 41 ms, fast | |
| Unstable (Degraded)Minor incident | Backups | 96.70% 90-day reliability | No latency for heartbeats |
| State | System | Uptime | Signal | 90 days |
|---|---|---|---|---|
| Online (Operational) | CDN | 99.84% 90-day uptime | Average response 60 ms, fast | |
| Online (Operational) | Webhooks | 99.80% 90-day uptime | Average response 273 ms, fast |
ALERTNightly backups running lateIdentified
ALERTElevated error ratesResolved
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.