Status Pages
Give customers and teammates a clear view of service health and incident progress.
A status page is an organization-owned page containing the health of linked monitors, heartbeats and components, together with incident history and subscriber updates.
What a status page contains
- Resources — monitors, heartbeats or manual components.
- Current health — the latest state of each linked resource.
- Incidents — open and historical incidents relevant to the page.
- Subscribers — verified email addresses that receive page updates.
Components
Use a component for a service that is not directly probed by a monitor or heartbeat. Components can be up, degraded or down, and their status history is kept separately from automated checks.
Publishing useful updates
During an incident, publish short updates as the situation changes: acknowledge the impact, describe the current work and announce recovery. Avoid internal details or secrets.
Before publishing
- Use a clear page name and description.
- Link only resources that belong to the same service or audience.
- Check the public page in an incognito window.
- Verify subscriber confirmation and notification behavior.
Troubleshooting
A resource is missing from the status page
- Check that the resource belongs to the same project or organization
- Verify that it is linked to the status page
- Refresh the public page after saving the configuration
Subscribers are not receiving updates
- Check that the subscriber completed email verification
- Confirm that the incident update is associated with the correct status page
- Ask the subscriber to check spam or filtering rules