DemoAcme Cloud · Departures Board template

Use this template

Acme Cloud

Live status for the Acme Cloud API, dashboard and data pipeline. Updates land here first, or read the incident handbook.

Departures

Some flights delayed (Partial outage)

Announcement
Nightly backups running late · The backup is running again and should finish within the hour.
Terminal 1 · Core platform
TimeFlightDestinationGate (90-day uptime %)Remarks
19:05, fast responseFlight CP 467API19:05 · CP 467 · 99.899.8% 90-day uptimeOn time (Operational)
19:05, normal responseFlight CP 555Dashboard19:05 · CP 555 · 99.899.8% 90-day uptimeOn time (Operational)
19:05, fast responseFlight CP 542Auth19:05 · CP 542 · 99.899.8% 90-day uptimeOn time (Operational)
On-time performance · 90 days
  • API
  • Dashboard
  • Auth
Terminal 2 · Data
TimeFlightDestinationGate (90-day uptime %)Remarks
19:05, fast responseFlight DA 819Postgres primary19:05 · DA 819 · 99.899.8% 90-day uptimeOn time (Operational)
19:05Flight DA 794Backups19:05 · DA 794 · 96.796.7% 90-day reliabilityDelayed (Degraded)
On-time performance · 90 days
  • Postgres primary
  • Backups
Terminal 3 · Edge
TimeFlightDestinationGate (90-day uptime %)Remarks
19:05, fast responseFlight ED 919CDN19:05 · ED 919 · 99.899.8% 90-day uptimeOn time (Operational)
19:05, fast responseFlight ED 365Webhooks19:05 · ED 365 · 99.899.8% 90-day uptimeOn time (Operational)
Flight operated by Crontap
On-time performance · 90 days
  • CDN
  • Webhooks

Announcements

  • Nightly backups running late

    Identified

    Minor impact · Started ·

    Affects Backups

    Last night's backup has not checked in yet. Data is safe; we are looking into the storage queue.

    1. The backup is running again and should finish within the hour.

    2. A stuck storage queue worker held the job. We restarted it.

Flight log

Nov 8, 2026

  1. NOTICENightly backups running lateIdentified

Oct 16, 2026

  1. NOTICEElevated error ratesResolved
    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.

    1. Error rates are back to normal. This incident is resolved.

    2. We found a faulty deploy and are rolling it back.