A status page is only as honest as the checks behind it. Ours runs periodic checks against every monitored service and records each result, so the public page is always a projection of real data.
Checks and state
- ▸Each service is probed on an interval configured per service
- ▸Results are stored, not just displayed — history survives restarts
- ▸A maintenance flag pauses alerts during planned work
The public API
The status page exposes a public API and a badge endpoint. Any website or README can embed a live status badge without an API key. The data is deliberately public — hiding problems helps nobody.
Why it matters
When something breaks, the incident page should already exist before users start asking. We publish incidents as structured records, link them to services, and let the page tell the story.
