Applies to: Uptime Kuma 2.5.9 (Docker image, tested) and UptimeRobot (features from uptimerobot.com at the time of writing)

Uptime Kuma is free, open-source monitoring software (MIT licence) that you run on your own server, so the checks come from that server and all the data stays with you. UptimeRobot is a hosted service: you sign up, add monitors in their dashboard, and the checks run from their network. Pick Uptime Kuma when you want control, unlimited monitors and private data; pick UptimeRobot when you want checks from several places with nothing to maintain. You can also use both together.

For a wider list of monitoring tools (Netdata, Zabbix, Prometheus and others), see Server Monitoring Software for Linux: Tools Compared. This article only compares these two uptime checkers.

What each one does

Uptime Kuma sends a check on a schedule and alerts you when it fails. In version 2.5.9 the Monitor Type list includes HTTP(s), HTTP(s) - Keyword, HTTP(s) - Json Query, TCP Port, Ping, DNS, Docker Container, Push (for cron jobs and backups that report in), databases such as MySQL/MariaDB and PostgreSQL, SMTP, game servers and more. A new monitor checks every 60 seconds by default. It also has public status pages, maintenance windows and certificate expiry warnings.

UptimeRobot, according to its website, monitors HTTP(s) pages, keywords, ping, ports, cron jobs (heartbeats), DNS records, SSL certificates and domain expiry, and offers status pages, maintenance windows and alerts by email, SMS, voice call, app push and chat tools such as Slack and Telegram.

Where the checks run from

  • Uptime Kuma: from the one server or VPS where you installed it. Every check uses that server's network, DNS resolver and route to the internet.
  • UptimeRobot: from their data centres. According to UptimeRobot, when a check fails it is re-checked from a different data centre in the same region before an incident is opened, on every plan including Free. Paid plans add multi-location monitoring from up to four regions.

Data ownership and privacy

  • Uptime Kuma keeps everything in its data folder on your server (/app/data inside the official container: the kuma.db database, uploads and settings). Nothing is sent to a third party unless you add a notification channel that uses one. You decide how long history is kept and you make your own backups.
  • UptimeRobot stores your monitors, logs and contact details on its platform. Its pricing page lists log retention of 3 months on Free and 12 to 24 months on paid plans.
  • Uptime Kuma can also check things that are not public: internal IP addresses, a database port bound to a private network, or services over a VPN. A hosted service can only reach what is open to the internet.

Limits and cost model

  • Uptime Kuma: no licence fee and no monitor limit in the software. The real limits are the server's CPU, memory and network, and your time to update it and back it up.
  • UptimeRobot: according to its pricing page, the Free plan has 50 monitors at a 5-minute interval and one status page; paid plans shorten the interval (down to 60, 30 or 15 seconds depending on the plan) and add features. Check their site for current plans.

The weak spot of a single self-hosted location

One Uptime Kuma server is one point of view. Keep these limits in mind:

  1. If the monitoring server is down, nothing alerts you. Silence looks the same as "everything is fine".
  2. Shared fate. If Uptime Kuma runs in the same data centre, or worse on the same server, as the sites it watches, a network or power problem takes out both at once.
  3. One route only. A site can be reachable from your monitor but not from visitors in another country, or the other way round. A routing problem near the monitor can also cause false alarms.
  4. Its own DNS resolver. A DNS change can look fine from the monitor while other resolvers still serve old or broken answers.

Ways to reduce this:

  • Run Uptime Kuma on a separate VPS in a different location from the servers it watches.
  • Set Retries on each monitor, so one lost packet does not page anyone.
  • Use the Globalping - Access global monitoring probes monitor type. It asks probes on the public Globalping network to run a Ping, HTTP(s) or DNS check from a Location you choose, such as a continent, country or city. In our test a Globalping HTTP(s) check of example.com from Europe worked straight away; Settings > General has a Globalping API Token field if you need one.
  • Watch the watcher: point an outside check at your Uptime Kuma status page.

When to use both

A practical setup for a business site:

  1. Uptime Kuma does the detailed work: every website, port, database, cron job and certificate, at short intervals, plus private services and a public status page on your own domain.
  2. A free hosted monitor (UptimeRobot or similar) checks your two or three most important URLs and your Uptime Kuma address from outside. If your monitoring server goes down, you still hear about it.
  3. Send both to the same alert channel so the team sees one stream of alerts.

Quick decision guide

  • You need private network checks, many monitors or full control of the data: Uptime Kuma.
  • You have no server to run it on and want multi-region checks with nothing to maintain: a hosted service.
  • Uptime really matters to your business: both, with the hosted one watching Uptime Kuma itself.

Running Uptime Kuma with Ucartz

If you want root access and full control, an Uptime Kuma VPS comes with Uptime Kuma installed by our engineers, and you can add other tools such as a VPN to reach private networks. If you would rather not run the server yourself, managed Uptime Kuma hosting gives you your own private instance that we host, update and secure, with a status page on your own domain. Either way, host it in a different location from the servers it watches.

Official documentation: Uptime Kuma on GitHub.

Related services

KVM VPS hosting

NVMe SSD and full root access, with Free Basic Managed Support.

Unmanaged dedicated servers

full root access and free IPMI KVM, with Free Basic Managed Support.

Managed dedicated servers

our engineers look after the server for you, from $135 a month.

Was this answer helpful?

Still stuck? Open a ticket