Status Pages
Status Pages
Publish hosted or protected service status pages with incident history.
Status pages let you publish check/server health externally. Each page has a hosted slug URL and can optionally use private visibility, password protection, and a custom domain.
Hosted URL Model
Hosted URL Pattern
https://pulsebeacon.io/status/{slug}- Slug is per-user unique and generated from page name if empty.
- You can edit slug later; PulseBeacon keeps uniqueness by auto-adjusting duplicates.
- Hosted URL keeps working even if custom domain is disconnected.
Visibility and Access
| Setting | Behavior |
|---|---|
| Public | Anyone with URL can view page. |
| Private | Only owner can access; non-owners receive 404. |
| Password-protected | Visitors must unlock with password before component and incident data is shown. |
Password Update Behavior
On edit: leaving password blank keeps the current password. Enter
- to remove password protection.
Components
- Add checks and servers to each status page.
- Optional display name overrides per component.
- Optional group name for sectioning (API, Frontend, Infrastructure, etc.).
- Sort order controls display position inside each group.
Visitors only see confirmed status
Components display the confirmed state of each monitor. A monitor that is currently
re-checking an unconfirmed failure keeps showing its last confirmed state, so transient blips never appear as public outages.
Warning states (for example an expiring SSL certificate) appear as Degraded, not Down.
Incident History
- You can choose how many days of incidents to display publicly.
- The timeline shows monitor and server incidents related to components on this page.
- Component history bars/dots use check pings and server metrics in the configured window.
Operational Checklist
- Create a status page from the Status Pages section.
- Set visibility, headline, incident window.
- Attach components and verify status labels.
- If needed, connect custom domain and verify.
- Share URL with customers/stakeholders.