Status pages

A status page is a public web page that shows the live status and uptime of the monitors you choose. It’s how you keep customers and teammates informed without fielding “is it down?” messages during an incident.

Want to see one before you build your own? There’s a live example at /status/demo.

1. 1

   Open Status pages

   From the dashboard, go to Status pages.

2. 2

   Name it and pick a slug

   Give the page a name, and pick a slug — a short word or two that becomes part of its web address. Once saved, the page is published at /status/your-slug.

3. 3

   Add the monitors you want to show

   Pick which of your monitors appear on the page, arrange the order they show in, and — if you have more than a handful — sort them into categories. More on that below.

You decide which of your monitors appear on the page — the rest stay private. You also choose the order they appear in, so you can group and prioritise them the way you want.

Each monitor is shown using the friendly name you gave it when you created it.

Once a page carries more than a handful of services, a flat list stops being readable. Categories break it into named blocks — one per part of your estate — each with its own heading, status and 90-day uptime, so a visitor can see at a glance which part is unhappy:

• cPanel Servers — cPanel Server 1, cPanel Server 2
• DirectAdmin Servers — DA 1, DA 2
• FTP Servers — FTP 1, FTP 2

Open a status page, go to Monitors & categories, name a category and add it. Use Move… on any monitor to file it under a category, the arrows to order monitors within a category, and the arrows on a category heading to order the categories themselves. Nothing is published until you press Save layout, so a half-finished rearrangement never reaches a live page.

• Monitors you leave ungrouped appear at the top of the page, above the categories and without a heading.
• Categories belong to the page, not the monitor — the same monitor can sit under different headings on two different status pages.
• Deleting a category never removes its monitors from the page; they simply go back to being ungrouped.
• An empty category is not rendered publicly, so you can set one up before the monitors that belong in it exist.

Make the page look like yours:

• Description — a short blurb shown on the page to give visitors context.
• Logo — added by URL, so your brand mark sits at the top of the page.
• Header colour — sets the page’s header tone. It defaults to a dark navy (#0E1422) and you can change it to match your brand.

Every status page has a visibility switch. While a page is public — the default — anyone with its link can open it. Turn visibility off and the page goes offline: visitors get a “not found” page until you switch it back on.

A private page is still visible to you. Every status page has a preview link — /status/your-slug/preview — that renders the page exactly as visitors would see it, but only for signed-in members of your organization. Use it to check a page before you publish it, or to keep an internal status board that never goes public. Anyone else, signed in or not, gets the same “not found” page.

A published page can also be put behind a password. Set one under branding and visitors must enter it before they see any services, uptime or incidents — the page shows only its name. The password is stored hashed, so it can be replaced but never read back; changing or removing it immediately signs out everyone who had unlocked the page. Members of your organization are never prompted. This applies on your custom domain too.

For each monitor you list, the page shows its current status and the last 90 days of uptime as a row of daily bars, plus a feed of recent incidents. During an outage your users can see exactly what’s affected — without opening a ticket. Status pages pair naturally with incidents, which capture when an outage started and how long it lasted.

• Managing monitors — the monitors you choose to list on a status page.
• Incidents — what your visitors are seeing during an outage.