Public status page#
A public status page is a page anyone can open, with no login, showing whether the things you choose to publish are up. It’s for your customers or team to check “is it down, or is it just me?” without asking you.
It’s off by default, and publishing is a deliberate two-step choice: you turn the page on for the organisation, and then you opt in each individual check you want listed on it.
The public status page is not the Status item in the navigation bar. That one is your own private view of what’s failing right now; this one is public. See Reading the dashboard.
Turning it on#
- Go to Organisation settings (from the menu under your email address in the top right), find Public status page, tick Publish a public status page, and save.
- The page then shows Live at followed by its address, of the form
https://tenpmuptime.com/status/<slug>. Share that link.
The address is derived from your organisation’s name when the organisation is created. Renaming the organisation later doesn’t change it, so a link you’ve already shared keeps working.
The public status page is a paid-plan feature — see Plans and billing. On a plan that doesn’t include it, the toggle isn’t offered.
Choosing which checks appear#
Turning the page on publishes nothing by itself. For each check you want listed, open its edit page and tick Show this check on the organisation’s public status page, under Status.
Two things can stop a check being published:
- A restricted check can’t be published at all — the option is replaced by a note saying so. A check that only runs on your own monitors because it targets an internal address, or because you asked for it to stay off the shared fleet, is exactly the kind of thing you don’t want on a public page. See Shared vs. private monitors, and restricted checks. If an already-published check later becomes restricted, it’s removed from the page automatically.
- A check that the platform has disabled is left off the page, so a visitor is never told “Operational” about something that isn’t being monitored.
Heartbeat checks aren’t shown on the status page — only checks are.
What visitors see#
For each published check, only:
- its name,
- its current status — Operational, Down, or No data if it hasn’t reported yet,
- its uptime over the last 30 days,
plus an overall banner: All systems operational, Some systems are experiencing issues, or Status pending if nothing has reported.
That’s deliberately all. There’s no URL, no error text, no response detail and no indication of which monitors run the check — nothing that could leak how you’ve set something up. Pick check names you’re comfortable showing publicly.
Turning it off#
Untick the toggle and save. The page stops working straight away and its address returns a plain “not found”, the same as an address that never existed — a visitor can’t tell “off” apart from “there’s no such page”.
The same happens if your organisation moves to a plan that doesn’t include the status page: it goes dark immediately rather than staying up until you next touch it. Nothing is lost — your per-check choices are kept, and the page comes straight back if you’re on a plan that includes it and the toggle is still on.