Status pages
Configure and publish component health, incidents, and maintenance.
A status page communicates selected component health, incidents, maintenance,
and history to an audience. An organization can own multiple pages, each
published at /status/{slug}. Open Status pages to create, edit, preview,
and delete them.
Create a page
Select New status page and fill in:
| Field | Notes |
|---|---|
| Name | Required, 2–100 characters. |
| Slug | Required. Lowercase letters, numbers, and hyphens, 2–80 characters. The page is published under /status/{slug}. |
| Description | Optional, up to 500 characters. |
| Access | Public, Private owner preview, or Password protected. Choose the private mode while you are building. |
| Password | Required for password mode, at least 8 characters. |
| Custom domain | Optional fully qualified hostname, configured later on the Access tab. |
Select Create page. The page opens in the editor with tabs Design, Content, Components, Access, and Share.
The save bar under the tabs shows unsaved changes. Preview opens the live page in a drawer. The ⋯ menu offers Open public page, Announcements…, Subscribers…, Copy page path, and Delete status page…. Deleting a page sends it to the recycle bin for 30 days.
Add components
On the Components tab, select Add component. Each component has:
- a name, optional icon, and optional description;
- an optional parent group for nesting (up to five levels deep);
- an optional link to your own documentation;
- a monitors mapping of up to 100 owned monitors—the component reports the worst status among them;
- a Published switch—hidden components keep their history but are not shown;
- an uptime bar and percentage switch;
- a group starts collapsed switch for groups.
Use the arrows to reorder components; the public page renders this exact order and nesting. Delete component… removes one; Delete group and children… removes a group and everything nested in it.
Published component status
A component publishes one of six states rather than a bare up/down:
| State | When |
|---|---|
| Operational | every enabled mapped monitor is up |
| Degraded performance | a mapped monitor is pending or paused, or the most recent average response time exceeds the page's degraded threshold |
| Partial outage | some but not all mapped monitors are down |
| Major outage | every mapped monitor is down |
| Under maintenance | a maintenance window covering a mapped monitor is running, and nothing is down |
| Not monitored | the component maps no enabled monitors |
A group publishes the worst state among itself and everything nested beneath it, and the page banner publishes the worst state across every measured component.
Status overrides
A component can publish a status of your choosing instead of the monitors'. In the component editor's Status override section, pick a published status (otherwise Follow the monitors) and an optional Until time after which the override lifts by itself. Overrides are read by the live page, the widget, and the badge alike, so an intentionally offline service never reads as an unexplained outage.
Incident impact
Incident declarations can select any owned status-page components, and the mapping remains editable throughout the incident lifecycle. The incident workspace displays the affected page and component names. Automatic monitor incidents derive component impact from monitor mappings.
Public pages show only incidents whose explicit component impact includes the page's components, and label the affected components. Internal notes and responder discussion never publish.
Design the page
The Design tab covers:
- Identity: page name, slug, an optional Headline that replaces the page name above the fold, and the description.
- Brand: accent colour, brand bar colour, and optional logo, favicon, and social-preview image URLs. Colours are six-digit hex values.
- Appearance: default theme (Match visitor, Light, or Dark), component layout (List or Cards), and whether visitors get a theme switcher.
- Custom CSS: up to 20,000 characters, applied to the page, its archive, and the unlock screen. Markup is rejected.
Choose the page content
The Content tab chooses what the page publishes. Each section is a switch:
- Status banner, Uptime bars, Uptime percentage, Response times, Active incidents, Planned maintenance, Past incidents, Subscribe form, and Powered by Status.
History options:
- Uptime window: 24 hours, 7, 30, 60, or 90 days.
- Past incidents cover: 1–365 days of the past-incident strip.
- Time zone: every date and time on the page uses it.
- Language: English, Spanish, or French. A visitor's saved public-page language preference takes priority, followed by the page default and then the browser's accepted languages.
Advanced options add up to eight header and eight footer links (absolute http(s) URLs), and a Degraded above response-time threshold that makes an otherwise-up component read as degraded; 0 turns it off.
Every page links to a reverse-chronological history archive that merges resolved incidents with completed, cancelled, or elapsed maintenance windows. It applies the same scoping rules as the live page and never includes internal incident notes.
Control access
The Access tab sets who can read the page:
- Anyone with the link: public, cacheable, indexable unless you disable indexing.
- Owner preview only: visible only to the authenticated owner; everyone else receives a 404, and the page is never indexed.
- Password protected: visitors unlock the page with the password. A blank password field keeps the current one; changing it signs unlocked visitors out. Unlock attempts are limited to five per visitor per ten minutes, and a successful unlock stays valid for seven days. Password pages answer 404 from badges, widgets, and RSS.
Custom domains
Enter a fully qualified hostname, such as status.example.com, then add the
displayed DNS record at your provider:
TXT _status.status.example.com "status-verification=<page challenge>"Select Verify DNS once the record is published. Until verification succeeds, requests to the custom domain keep going through the ordinary console instead of the status page. TLS certificates and external DNS routing remain deployment responsibilities. Clearing the hostname removes the verification.
Share the page
The Share tab configures discovery and embeds:
- Meta title (up to 70 characters), Meta description (up to 160 characters), and a Social image URL for link previews.
- Search indexing: private and password-protected pages are never indexed regardless of this setting.
For public pages, ready-to-copy snippets:
- a Markdown status badge (
/api/status/{slug}/badge.svg); - an HTML widget iframe (
/status/{slug}/embed); - the RSS feed URL (
/api/status/{slug}/rss.xml), which merges page-scoped incidents and maintenance, newest first, up to 100 items.
Schedule announcements
Announcements… in the page menu schedules a title and message with an absolute Publish at time and an optional Expire at time (the visible span cannot exceed one year). Announcements appear on the live page only while they are active; future and expired content is never shown.
Subscriptions
A public page can offer readers a Subscribe form (a Content tab switch). Subscribers confirm their destination before receiving anything. Manage and remove subscribers under Subscribers… in the page menu. See Status-page subscriptions.