StatOSS compared with UptimeRobot
UptimeRobot is the biggest name in cheap uptime monitoring, with a free tier for non-commercial use. StatOSS is smaller, open source at the core, and built around a status page that shows every failed check.
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 | UptimeRobot | |
|---|---|---|
| Free tier | 1 page, 1 monitor, checks every 5 minutes, 7 days of history, email alerts | For non-commercial use only since July 2025: 50 monitors, checks every 5 minutes, 3 months of data, 1 status page without a custom domain, up to 5 integrations, no login seats |
| 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 | Solo, €10 a month or €9 billed annually: 10 or 50 monitors, checks every minute, 3 status pages with your own domain, 12 months of data, 10 to 20 SMS or voice credits |
| Failure confirmation | A second server on another network repeats every failed check; two confirmed failures in a row make an outage | A verification check from other servers in the same region; checking from several regions is paid |
| What the status page shows | Response-time bars with a mark for every failed check, each failure with its time and reason, incidents, an error budget | Uptime bars and percentages for 24 hours to 90 days, response times, an incident timeline |
| Monitor types | HTTP with keyword, TCP, DNS, ping, certificate, domain expiry, heartbeat, component | HTTP, keyword, ping, port, DNS, UDP, heartbeat, API; SSL and domain expiry on every plan |
| Alerts | Email on every plan; Slack, Discord, Microsoft Teams, Telegram, PagerDuty, Opsgenie, Pushover, ntfy and a signed webhook on Hobby and Pro. No SMS | Email, push, Slack, Teams, Discord, Telegram, PagerDuty, webhooks and more; SMS and voice by credits bought once |
| 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 UptimeRobot is the better pick
If you want to watch fifty things for nothing on a non-commercial project, UptimeRobot's free tier holds them; StatOSS Free holds one monitor, and watching more costs $4 a month. If you need SMS or a phone call rather than a push through Pushover, ntfy, PagerDuty or Opsgenie, UptimeRobot sells the credits. It also has integrations for far more tools.
Moving over
The import screen under Monitors reads an UptimeRobot export: paste it, see what each row becomes, tick what to bring. The import page has the steps. Your history does not come with it, since it is a different kind of record; the strips fill from the first check.