Components and statuses
The component tree (categories up to three levels deep), the five renamable component statuses, worst-child rollup, and how 90-day uptime is derived.
Components and statuses
A status page is built from components - the individual services you report on - optionally organized into categories. You manage the whole tree from the page editor's Components tab.
The component tree
- Components are leaf items; each carries a current status.
- Categories group components (and other categories). The tree can nest up to three levels deep.
- Drag the handle to reorder items or move them between categories.
- Only leaf components count toward the free-tier 5-component cap; categories are free.
A category's status rolls up to the worst of its children automatically. You can instead pin a category to a manual status if you want to override the rollup.
The five statuses
Every component is in one of five statuses. The labels are renamable per page (Customize tab); the colors are fixed so visitors learn them once:
| Status | Default label | Color |
|---|---|---|
operational | Online | green |
degraded | Degraded | yellow |
partial | Partial Outage | orange |
outage | Outage | red |
maintenance | Maintenance | blue |
The page's overall headline ("All Systems Operational", etc.) is derived from the worst component status and is also renamable per page.
Setting status
There are two ways a component's status changes:
- Quick toggle. Change a component's status directly from the Components tab. The public page updates immediately. Quick toggles do not open an incident and are not counted toward downtime.
- From an incident. Posting an incident update can set the status of one or more affected components (see Incidents). These changes are recorded, so they feed the uptime history.
Uptime
Each leaf component can show a 90-day uptime bar on the public page (toggle per component, and page-wide in Customize). Uptime is derived from incident history: a component counts as down for the span an incident set it to a non-operational status, until the incident resolves (which auto-resets affected components to operational). The page header shows the average uptime across components.