Status pages

The page your users open when something feels wrong.

A branded page on your own domain, hosted away from your infrastructure and fed by the same checks that watch your services. When those checks start failing the page says so on its own — nobody has to find the login and agree on wording first.

Free forever on one page, with your own domain and SSL included. No credit card.

What your users see

One page. The whole story.

Current state at the top, the history to back it up, and the written record underneath.

https://status.acme.com
Acme Status
status.acme.com
Partial outage
Elevated webhook delivery failures

02:14 UTC · Investigating — opened automatically after three consecutive failed checks.

ServicesUptime · 30 days
API
99.98%
Web app
99.94%
Webhook delivery
99.71%
Dashboard
100.00%
Object storage
99.96%
Upcoming maintenance
Database failover rehearsal

14 Mar · 01:00–03:00 UTC

Past incidents
  • Slow API responses in EU

    02 Mar · resolved in 41m

  • Login errors after deploy

    18 Feb · resolved in 12m

Powered by StatusOwlUpdated 2m ago
Anatomy

Five parts, and you decide which of them show.

Uptime bars, response times and incident history each have their own switch. A page that only needs to say up or down can say just that.

Banner

The one-line answer

The top of the page says what is happening right now. An in-progress maintenance window wins the slot; otherwise the highest-impact open incident; otherwise an automatically-detected outage; otherwise nothing at all.

Services

A row per thing you run

Every monitor you attach to a page becomes a row carrying its current state, its uptime over the last thirty days and its most recent response time.

History

Ninety daily bars

One bar per day per service. Hovering gives the date, the status, that day's uptime percentage, the average response time and how many checks ran.

Incidents

A written record

Investigating, identified, monitoring, resolved — each update timestamped and appended, and every incident gets a permanent page your support team can link to.

Maintenance

Planned work, announced

Upcoming windows list ahead of time, take over the banner while they run, and file themselves under past maintenance with both the scheduled and the actual times.

How your users find out

They open the page, and the page is already right.

Link it from your app footer, your docs, your support macros and your sign-in screen. After that it maintains itself: the incident opens from the checks, and every tab already sitting on the page picks the change up within half a minute.

Refresh behaviour
Poll interval
30 sec
Hidden tab
Paused
Failed poll
Keeps last data
Freshness stamp
Updated Xm ago
Not shipped yet — subscribers

Not built. There is no subscribe form on status pages and no subscriber list in the dashboard. Publishing an incident today updates the page; it does not send anything to anyone. If you need an incident pushed out to a mailing list today, StatusOwl cannot do that for you. Where this sits on the roadmap.

On every plan

The parts that matter are not held back for the paid tiers.

A custom domain is the usual upsell in this category. It is on Free here. What the ladder buys you is more pages, more monitors, faster checks and longer history.

Custom domain with automatic SSL

status.yourcompany.com. Certificates issue and renew with nothing to install.

Private pages

Unlisted pages that return a 404 to anyone without the link. Not password-protected.

Logo, light / dark / auto
Visitor theme toggle
Pages by planFree1Starter3Growth10ScaleUnlimited
How multiple pages work

Your page can be live in a few minutes.

Point a monitor at your service, attach it to a page, and send your users the link. Free forever on one page, with your own domain and SSL.