StatOSS compared with Instatus
Instatus is a polished status page with monitoring added on and a generous free tier. StatOSS starts from the monitoring, shows every failed check on the page, and is open source at the core.
Northwind is up.
All 2 monitors are responding, 5 failed checks in the last 24 hours.
API
Up for 6 h 51 min99.65% passed
1,438 checks, median 204 ms, 5 timeouts
95% under 299 ms
- Timed out5 min, 5 checks
Website
Up for 23 h 58 min100% passed
1,438 checks, median 137 ms, all passed
95% under 199 ms
Side by side
| StatOSS | Instatus | |
|---|---|---|
| Free tier | 1 page, 1 monitor, checks every 5 minutes, 7 days of history, email alerts | 15 monitors, checks every 2 minutes, email alerts, 5 team members, 200 subscribers, public page only, no custom domain |
| Cheapest paid plan | Hobby $4 a month: 10 monitors, every minute, 90 days. Pro $15: 100 monitors across 10 pages, a year, your own domain | Pro, $20 a month or $15 billed yearly by Capterra's and Hyperping's September 2026 listings (Instatus's page does not show the figure): 50 monitors, 30-second checks, SMS alerts, 50 team members, a custom domain, 5,000 subscribers, public pages only; private pages are on Business |
| Check locations | Aarhus and Copenhagen in Denmark, Falkenstein in Germany, Ashburn in the USA, Singapore, and Sydney in Australia, the regions in turn, with every failure checked again from every region before it counts | United States, Canada, Europe and Asia in round robin, one location per check |
| What the page shows | Response-time bars with a mark for every failed check, each failure with its time and reason | 90-day daily uptime bars per component, incidents |
| Monitor types | HTTP with keyword, TCP, DNS, ping, certificate, domain expiry, heartbeat, component | HTTP with status, body, JSON and header assertions, keyword, heartbeat, ping, TCP, UDP, DNS, SSL |
| Subscriber channels | Email and webhook on Pro; RSS and Atom on every page | Email, SMS through your own provider, webhook, Slack, Teams, Discord, Google Chat, X, RSS |
| Open source | The core is MIT licensed and runs on your own box | No |
Facts about the other product were read from its own site on 29 September 2026. Prices and limits change; check theirs before deciding, and tell [email protected] if something here is out of date.
What StatOSS does differently
Most uptime pages show a row of green squares, one per day, and a percentage. A five-minute outage at 3 a.m. becomes a square that is still green and a figure that still says 99.99%. StatOSS draws a strip per monitor where every bar is one check, its height the response time, amber for a timeout and red for any other failure, and groups the failed checks into entries with the time and the reason. The mark stays visible for the whole range. A customer who was refused at 3 a.m. finds the moment on the page, and so do you.
Before a failure counts, a second server on another network repeats the check, and only a failure both see goes on the record; two of those in a row make an outage. The response time of every check is kept, and a slow threshold turns a sluggish service into its own state with its own alert. The core is open source under MIT, so the page you get from the hosted service is the page you can run yourself.
When Instatus is the better pick
Fifteen free monitors against our one, subscribers on the free tier, SMS on Pro, subscriber channels into Slack, Teams and Discord, and checks from four continents: if those are what you need, Instatus has them. Instatus also takes status from other monitoring tools, which suits a team that already has Datadog or Checkly and wants a page in front of it.
Where StatOSS fits: the failed checks on the page rather than daily bars, every failure checked again before it counts, from every region on Hobby and Pro, a flat $4 a month for the ten-monitor case, and a core you can run yourself. Any CSV with a URL column imports.