Status pages
Understand status pages
Use a status page to give people outside your monitoring workspace a read-only view of service health without granting them a GetPulseCheck account.
What a status page shows
A published page displays the monitors you choose, arranged in the groups you define. Visitors can see the overall state, each monitor's current state, uptime over your plan's history window (30 days on Free, one year on Pro and Team) when analytics are available, and when the page configuration was last saved.
- Operational, Degraded, Down, Paused, or Unknown for the overall and individual monitor status.
- The selected monitor's target and display name.
- Uptime over your plan's history window, or
—when there is no analytics data. - The page configuration's last-updated time and a live relative refresh label.
Know which status surface you are using
- Hosted demo:
/statusis a static marketing demonstration with illustrative service data. It is not your workspace's public page. - Published page: the dashboard editor saves one tenant-specific page at
/s/your-slug. This page uses your selected monitors and live status data, and anyone with the URL can view it without signing in.
Current scope
Status pages currently support several pages per workspace (capped by your plan), a path-based URL, grouped monitors, a custom accent color, an optional logo, hiding GetPulseCheck branding, and a custom domain — each gated by your plan. Subscriptions and incident history are not available.
Custom domain
Plans that include custom domains can serve a status page at your own hostname instead of /s/your-slug. From the page's editor, add your domain, then point a CNAME record at it (or an A record, for an apex domain) — plus a TXT verification record if Vercel asks for one. Click Check DNS once the records are live; the page starts serving on your domain automatically, with a certificate issued for it.