Service health

In design

Per-service status board with incident history and impacted ticket counts.

Not built yet

This page is on the roadmap. Below is what already works that covers the same job.

What you can do today

The Operations Overview shows the live service status grid (Corporate VPN, Microsoft 365, Okta SSO, RDS Production, etc.). It reads from fixtures/service_status.json today.

The voice agent uses the same data via its check_service_status tool, so callers reporting a known outage get an immediate honest answer rather than a runbook.

Target availability

After monitoring webhook ingest lands (Phase 2) so the grid is fed by reality, not a JSON file.