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

Gallery notice

Some exhibits have limited viewing (Partial outage)

  • 7 exhibits in 3 rooms
  • 99.83% uptime over 90 days
  • Limited viewing: 1

Curator's notes

  • Curator's note · Identified

    Nightly backups running late

    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.

Room 1 · Core platform

  • API

    HTTP monitor

    On view 90+ days

    Provenance

    99.84% uptime, last 90 days

    Average response 190 ms

    On view (Operational)

  • Dashboard

    HTTP monitor

    On view 90+ days

    Provenance

    99.84% uptime, last 90 days

    Average response 334 ms

    On view (Operational)

  • Auth

    HTTP monitor

    On view 90+ days

    Provenance

    99.84% uptime, last 90 days

    Average response 157 ms

    On view (Operational)

Room 2 · Data

  • Postgres primary

    HTTP monitor

    On view 90+ days

    Provenance

    99.84% uptime, last 90 days

    Average response 41 ms

    On view (Operational)

  • Heartbeat

    On view 90+ days

    Provenance

    96.70% of check-ins received, last 90 days

    Last check-in

    Limited viewing (Degraded)

Room 3 · Edge

  • CDN

    HTTP monitor

    On view 90+ days

    Provenance

    99.84% uptime, last 90 days

    Average response 60 ms

    On view (Operational)

  • Webhooks

    HTTP monitor

    On view 90+ days

    Provenance

    99.80% uptime, last 90 days

    Average response 273 ms

    On view (Operational)

Acquisitions log

Nov 8, 2026

  1. Nightly backups running late

    Affects Backups

Oct 16, 2026

  1. Elevated error rates

    Affects API

    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.