Communication
Status pages
Status pages give customers and internal stakeholders a reliable place to check service health without opening the private dashboard.
What to publish
- Customer-facing APIs and web applications.
- Critical background workflows that customers depend on.
- Services with clear owners and linked monitors.
- Only monitors that are meaningful to the audience of the page.
Configuration
- Set a clear status page title and slug.
- Choose which monitors appear on the page.
- Use status pages to share uptime history and current health.
- Review visibility before sharing the public URL.
Best practices
- Do not expose internal-only monitor names that customers should not see.
- Group status pages by product, environment, or audience.
- Keep monitor names readable and customer-safe when they appear publicly.
- Use incident reviews internally even when the public page only shows current health.