Status pages
A status page is a public, shareable view of your service health — component status plus incident history — assembled from the monitors and hosts you already run.
- Read
- 3 min
- Sections
- 3
- Plans
- All plans
Create a page
Give the page a title and a slug — the slug is the public URL. Pick a light or dark theme and choose whether the page is publicly accessible. A private page is reachable only with the link disabled.
Components & incidents
Add components and bind each to a monitor. The component’s status reflects the monitor’s latest check, and when a monitor opens an incident it surfaces on the page automatically. You can also post manual incidents (e.g. a planned migration) with updates.
The public endpoint
The page is served anonymously and cached, so it stays up even under load and never exposes private detail — only aggregated component status and incident summaries, never stack traces or internal errors.
GET /api/v1/public/status/{slug}
# No auth. Cached ~30s. Returns component status + recent incidents.