DemoAcme Cloud · Isometric City template

Use this template
Skip the city

Acme Cloud

Live status for the Acme Cloud API, dashboard and data pipeline. Updates land here first, or read the incident handbook.

Major outage

Blackout

Blacked out: 2 · Lights on: 5

Powered by Crontap

City bulletin

  • Public noticeInvestigating

    API and dashboard unavailable

    Since · Major impact

    Affects API, Dashboard

    Latest update ·

    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.

Core platformBlacked out (Down)

  • API

    Major incident
    Blacked out (Down)
    30 days ago90 days ago99.78% 90-day uptime190 ms avgToday

  • Dashboard

    Major incident
    Blacked out (Down)
    30 days ago90 days ago99.78% 90-day uptime334 ms avgToday

  • Auth

    Lights on (Operational)
    30 days ago90 days ago99.84% 90-day uptime157 ms avgToday

DataLights on (Operational)

  • Postgres primary

    Lights on (Operational)
    30 days ago90 days ago99.84% 90-day uptime41 ms avgToday

  • Backups

    Lights on (Operational)
    30 days ago90 days ago96.73% 90-day reliabilityToday

EdgeLights on (Operational)

  • CDN

    Lights on (Operational)
    30 days ago90 days ago99.84% 90-day uptime60 ms avgToday

  • Webhooks

    Lights on (Operational)
    30 days ago90 days ago99.84% 90-day uptime273 ms avgToday

City log

Nov 8, 2026

  1. Notice API and dashboard unavailable · Investigating

    Affects API, Dashboard

    2 automatic events
    • Dashboard went down
    • API went down

Oct 16, 2026

  1. Notice Elevated error rates · Resolved

    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.