Status pages

A status page is a public (or private) view of a hand-picked set of your monitors. Visitors see whether each component is up, recent uptime, and any incident updates you’ve posted — without needing an Aloft account.

Each page lives at /status/<slug>, where the slug is a short, URL-friendly name you choose. Open Status pages from the top navigation to manage them.

Note

Status pages belong to the organisation you’re currently working in, just like monitors and channels. If you don’t see a page you expect, check the org switcher in the top bar — see Teams and roles.

Create a status page

1. Go to Status pages and choose New page.
2. Fill in the form:
   • Name — the title shown at the top of the page (e.g. Acme status).
   • Slug — lowercase letters, digits, and hyphens only. This becomes the URL: a slug of acme is served at /status/acme.
   • Public — leave the toggle on to make the page reachable by anyone with the link. Turn it off to keep it private (see below).
   • Description (optional) — a sentence shown under the page title.
3. Under Monitors to display, tick the monitors you want to appear. Only monitors in your current organisation are listed. You can pick none for now and add them later.
4. Choose Create status page.

Your page is now live at /status/<slug>. Each monitor appears as a component with a 90-day uptime bar, 24-hour and 90-day uptime percentages, and average response time.

Tip

You can revisit any of these settings later from Status pages → Edit. Changing the slug changes the public URL, so update any links you’ve shared.

Public vs. private

The Public toggle controls who can reach the page:

• Public — anyone with the URL can view it. No sign-in required. This also enables the email subscription form and the RSS feed.
• Private — the page returns a “not found” response to visitors, and the subscribe form and RSS feed are disabled.

Access is keyed by slug alone — there’s no per-visitor login for public pages, so treat the slug as effectively public once you’ve shared it.

Customise branding

On the New page or Edit form you can tailor the look of the page:

• Brand color — a hex value like #1d4ed8 (or an hsl(...) string). It tints the accent colour, the call-to-action button, and the focus ring on the public page.
• Logo URL — a link to an image (e.g. https://example.com/logo.svg). When set, your logo replaces the default shield icon in the page header.

Both are optional. Leave them blank for the default Aloft styling.

Point a custom domain at your page

You can serve a status page from your own hostname, such as status.example.com, instead of /status/<slug>.

1. In the page’s Edit form, set Custom domain to the hostname you want to use (e.g. status.example.com).
2. At your DNS provider, add a CNAME record for that hostname pointing at the same target as your Aloft deployment’s APP_URL.
3. Save. Once DNS propagates, visiting https://status.example.com/ serves your status page at the root of that domain.

Note

Only the public status routes are served over a custom domain — the dashboard and API stay on your canonical Aloft host, so pointing a domain at Aloft can never expose your dashboard at status.example.com.

Post incident updates

When something breaks, keep visitors informed by posting updates. From Status pages, choose Posts on the page you want to update. Updates appear in the Updates section of the public page, newest first.

Each post has:

• Title — a short summary (e.g. Elevated 5xx on /api/v1/orders).
• Status — one of the four lifecycle stages below.
• Update — the body text. Keep it short and factual.

The incident lifecycle

Posts move through four statuses, mirroring the typical arc of an outage:

Status	Meaning
Investigating	You’ve noticed a problem and are looking into it.
Identified	You know the cause and are working on a fix.
Monitoring	A fix is in place; you’re watching to confirm it holds.
Resolved	The incident is over.

To work through an incident, post a new update at each stage rather than editing the previous one — that way the timeline tells the full story. The same post title across updates helps readers follow a single incident from start to finish.

Caution

The update body is shown as written — there’s no preview or HTML rendering, so keep formatting simple and avoid pasting anything sensitive.

To remove a post, choose Delete next to it in the timeline.

Post-mortems appear here too

If you publish a post-mortem for an incident on one of the monitors shown on a page, it appears automatically in a Recent post-mortems section on the public page, with a summary and an expandable write-up. You don’t need to do anything extra on the status page itself — publishing the post-mortem is enough.

Email subscribers (double opt-in)

Public pages include a Stay in the loop form so visitors can get an email whenever you post an incident update. Aloft uses double opt-in:

1. A visitor enters their email and submits the form.
2. Aloft sends them a confirmation email with a link.
3. They click the link to confirm. Only confirmed subscribers receive updates.

Every update email includes an unsubscribe link, so subscribers can opt out at any time with one click. Submitting the form again for an address that previously unsubscribed re-sends the confirmation rather than creating a duplicate, so a re-subscribe just needs another confirmation click.

Note

Subscriber emails go out only when you publish a new post, and each post is sent to a given subscriber only once.

RSS feed

Every public page also exposes an RSS feed at /status/<slug>/feed.xml, linked from the page itself. It carries the same incident updates, so visitors who prefer a feed reader over email can follow along there. The feed is disabled while a page is private.