Docs
One section per part of the product.
Northwind is up.
All 3 monitors are responding, 2 failed checks in the last 24 hours.
Website
Up for 23 h 58 min100% passed
1,438 checks, median 137 ms, all passed
95% under 199 ms
API
Up for 7 h 6 min99.86% passed
1,438 checks, median 204 ms, 2 timeouts
95% under 299 ms
- Timed out2 min, 2 checks
Docs
Up for 23 h 58 min100% passed
1,438 checks, median 94 ms, all passed
95% under 136 ms
What StatOSS is
A status page with the checks built in. You add the things to check, StatOSS requests them every minute from Aarhus and Copenhagen in Denmark, Falkenstein in Germany, Ashburn in the USA, Singapore, and Sydney in Australia in turn, and draws a public page that shows every failed check with its time and reason. When something goes down you are alerted, an incident opens on the page by itself, and subscribers hear about it. Everything the dashboard does is also in the API.
Getting started
- Create an account with an email address, Google, or GitHub.
- Name the status page. The name goes in the headline, as in "Northwind is up." On Free the address is assigned from the name; Hobby and Pro pick their own.
- Add each thing to check. The default is a URL; the type picker offers the rest. "Run a test check" requests the address right away, so a mistyped one does not show up as an outage. Or import what another service already has.
- Share the address. The page is public from the moment it exists, and the first real check runs within a minute.
Free holds 1 monitor on 1 page, checked every 5 minutes. Hobby is $4 a month, Pro $15. The plans page has the whole table.
The sections
- Checks
- HTTP, TCP, DNS, ping, certificate, domain expiry, heartbeat and components. The second opinion, the slow state, groups.
- The page
- Reading the strips, the headline and the error budget. Logo, colours, time zone, and the password.
- Incidents and maintenance
- Opening, updating and resolving. Maintenance windows, templates, and what subscribers hear.
- Alerts
- Email, Slack, Discord, Microsoft Teams, Telegram, PagerDuty, Opsgenie, Pushover, ntfy and your own webhook, with its signature.
- Subscribers
- The subscribe box, per-monitor subscriptions, webhook subscribers and the signed payload.
- Feeds and embeds
- status.json, the badge, RSS and Atom, the widget, llms.txt. Embedding a locked page.
- Addresses and domains
- Assigned addresses, your own domain, one-click DNS.
- Deploy markers
- Marking releases on the response-time chart from CI.
- API
- Keys and scopes, every endpoint with its fields and examples, errors and limits.
- MCP and agents
- The MCP endpoint next to every page and the keyed one over the account.
- Importing
- Moving in from UptimeRobot, Better Stack or Statuspage.
- Teams
- Inviting people, roles, what seats cost on Pro, working in several teams.
- Plans, billing and data
- What each plan holds, how billing works, your data, self-hosting.
Help
The help center searches these docs and takes a message; a person reads it. Our own status page is at statoss.statoss.com, and the changelog says what changed and when.