DemoAcme Cloud · Cosmos template

Use this template
Skip the universe

Acme Cloud

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

Major outage

Eclipse in progress

Eclipsed: 2 · In orbit: 5

Transmissions

  • · Major impact · Investigating

    API and dashboard unavailable

    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.

Core platformEclipsed (Down)

  • Eclipsed (Down)
    30 days ago90 days ago99.78% 90-day uptime190 ms avgToday
  • Eclipsed (Down)
    30 days ago90 days ago99.78% 90-day uptime334 ms avgToday
  • Auth

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

DataIn orbit (Operational)

  • Postgres primary

    In orbit (Operational)
    30 days ago90 days ago99.84% 90-day uptime41 ms avgToday
  • Backups

    In orbit (Operational)
    30 days ago90 days ago96.73% 90-day reliabilityToday

EdgeIn orbit (Operational)

  • CDN

    In orbit (Operational)
    30 days ago90 days ago99.84% 90-day uptime60 ms avgToday
  • Webhooks

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

Mission log

Nov 8, 2026

  1. Transmission API and dashboard unavailable · Investigating

    Affects API, Dashboard

    2 automatic events
    • Dashboard went down
    • API went down

Oct 16, 2026

  1. Transmission 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.