Skip to content

Share public status pages

Public pages expose selected monitoring information without requiring account sign-in. Their token links are access links, not heartbeat ingestion URLs.

An Admin can publish a custom dashboard:

  1. Create a custom dashboard and add only the intended checks.
  2. Review names, incident updates and visibility settings.
  3. Edit the dashboard, enable Public and save.
  4. Copy the public URL shown by the app.
  5. Open it in a signed-out browser and inspect the actual audience experience.

Dashboard visibility settings with Public enabled and the generated public link hidden.

Copy the link privately from your dashboard. The demo link is hidden here; enabling Public allows anyone with that link to view the selected information.

The account’s Overview cannot be published. Public dashboard links use /status/dashboard/<token>; public wallboards append /wallboard. Disabling Public makes the dashboard unavailable through its public link. Do not assume toggling sharing rotates the token.

Individual checks have token-based status pages at /status/<token>. Retrieve the link from the signed-in check, not by constructing it from a check ID. A status token is not the location token used at /ping/<token>.

Anyone with an accessible public link can read the visible information. A hard-to-guess link is not identity-based authorization. Do not put confidential service names or incident text on a page merely because you have not advertised its URL.

Use the signed-out view to verify exactly which details, locations, performance and incidents are shown. Automation can return already-public dashboard links but cannot enable sharing or change branding.

These features provide hosted token-link pages; do not assume customer custom-domain configuration is available from the dashboard form.