Context
For a platform serving thousands of users and partners, there is no public status page communicating
uptime, incidents, and maintenance windows.
Scope
- Status page fed by health/SLO checks (API, RPC, indexer, contracts).
- Incident lifecycle (investigating → identified → resolved) + subscribe for updates.
- Scheduled-maintenance notices.
Acceptance criteria
- Real-time component status is public; incidents and maintenance are communicated to subscribers.
Verification
- A simulated dependency outage flips the relevant component to degraded on the status page.
Context
For a platform serving thousands of users and partners, there is no public status page communicating
uptime, incidents, and maintenance windows.
Scope
Acceptance criteria
Verification