Status Pages and Reports
Understand status page publishing, resources, sections, incident reports, and maintenance updates
A status page publishes service health information for customers or internal stakeholders. It contains page settings, public resources, incident reports, and maintenance windows.
A status page has settings and visibility
Status page settings control the public identity and access state.
| Setting | What it controls |
|---|---|
| Company Name | Name shown on the status page |
| Sub Domain | Public status page subdomain |
| Get in touch URL | Optional contact link |
| Announcement | Message shown on the status page |
| Status History | Number of days shown in the resource chart |
| Status page access | Whether visitors can access the page |
A hidden status page remains configured but is not publicly accessible.
Sections organize public resources
Sections group checks and custom incident services on the status page.
Each resource can have:
| Field | What it changes |
|---|---|
| Public Name | Visitor-facing resource name |
| Explanation | Visitor-facing context for the resource |
| Widget Type | Whether the page shows history, chart, both, or neither |
Sections can hide their heading when the section name is blank.
Reports explain incidents
Reports are public updates about incidents. A report starts with a summary and an initial update.
Incident report updates can use these statuses:
| Status | Meaning |
|---|---|
| Investigating | The team is still finding the cause |
| Identified | The cause is known |
| Monitoring | The fix or recovery is being watched |
| Resolved | The incident is complete |
The latest update controls the report's current status and affected resources.
Maintenances explain planned work
Maintenance windows communicate planned work. A maintenance has a summary, affected resources, start and end time, and updates.
Maintenance updates can move through scheduled, in-progress, and complete states.
Public responses hide internal identifiers
Public status page responses omit internal tenant data and hide resource IDs that visitors do not need. Visitors see public names, explanations, widget choices, reports, and status history.