Public status pages

A status page is a public, read-only view of the monitors you choose to publish. Anyone with the link can open it — no account, no sign-in — and see the current state of each system. During an incident it answers "is it down?" once, for everyone, instead of one phone call at a time.

A status page carries no identity: it doesn't know who's looking, and it shows exactly the monitors you picked — nothing more. For a signed-in, client-specific view with incident detail, that's the client portal.

Creating one

In the console, open Status pages and choose Create:

1. Name — internal only. This is how the page appears in your console list; visitors never see it. "Acme — public" is a fine name.
2. Public heading — the title shown at the top of the page itself. Leave it blank and the page uses your workspace name.
3. Published — the on/off switch, on by default. While it's off, the page's URL answers "not found"; your configuration is kept.
4. Monitors — pick any set of your workspace's monitors. The picker isn't limited to one client: each option is labelled client — site — monitor, so you can build a page for one client, one site, or a cross-client selection such as every internet link you manage. Two clients can both have a "File Server", so read the full label before choosing.

Below the picker are four content toggles that decide which figures accompany each monitor — uptime, response times, history bars, and recent events. They're covered in Status page options.

The link

Every page gets a URL of the form:

https://{workspace}.upall.app/status/{token}

The token is a random 40-character string, so the URL is effectively unguessable — and it is the only key. There's no password in front of it, and search engines are told not to index it. That security model, and the Regenerate link button that replaces the token, are covered in Sharing and regenerating links.

What visitors see

Monitors render grouped by site, one row each: a status glyph and the monitor's name. The name only — never the target, hostname, IP, or port. A public page should not map anyone's infrastructure, so if a monitor's name contains an internal address, rename it before publishing.

At the top, an overall banner sums up everything on the page, worst state first:

The precedence is deliberate: red beats amber, and a stale monitor makes the headline "unknown" rather than letting old data claim green. The states themselves are explained in Monitor statuses explained.

The page is rebuilt from the latest checks each time it's loaded (results are cached for at most a minute), so what a visitor sees is never more than about a minute behind reality.