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

Monitor · 7 channels

Irregular rhythm detected

Partial outage

HR

71

median bpm

90-day uptime
99.83%
Degraded
1

Alarms

  • Nightly backups running late

    Identified

    Minor impact · Started ·

    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.

Bay 1 · Core platform

3 ch

  • API

    Stable· Operational
    HR
    75bpm
    Uptime (90 days)
    99.84%190 ms

  • Dashboard

    Stable· Operational
    HR
    90bpm
    Uptime (90 days)
    99.84%334 ms

  • Auth

    Stable· Operational
    HR
    69bpm
    Uptime (90 days)
    99.84%157 ms

Bay 2 · Data

2 ch

  • Postgres primary

    Stable· Operational
    HR
    69bpm
    Uptime (90 days)
    99.84%41 ms

  • Backups

    Irregular· DegradedMinor incident
    HR
    60bpm
    Uptime (90 days)
    96.70%

Bay 3 · Edge

2 ch

  • CDN

    Stable· Operational
    HR
    73bpm
    Uptime (90 days)
    99.84%60 ms

  • Webhooks

    Stable· Operational
    HR
    71bpm
    Uptime (90 days)
    99.80%273 ms
Monitored around the clock by Crontap

Chart notes

Nov 8, 2026

  1. ALARM· Nightly backups running late· Identified

Oct 16, 2026

  1. ALARM· Elevated error rates· Resolved · 50 min

    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.