Create and publish a status page

Create the page

1. Go to Status Pages in the sidebar and click Add Status Page.
2. Give it a title and a slug. The slug becomes part of the public URL (https://<slug>.status.uptimehunt.io) — lowercase letters, numbers, and hyphens only, starting and ending with a letter or number. Pick it carefully: it can't be changed later.
3. Save. New pages start unlisted — nothing is served publicly yet.

Add components

Components are what visitors actually see — a status page never shows a service or cron job you haven't explicitly added, and a component's public name never has to match any monitor's internal name.

1. Open the page and go to its Components tab.
2. Click + Component, then pick one or more monitors for it from the searchable list of your services and cron/heartbeat monitors. A monitor already used by another component on this page won't show up — it can only back one component per page, so a single outage is never double-counted across two rows.
3. Set the component's display name and, optionally, its group (see below).
4. Save. The whole layout — every group and component — saves as one ordered set, so reordering or moving several things at once is a single action.

A component isn't limited to one monitor. Bundle everything that makes up the same user-facing thing — a "Website" component watched by both an HTTP check and a DNS check, a "Nightly Backups" component watched by a cron job and the upload it triggers — instead of showing every underlying check as its own row. Add or remove a component's monitors any time from its ⋮ menu → Edit monitors….

What a multi-monitor component shows

• Live status is worst-of. A component shows the worst state across its monitors — down outranks degraded, which outranks maintenance, which outranks operational — computed after each monitor's own maintenance windows are applied first. A maintenance window covering one monitor never masks a real outage on another monitor in the same component.
• History and uptime are merged, and deliberately conservative. A day on the 90-day strip is marked down or degraded if any one of the component's monitors was down or degraded that day, and each monitor's downtime minutes are added together (capped at a full day). Overlapping outages on different monitors can therefore double-count minutes, which means the displayed uptime percentage is a lower bound — it can undercount how good things actually were, but it never overstates them.

Groups

Groups are headings that organize components on the public page — "Core Platform", "Game Infrastructure", whatever makes sense for your service. A page's ungrouped components always show first, above any named group.

1. In the Components tab, click + Add group and name it.
2. Move a component into a group from its ⋮ menu → Move to group — choose an existing group or create a new one on the spot.
3. Reorder groups with the arrows next to the group heading; reorder components within a group the same way.
4. Rename a group any time by editing its heading inline — its components stay exactly where they are.
5. Deleting a group ungroups its components; it never deletes them. They fall back to the top-level ungrouped section.

Each component shows its live status, a 90-day history strip that packs densely to fit more information at a glance, and an uptime percentage computed the same honest way everywhere else in UptimeHunt: days with no data at all are excluded, never counted as either up or down.

Preview before publishing

While a page is unlisted, its public URL serves nothing (a 404) — that's the whole point of unlisted: nobody can stumble onto it. Preview exactly what visitors will see from the page editor itself, which renders the same document that goes public the moment you publish.

Publish

1. Go to the page's Settings tab.
2. Flip Visibility to Published. You'll be asked to confirm — this makes the page public at its URL immediately.
3. The public URL, badge URL, and feed URLs are all shown on this tab with a copy button.

Publishing — and any later edit — is picked up automatically; there's no separate "rebuild" step. Flip a page back to Unlisted at any time to pull it offline again; its URL then 404s until you republish.

Related Documentation

• Publish incident updates
• Branding
• Maintenance windows
• Badges and feeds
• Cron Job Monitoring