Components and Groups
Organize your services into components and groups on your status page for clear, structured communication.
Components and Groups
Components are the building blocks of your status page. Each component represents a service, system, or feature that you want to communicate the health of to your users.
Adding components
To add a component to your status page:
- Open the status page settings
- Click Add Component
- Enter a name (e.g., "API", "Website", "Dashboard", "Database")
- Optionally, add a description that explains what the component does
- Save
Component names should be meaningful to your users. Use names they would recognize -- "API" is better than "api-gateway-prod-us-east-1" for a public-facing status page.
Linking components to monitors
The real power of components is linking them to your service monitors. When a component is linked to a monitor:
- The component status updates automatically based on the monitor's health
- When the monitor is up, the component shows as Operational
- When the monitor fails, the component status changes to reflect the outage
- When the monitor recovers, the component automatically returns to Operational
This means you do not need to manually update component statuses during an outage -- it happens in real time as your monitors detect problems.
To link a component to a monitor, select the monitor from the dropdown when creating or editing the component.
Component states
Each component can be in one of five states:
| State | Color | Meaning |
|---|---|---|
| Operational | Green | The service is working normally |
| Degraded Performance | Yellow | The service is working but slower or with reduced functionality |
| Partial Outage | Orange | Some parts of the service are unavailable |
| Major Outage | Red | The service is completely unavailable |
| Under Maintenance | Blue | The service is intentionally offline for scheduled work |
When linked to a monitor, the transitions between Operational and outage states happen automatically. You can also manually set a component to any state -- for example, setting it to Degraded Performance when the service is slow but not fully down, or Under Maintenance during a planned deployment window.
Component groups
Groups let you organize related components under a collapsible section. This keeps your status page clean and scannable, especially when you have many components.
Example groups:
| Group | Components |
|---|---|
| Core Services | API, Website, Dashboard |
| Infrastructure | Database, Cache, CDN |
| Third-Party Integrations | Payment Gateway, Email Provider, SMS Provider |
To create a group:
- Click Add Group on the status page settings
- Enter a group name
- Drag components into the group, or select the group when creating a new component
Groups show a summary status based on the worst state among their components. If one component in the group has a Major Outage, the group header shows the Major Outage indicator.
Reordering components and groups
Drag and drop to reorder components within a group or reorder groups on the page. The order you set is the order users see on the public status page.
Put your most important services at the top so users can quickly find what they care about.
Visibility
Each component has a visibility setting:
| Visibility | Behavior |
|---|---|
| Public | Visible to everyone who visits the status page |
| Internal | Visible only to authenticated organization members |
| Hidden | Not shown on the status page at all |
Internal components are useful for backend services that your team wants to track but that are not meaningful to external users. Hidden components let you temporarily remove a service from the page without deleting the configuration.
Display options
You can toggle two additional data points for each component:
- Show uptime percentage -- Displays the component's uptime percentage (e.g., "99.95%") calculated over the last 90 days. This gives users confidence in your service reliability.
- Show response times -- Displays average response time data from the linked monitor. This is useful for API-focused products where latency matters to users.
Public response time display is available on Ultra plans and above. Pro plans can display uptime percentage but not response times.