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
- 5
- 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.
Branding and custom domain
A status page carries your logo and an accent colour, and renders in a light or dark theme. It can also be served from your own domain — point a CNAME at DataRunner and set the custom domain on the page, so customers reach status.yourcompany.com rather than a URL that reads like a vendor subdomain.
Subscribers
Visitors can subscribe to a status page by email to be told when something breaks and when it is fixed, instead of having to remember to check. Subscription is double opt-in: the address is stored unconfirmed and only starts receiving mail after the confirmation link is followed. Every notification carries a one-click unsubscribe token.
POST /api/v1/public/status/{slug}/subscribe
Content-Type: application/json
{ "email": "ops@customer.com" }
# No auth. Creates an unconfirmed subscriber and emails a confirmation
# link. Subscribing an address that already exists is a no-op, so the
# endpoint cannot be used to probe who is on the list.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.