Status pages
Public-facing operational pages with components, groups, linked incidents, themes, custom domains, subscribers, and RSS.
A status page exposes a subset of monitors to your customers under /status/<slug> (or a custom domain you verify).
Components
Section titled “Components”Components are what your customers see, not your monitors. Many setups want a single “API” component that aggregates checks from three regions. Create the component, then link the underlying monitors to it. The component’s status derives from the worst observed monitor status: any down → down, else any degraded → degraded, else operational.
Set Display group to bucket components on the page (e.g., Customer-facing, Infrastructure).
Manual updates
Section titled “Manual updates”Public updates posted to a status page appear in the page’s active-incident timeline (if linked to an incident) or in a “Recent updates” history (if standalone). Posting an update can optionally notify subscribers.
Linked incidents
Section titled “Linked incidents”From the status-page editor → Linked incidents → add. The incident appears on the public page until it’s resolved, with a full timeline of updates.
From the incident detail → Send public update also writes to the same timeline.
Maintenance windows
Section titled “Maintenance windows”Schedule a window (starts_at → ends_at) with optional body copy. The window is publicly listed on the status page; alerts for affected monitors are suppressed during the window if the rule has respect_maintenance enabled (default).
Per status page, choose:
- Auto (default) — follows the visitor’s OS
prefers-color-scheme. - Light — force light palette for everyone.
- Dark — force dark palette for everyone.
Override per visit with ?theme=light or ?theme=dark query param (operator preview).
Custom domain
Section titled “Custom domain”To serve a status page from status.customer.com:
- Status pages → Page → Custom domain → Add
status.customer.com. Pulse returns a_pulse-challenge.<domain>TXT record value. - Publish the TXT record on the customer’s DNS.
- Click Verify. Pulse resolves the TXT and, on match, flips the domain to active and queues an ACME issue via Traefik’s on-demand resolver.
Multiple domains per page are supported; the canonical /status/<slug> keeps working alongside.
Subscribers
Section titled “Subscribers”Visitors can subscribe to a status page via email. Pulse double-opts-in: subscriber gets a confirmation link, must click before any updates are sent. Subscribers receive a digest per public update posted on the page.
RSS feed
Section titled “RSS feed”Every status page exposes /status/<slug>/rss.xml. Use it for monitoring tools / aggregators / customer dashboards that prefer feeds over webhooks.
Status-aware favicon
Section titled “Status-aware favicon”The browser tab icon is an inline SVG colored by overall status: violet (operational) → amber (degraded) → red (down). Pin the status page tab and you’ll see the favicon flip the moment status changes.