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

Flatline: resuscitating

Major outage

HR

69

live median bpm

2 flatlined

90-day uptime
99.82%
Down
2

Alarms

  • API and dashboard unavailable

    Investigating

    Major impact · Started ·

    Affects API, Dashboard

    Latest ·

    We are rolling back a load balancer change made at the start of the outage.

    All updates (2)

    Requests to the API and dashboard are failing. We are investigating and will post an update within 30 minutes.

    1. We are rolling back a load balancer change made at the start of the outage.

    2. Every region is affected. Background jobs are paused to protect data.

Bay 1 · Core platform

3 ch

  • API

    Flatline· DownMajor incident
    HR
    --bpm
    Uptime (90 days)
    99.78%190 ms

  • Dashboard

    Flatline· DownMajor incident
    HR
    --bpm
    Uptime (90 days)
    99.78%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

    Stable· Operational
    HR
    60bpm
    Uptime (90 days)
    96.73%

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.84%273 ms
Monitored around the clock by Crontap

Chart notes

Nov 8, 2026

  1. ALARM· API and dashboard unavailable· Investigating

    2 automatic events
    • Dashboard went down
    • API went down

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.