Status pages & service catalog
Status pages provide a real-time communication layer for users and stakeholders.
By linking incidents and maintenance events to service catalog entities, you ensure accurate and transparent updates across all status boards.
This page explains how incidents and maintenance updates are reflected on status boards and how service associations control visibility and impact.
View Incident Impact on Services via the Status Board
When working with incidents, you can control how updates are reflected across one or more status boards.
What you can do
- Publish to board — Control whether the incident appears on selected status boards
- Link services — Associate affected services or components from the service catalog
- Select boards — Choose which boards should display the incident
- Update service status — Reflect real-time states like Operational or Degraded
- Track changes — View timeline updates and incident history
These controls ensure that users see the correct impact based on affected services and systems.
Always verify service associations before publishing to ensure accurate communication on status pages.
View Maintenance Impact on Services via the Status Board
Maintenance events follow a similar workflow, allowing planned changes to be communicated clearly and proactively.
What you can do
- Schedule visibility — Show maintenance windows on status boards in advance
- Associate services — Define which services are impacted
- Control board visibility — Choose where maintenance updates appear
- Update maintenance status — Reflect stages like Scheduled, In Progress, or Completed
- Ensure clarity — Provide consistent updates across all affected platforms
This helps set expectations and keeps users informed about planned disruptions.
Service catalog and ownership
The service catalog is the backbone of status communication.
- Each incident or maintenance event is tied to specific services or components
- Ownership ensures the right teams manage updates
- Proper mapping ensures accurate visibility across all status boards
Keeping your catalog updated improves both internal coordination and external communication.
Best practices
- Link every incident or maintenance event to the correct service catalog entities
- Use status boards selectively based on audience and visibility needs
- Keep updates timely and consistent
- Review affected services before publishing updates
- Maintain clear ownership for faster response and communication