Skip to content
StatusOwlDocs

Create a status page

Create a page, pick a subdomain, choose what it shows, and publish it.

Last updated

A status page is a public page that tells your customers whether your service is working. StatusOwl hosts it, runs the checks behind it, and — if you let it — opens and closes incidents on it without anyone touching a keyboard.

Pages are served from *.statusowl.app, entirely separately from the application you are monitoring. When your origin is down, the page is not.

Create the page

  1. In the dashboard, go to Status Pages → New Page.
  2. Enter a name and pick a subdomain — acme becomes acme.statusowl.app.
  3. Click Create. The page is live at that URL immediately.

Subdomains are validated for format, checked against a reserved-word blocklist, and are globally unique across StatusOwl. If the one you want is taken, the form says so before you submit.

The three switches

Every page has three toggles that save the moment you flip them:

SwitchWhat it does
ActiveOff takes the page offline. Visitors get a 404.
PublicOff makes the page private. See Private pages — it is a 404, not a password.
DefaultMarks this page as the one served at the root of your subdomain.

Multiple pages under one subdomain

An organization can run more than one page. One page is the root, served at acme.statusowl.app. Every other page carries a slug and is served at acme.statusowl.app/{slug} — for example acme.statusowl.app/api and acme.statusowl.app/eu.

Plans cap how many pages you can have: 1 on Free, 3 on Starter, 10 on Growth, unlimited on Scale. The cap is enforced when you click Create, so you find out before you have named anything.

Choose what the page shows

Each page has its own display toggles:

  • Uptime bars — 90 days of daily uptime per service.
  • Response times — the latest response time under each service.
  • Incident history — past incidents below the current state.

Turn any of them off if they are noise for your audience. Details in Uptime history.

Attach the services

Each row on the page is a monitor you attach to it. Open the Components card, click Add Component, and pick a monitor. The row's label and description come from the monitor, so name monitors the way your customers would name the service — "API", not "prod-lb-healthcheck-2". See Services on your page.

Let it update itself

Turn on Auto-create incidents on monitor failure in the page's Settings and pick a default impact. Three consecutive failed checks on an attached monitor opens an incident; the first successful check resolves it. Off by default — see Automatic incidents.

You can still write incidents by hand at any time, and both kinds live on the same timeline. See Incidents.

How fresh the page is

The public page polls for new data every 30 seconds. Polling pauses while the browser tab is hidden and resumes when it comes back. If a poll fails the page keeps showing the last known data rather than blanking out, and an "Updated Xm ago" stamp tells the visitor how old what they are looking at is.

Put it on your own domain

Every plan, including Free, can serve a page from a hostname you own, with a certificate that issues and renews on its own. See Custom domains. The *.statusowl.app URL keeps working alongside it — both serve the same page.

What's next