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

Main display

Hold, hold, hold (Major outage)

2 of 7 systems no-go

Flight director: API and dashboard unavailable

Master alarm

  • APINo-go (Down)
  • DashboardNo-go (Down)

Go/no-go poll

  1. APINo-go (Down)
  2. DSHBRNo-go (Down)
  3. AUTHGo (Operational)
  4. PSTGRGo (Operational)
  5. BCKPSGo (Operational)
  6. CDNGo (Operational)
  7. WBHKSGo (Operational)

Flight director loop

  • API and dashboard unavailable

    Investigating

    Major impact · Started

    Affects API, Dashboard

    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.

Console 1 · Core platform

  • API

    Major incidentReliability 99.78%Link 190 msNo-go (Down)
    History
  • Dashboard

    Major incidentReliability 99.78%Link 334 msNo-go (Down)
    History
  • Auth

    Reliability 99.84%Link 157 msGo (Operational)
    History

Console 2 · Data

  • Postgres primary

    Reliability 99.84%Link 41 msGo (Operational)
    History
  • Backups

    Reliability 96.73%Go (Operational)
    History

Console 3 · Edge

  • CDN

    Reliability 99.84%Link 60 msGo (Operational)
    History
  • Webhooks

    Reliability 99.84%Link 273 msGo (Operational)
    History

Loop log

Nov 8, 2026

  1. FDAPI and dashboard unavailableInvestigating

    Major impact

    2 automatic events
    • · No-goDashboard went down

    • · No-goAPI went down

Oct 16, 2026

  1. FDElevated error ratesResolved

    Major impact · 50 min

    2 automatic events
    • · Back to goAPI recovered

    • · No-goAPI went down

    Transcript

    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.