UptimeRobot is the default. It has been around longer than almost anyone, it is reliable, and for a lot of people it is the right answer. If you are reading a comparison page, you probably want to know where it stops — so start with where it does not.
What UptimeRobot does better
Its free plan is far bigger than ours. 50 monitors at a 5-minute interval, with three months of history and a status page, against our 10 monitors at 3 minutes and 30 days. If you have 40 websites and you only need to know within five minutes, UptimeRobot's free tier is the better deal and we are not going to pretend otherwise.
At around 100 monitors it is cheaper. Their Team plan is €35/month for 100 monitors at a 30-second interval. To check every 30 seconds with us you need Business at €79/month — which brings 250 monitors, but if you only wanted 100 you are paying for headroom you do not use.
It has a longer track record. More years, more integrations built against it, more people who already know it.
Where we differ
UptimeRobot tells you when something is down. It does not show you that the telling worked. Ours does, and it is the whole reason the product exists:
- Every alert is written to an outbox before it is sent, then retried for about fifty minutes.
A restart mid-incident does not lose it.
- Once a week a real test event goes through every channel you have configured, and you are told
which ones failed. Broken webhooks are found on a Tuesday, not during an outage.
- If the alert pipeline is degraded, the dashboard says "Alerts are at risk" instead of looking calm.
- If the checker itself stops,
/api/healthreturns 503 so an outside watchdog can page you, and
your status page says monitoring has stopped rather than showing stale green.
The other difference is what we can check. Fifteen types, including several nobody else speaks: Minecraft server list ping, Steam/Source A2S queries, FiveM, Discord bot presence through a real gateway connection, Postgres/MySQL/Redis with a real authenticated query, and mail blocklists.
Side by side
| UptimeRobot | Uplance | |
|---|---|---|
| Free plan | 50 monitors, 5 min, 3 months history | 10 monitors, 3 min, 30 days history |
| Entry paid plan | Solo, €9/mo — 50 monitors, 60 s | Pro, €19/mo — 50 monitors, 60 s |
| 30-second checks | Team, €35/mo — 100 monitors | Business, €79/mo — 250 monitors |
| Fastest interval | 15 s on Scale (€65/mo) | 30 s on Business; 20 s on request |
| Game server checks | No | Minecraft, Source/Steam, FiveM |
| Discord bot presence | No | Yes, via a real gateway connection |
| Database checks | No | Postgres, MySQL/MariaDB, Redis |
| Mail blocklist checks | No | Five blocklists |
| Proof alerts were delivered | No | Outbox, retry ladder, weekly drill |
| Alerts from your own Discord bot | No | Yes — your name and avatar |
Which one to pick
Stay on UptimeRobot if you monitor a lot of plain websites, five-minute granularity is fine, and the free tier covers you. That is a real answer and it costs you nothing.
Switch if you run something UptimeRobot cannot see — a game server, a Discord bot, a database — or if you have ever had an outage where the alert did not reach anyone and you could not find out why. The second one is the reason people move.
You can test the difference on the free plan: configure your channels, then look at the weekly drill result. That number is the thing no feature table can show you.