Components & grouping
Build your status page out of the services customers recognize.
A component is one thing on your status page that customers care about — "API", "Website", "Dashboard", "EU region". Each is backed by one or more monitors, so its state reflects reality automatically.
Building the page
- Add a component and attach the monitors that represent it.
- Group components into sections (e.g. Core services, Regions) and collapse groups to keep a long page tidy.
- See live counts as you build, so you know what each group contains.
Rolled-up vs. detailed
You choose how much a component reveals:
| Style | Shows |
|---|---|
| Detailed | Each component's individual state. |
| Rolled-up | One aggregate indicator for a whole group — clean and simple. |
Use rolled-up groups when customers only need the headline, and detailed components when they want specifics.
Per-component history
Each component tracks its own status over time, feeding the uptime heatmap so visitors can see how stable a service has been — not just its state right now.
Tags make it easy to find the right monitors when assembling components — tag by service or region, then add them in one go.
Third-party components
Your service depends on others — GitHub, Cloudflare, Stripe, GitLab. When one of them has an outage, your customers feel it, and "is it you or your provider?" is the first question they ask. A third-party component answers it: it mirrors an external service's own public status page, live, right next to your own components.
To add one, choose Third-party service when adding a component, search the catalog (GitHub, Cloudflare, Stripe, GitLab, OpenAI, Slack, Google Cloud, and 30+ more), and either pick the specific parts you rely on (e.g. GitHub Actions and Webhooks) or leave them all unchecked to show the provider's overall status as one line.
- Status refreshes automatically every few minutes from the provider's public status page — nothing to configure.
- A 30-day uptime history builds up over time: collapsed and rolled-up components show a heatmap and uptime %, so visitors see the recent track record, not just the current moment. (History starts from when you add the component — a provider's past can't be back-filled.)
- The same display modes as your own components apply — rolled-up (overall only), collapsible (expand to see each part), or expanded.
- Each third-party component links to the provider's own status page, and flags when its data is momentarily delayed.
- A provider's outage doesn't flip your page's own "all systems operational" banner — it's their outage, not yours. The component shows the issue in place, while your overall status keeps reflecting only the services you run.
- It counts as a regular component on your page; there's no separate limit.
Don't see a service you need? Let us know — the catalog grows on request, and almost any service running on a standard status page can be added quickly.