Planned works
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.
DemoAcme Cloud · Transit Map template
Use this templateLive status for the Acme Cloud API, dashboard and data pipeline. Updates land here first, or read the incident handbook.
| Line or station | Status | Reliability |
|---|---|---|
| Core platform | Running normally (Operational) | 99.84% average reliability, 90 days |
| API | Running normally (Operational) | 99.84% uptime, 90 days |
| Dashboard | Running normally (Operational) | 99.84% uptime, 90 days |
| Auth | Running normally (Operational) | 99.84% uptime, 90 days |
90-day history, Core platform
| ||
| Data | Planned works (Maintenance) | 98.29% average reliability, 90 days |
| Postgres primary | Planned works (Maintenance)until | 99.84% uptime, 90 days |
| Backups | Running normally (Operational) | 96.73% reliability, 90 days |
90-day history, Data
| ||
| Edge | Running normally (Operational) | 99.84% average reliability, 90 days |
| CDN | Running normally (Operational) | 99.84% uptime, 90 days |
| Webhooks | Running normally (Operational) | 99.84% uptime, 90 days |
90-day history, Edge
| ||
| 23 days running normallyNetwork operated by Crontap | ||
Planned works
Affects Postgres primary
We are moving the primary database to a larger instance. Reads stay available; writes may queue for a few seconds.
Planned works ahead: 1
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.