When it breaks,
your users
already know.
StatusOwl watches your services and posts the incident to your status page the moment checks start failing. Nobody has to find the login, agree on wording, and publish an update while the pager is going off.
Free forever on one page — with your own domain and SSL included.
Acme Status
Uptime · 30 days
02:14 UTC — Opened automatically after 3 consecutive failed checks.
Updated 30s ago
The page writes the first update for you.
Most status pages are only as fast as the person who remembers to update them. StatusOwl opens the incident from the checks themselves, so the page is already correct when your users get there.
Three checks fail in a row
A single blip does not post an incident. Three consecutive failures on a monitor attached to your page does.
The incident opens itself
StatusOwl creates the incident at the impact level you configured, seeds an automatically-detected first update, and puts the banner on your page. Duplicates are suppressed.
Recovery closes it
On the first successful check, StatusOwl posts a recovery update and resolves the incident — with the whole timeline preserved.
Everything your users go looking for.
Current state at a glance, the history to back it up, and a written record of what happened.
90 days of uptime
A daily bar per service, colour-coded and hoverable, with the exact uptime percentage, average response time and check count for that day.
Read moreIncident timelines
Investigating, identified, monitoring, resolved — each with its own timestamped update and a permanent public page.
Read moreScheduled maintenance
Announce planned work in advance. The window takes over the banner while it is running and files itself into history when it is done.
Read moreYour own domain
status.yourcompany.com with automatic SSL. Staged DNS instructions, verified live as you go — nothing to install or renew.
Read moreYour brand
Logo, light, dark or auto, and a theme toggle for visitors. The page remembers what each visitor chose.
Read morePrivate pages
Unlisted pages for internal services. Public pages for customers. Both on the same account.
Read moreMonitoring is how the page keeps itself honest.
You do not have to wire up a separate monitoring product and hope the two agree. The checks that decide whether your page says operational are the same checks that open the incident.
- Method
- GET
- Expected status
- 200, 201
- Interval
- 30 sec
- Timeout
- 10 sec
- Follow redirects
- Yes
- Last response
- 142 ms
A status page company should be the last to oversell.
So here is the current, unflattering list. If one of these is a dealbreaker for you, better you find out on this page than three weeks in.
Status page subscribers
Building nowNot 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.
Uptime alerts to your team
Building nowThe six notification channels are built, tested and in production — but the only thing that currently triggers them is a Watch Owl server-metric alert rule. A failing HTTP, ping or TCP check opens an incident on your status page and notifies nobody. This is the single biggest gap in the product and it is what we are working on right now.
Priced per status page, not per subscriber.
The incumbent charges by how many people are watching. We think that is a tax on being useful during an outage.
One page for a side project, an open-source tool, or a first product.
- 1 status page
- Your own domain, with SSL
- 25 monitors, checked every 3 min
- Incidents open automatically
- 30 days of history
A team running one product that needs a page customers actually trust.
- 3 status pages
- 100 monitors, checked every 60 sec
- 8 team members
- 90 days of history
- 1 dedicated checking node
Several services, several audiences, and internal pages alongside public ones.
- 10 status pages
- 300 monitors, checked every 30 sec
- 25 team members
- 180 days of history
- 3 dedicated checking nodes
Agencies, platforms and enterprises running a page per customer or per region.
- Unlimited status pages
- 1,000 monitors, checked every 30 sec
- Unlimited team members
- 365 days of history
- Unlimited dedicated nodes
Separate from your stack
Your status page runs on our infrastructure, not yours. When your origin is down, the page that says so is not.
Redundant by default
Status pages run multi-instance behind Cloudflare, with certificates issued and renewed automatically for every custom domain.
Live without refreshing
Pages poll for fresh data every 30 seconds, pause while the tab is hidden, and keep the last known state if a poll fails.
Scoped to your org
Every query is scoped by organisation and every membership checked before a read or a write.
Put up a status page today.
Free forever on one page, with your own domain and automatic SSL. No credit card, no trial clock.