DemoAcme Cloud · Radar 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.

Sonar · 7 contacts · 1 intermittent

Intermittent contact (Partial outage)

Transmission Nightly backups running late

Partial outage
ID (code and bearing)NameStatusRange (90-day uptime)Signal (response time)
Sector 1 · Core platform
AP 020APINominal (Operational)99.84% uptime, 90 daysStrong · 190 ms
DA 060DashboardNominal (Operational)99.84% uptime, 90 daysFair · 334 ms
AU 097AuthNominal (Operational)99.84% uptime, 90 daysStrong · 157 ms
Sector 2 · Data
PP 164Postgres primaryNominal (Operational)99.84% uptime, 90 daysStrong · 41 ms
BA 219BackupsIntermittent (Degraded)96.70% reliability, 90 daysPing
Sector 3 · Edge
CD 288CDNNominal (Operational)99.84% uptime, 90 daysStrong · 60 ms
WE 320WebhooksNominal (Operational)99.80% uptime, 90 daysStrong · 273 ms
Sonar by Crontap

Transmissions

  • TX · Minor impact · Identified

    Nightly backups running late

    Affects Backups

    Latest ·

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

    All updates (2)

    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.

Contact log

Nov 8, 2026

  1. TX · Nightly backups running late · Identified

Oct 16, 2026

  1. TX · Elevated error rates · Resolved
    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.