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.

Installation in progress

Gallery being rehung (Scheduled maintenance)

  • 7 exhibits in 3 rooms
  • 99.84% uptime over 90 days
  • Being rehung: 1

On view without interruption for 23 days

Rehang scheduled, next on

  • Network provider maintenance to

Curator's notes

  • Maintenance · In progress

    Database upgrade

    Scheduled to

    Affects Postgres primary

    We are moving the primary database to a larger instance. Reads stay available; writes may queue for a few seconds.

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

    Being rehung (Maintenance)

  • Backups

    Heartbeat

    On view 90+ days

    Provenance

    96.73% of check-ins received, last 90 days

    Last check-in

    On view (Operational)

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.84% uptime, last 90 days

    Average response 273 ms

    On view (Operational)

Acquisitions log

Nov 8, 2026

  1. Database upgrade

    Affects Postgres primary

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.