Status pages on the client’s own domain

How many pages each plan gets

The limit is on pages, not on monitors shown. Free includes 1, Starter 3, Pro 10 and Agency has no cap. One page can show any number of monitors, so a studio with forty small sites usually builds a handful of pages by client or by product, not one per site. A custom domain starts on Starter, white-label (no Tenium branding at all) on Pro. On Free the page lives on a Tenium address and carries our branding, which is fine for a side project and not what you want to hand a paying client.

Putting a page on the client’s domain, step by step

The usual choice is a subdomain such as status.clientsite.com. The setup is four moves and takes a few minutes of your time plus DNS propagation.

• Create the page under Status pages, pick the monitors (or on Agency a whole client workspace), give each a public name and group them into sections.
• In the page settings open the custom domain field and enter status.clientsite.com. The settings screen shows the CNAME target to use.
• At the client’s DNS provider add a CNAME record for status pointing to that target. If the zone is on a provider that offers a proxy toggle, leave the record unproxied until the certificate has been issued.
• Wait for propagation. The certificate is issued automatically, normally within a minute of DNS resolving, and the page is served over HTTPS only.

What visitors see

Each component shows its current state with a daily bar chart covering 90 days and a 30 and 90 day uptime figure. Components are grouped into sections you name, for example Website, Checkout, Email. Incidents open and close by themselves when the underlying monitors change state, and you can post manual incidents and scheduled maintenance with updates, which also go into the RSS feed.

If you switch on Show regional status, a problem that only some regions can see appears as degraded instead of a full outage. This is a deliberate choice, because it is honest about partial failures, and some clients prefer a page that only shows hard outages. Both are legitimate; decide with the client before the first incident, not during one.

Subscribers, and what they receive

Visitors can subscribe by email or follow the RSS feed. Email subscribers get a message when an incident opens, on each update and when it resolves, and the same for scheduled maintenance if the window is set to notify them. The subscriber list belongs to the page and can be exported, which matters when a client leaves and takes their audience with them.

How uptime is shown, and the maintenance exclusion

The percentage on a page is computed from the same incidents you see in the app, so the two always agree. Maintenance windows that are set to exclude downtime are left out of the figure, which is why a page can honestly show 100% in a month that included a two-hour migration. The detail is on maintenance windows.

Longer history lives in the monitoring data rather than the page: raw check history is kept for 90 days on Free, 365 on Starter and Pro, and 730 on Agency.

Limits and honest alternatives

A status page is a communication tool, not an incident tracker for engineers. There is no private page option with SSO, and we do not run a page for components that are not monitored by Tenium, other than manual incidents you post by hand. If you need a deeply customised page design, CSS overrides or per-visitor access control, a dedicated status-page product will go further.

What you do get is a page that costs nothing extra per page on higher plans and stays in step with the rest of the account. Other tools charge for each branded page; check their pricing pages before you compare totals. To brand the page for a client, continue to white-label.