StatusOwl hosts status pages and monitors services, opening an incident when an attached monitor records three consecutive failed checks. The first successful check then posts a recovery update and resolves the incident. Checks cover HTTP/HTTPS, ping, TCP ports, SSL certificate expiry, domain expiry, and server metrics. Status pages can show uptime history, timestamped incident timelines, scheduled maintenance, branding, and custom domains. Private pages are unlisted and return a 404 to people without the link, but they are not password-protected. Notifications can use email, Slack, Discord, Microsoft Teams, ntfy, or signed webhooks. There are important limits: uptime checks do not currently trigger notifications, and pages have no subscriber form or list to distribute incident updates. The free plan includes one status page, 25 monitors checked every three minutes, two team members, and 30 days of history. StatusOwl is available on the web and through an API.
Who it is for
StatusOwl suits teams that want hosted status pages alongside service checks and automatic incident resolution. Readers who need subscriber email updates or password-protected pages should account for the listed limits.
What is good
- Three failed checks open an incident automatically.
- Checks cover HTTP, ping, TCP, certificates, domains, and metrics.
- Pages include uptime history and incident timelines.
- Custom domains and branding are supported.
- Generic webhooks are signed with HMAC-SHA256.
What to know first
- Uptime checks do not currently notify anyone.
- Pages have no subscriber form or list.
- Private pages are not password-protected.
- Each monitor uses only one checking region.
Verdict
StatusOwl combines monitoring and hosted status pages, with incidents opened and resolved from check results. Its notification and subscriber limits matter if you need alerts or updates sent directly to page followers.
StatusOwl plans and pricing
All plansCompared on status page software
- Free plan
- Yes
- Custom domain
- Yes
- Private status page
- No
- Incident updates
- Yes
- Maintenance scheduling
- Yes
- Component limit
- 50 components
