Status pages

A published page is public at /status/your-slug. Visitors do not sign in. An unpublished page is not served there.

Create

1. Open Status pages in the dashboard and start a page.
2. Enter a name, a slug, and an optional description.
3. Select at least one monitor. You can add a manual component later in the editor.
4. Choose whether search engines may index the page, then publish.

Free includes 1 status page, Pro includes 10, and Enterprise is unlimited. Unpublished pages count. If a plan change leaves more pages than the new cap, those pages stay online. Delete pages until the workspace is within the cap before creating another.

Presets, blocks, and appearance

The editor starts from a preset. Changing the preset rebuilds the layout.

• Detailed — components with uptime, incidents, maintenance, a note, and subscribe.
• Minimal — component status without uptime metrics.
• Grouped — components in a named group, plus a response-time chart.
• Rollup — a collapsed group summary and uptime bars.

You can add a section, status banner, component, component group, uptime bars, response-time chart, incident feed, maintenance list, Markdown text, or subscribe form. Appearance covers the brand color, logo, dark mode, a compact header or a hero band, an icon or a wordmark, intro text, up to six header links, and footer text. “Powered by” stays on unless the workspace is allowed to remove it.

Custom CSS and header or footer HTML are saved only on a verified custom domain. A stylesheet that uses url(), @import, a script, or unbalanced braces is rejected, and the previous look stays.

Preview, publish, and manage

Preview shows the draft, including changes that are not published yet. From the status page list you can edit, copy the public link, open the live page or the preview, publish or unpublish, and delete. Page settings also has a published switch. Publishing an existing page does not create another page.

Subscribers

A visitor enters an email on the page. The address stays pending until they open the confirmation link, which expires after 48 hours. The email also includes an unsubscribe link. Visitors are not signed in.

The cap is Free 50, Pro 500, and Enterprise unlimited. Pending and confirmed rows both count. Page settings, under Email subscribers, lists confirmed subscribers and can remove one. CSV import and export are in that same section when CSV is enabled, which is the default. An import creates pending rows and still requires confirmation. There is no separate screen for assigning components to a subscriber. When component subscriptions are enabled for the workspace, the public form can limit updates to selected components.

SMS and Slack are available only when that capability and the workspace integration are set up. Slack is connected by the page owner. Microsoft Teams is not a delivery channel. When the page is already at its cap, the public form still shows the generic confirmation message and does not store the address.

Custom domain

Custom domains are available unless that capability is turned off for the workspace. The page is served on the hostname only after DNS verification and only while the page is published. A platform hostname cannot be claimed.

1. In page settings, enter the hostname, for example status.example.com, and save it.
2. Create the TXT record the product shows. The name is _uptm-challenge.your-hostname. The value starts with uptm-site-verification=.
3. Choose Verify DNS. The state is pending until the lookup succeeds, verified when the TXT matches, or failed with the error from the lookup.
4. Point the hostname at the dashboard edge with a CNAME or an A/AAAA record.
5. Terminate HTTPS on that edge and forward the Host header to the dashboard.

UPTM does not issue the certificate. Certificate status stays pending until an operator’s edge reports otherwise. Pending is not an issued certificate. Failed means the edge reported a provisioning failure. Active is shown only when the edge reports that the certificate is issued. Removing the domain drops the hostname and the custom CSS and HTML that required it.

Password protection, an IP allowlist, extra languages, embeds, and the maintenance calendar are separate capabilities. They are off until enabled for the workspace. The seeded rule turns them on for Enterprise. Visitor SSO is not part of this release.

Public API reference