Status pages
The editor
Section titled “The editor”Components arrange by drag and drop into groups, and uptime windows show 7, 14, 30, 90, 180, or 365 days. Changes save explicitly against a draft baseline, and every save creates a numbered version with its author. Versions from the last 90 days restore in one click. A deleted page moves to the archive, where you can restore it for 90 days.
Access modes
Section titled “Access modes”Per page: draft, public, shared password (one password, stored as a hash, never shown again), or viewer accounts (individual sign-ins). Gated modes are included from Sentinel. Sign-in endpoints are rate-limited.
Your own domain
Section titled “Your own domain”Serve the page at status.yourcompany.com: verify by CNAME or TXT record, and Perstat issues and manages TLS automatically. Sentinel carries 3 custom domains per page, Command 10.
The CNAME target is a token host, something like 359db456….perstat.io. The token proves
that you control the zone, which a predictable slug could not.
Good to know before you tidy up DNS later: a domain pointed at the slug host still serves correctly, because delivery keys off the Host header. Re-verification, however, expects the token target. Verified domains stay verified, so keep the CNAME on the token target shown on the domain’s card, and every re-verification succeeds.
Subscribers
Section titled “Subscribers”Email subscriptions are double opt-in: signing up sends a confirmation mail, and the address joins the list once that link is followed. Everyone on your list has confirmed, and the subscriber list shows each confirmation timestamp, so a pending address is visible as pending.
Subscribers are notified when an incident opens and when it is resolved, and every mail carries a one-click unsubscribe link backed by its own token. You can also remove a subscriber yourself from the page’s subscriber list.
Included from Sentinel.
White-label
Section titled “White-label”From Command, rendered pages carry your brand alone, with separate light- and dark-mode logos,
and without the Powered by Perstat link. On other plans, that footer link points to
perstat.io. See Plans and limits.
One record for pages and evidence
Section titled “One record for pages and evidence”The page is fed by the same record as your SLA evidence: the incident your subscribers saw and the incident your auditor reads are the same incident with the same boundaries. Maintenance windows show as banners while they suppress alerts, and the page carries an SVG badge and an RSS feed for the people who want the status in their own tooling.
Status pages are scriptable too: with status-pages:write, the REST API creates pages,
assigns monitors, adds and verifies custom domains, and manages access.
- Reading a status page: what your customers see on it.
- Maintenance and curation: announce planned work on the page.