Uptime Monitoring Tools in 2026: An Honest Comparison

I run one of the tools on this list, so read the whole thing with that in mind. I have tried to be fair about the others, and in a few places I say outright that you should pick them over us. If your situation is one of those, please do.

The market has settled into a few recognisable shapes, and the useful way to compare is by shape first and feature list second. A hobbyist watching two side projects, an agency responsible for forty client domains, and a platform team already living inside Datadog are shopping for different products that happen to share a name.

What every one of them does

Before the differences, the baseline. All of these will request a URL on a schedule and record the status code and response time. All of them alert you through at least email and Slack when a check fails. All of them show incident history and an uptime percentage, warn you before a certificate expires, and publish some kind of status page.

If that covers what you need, the cheapest option that feels pleasant to use is the right answer, and most of this post is not for you. The differences start to matter when you own more than a couple of domains, when the team needs to be paged sensibly, or when the thing that takes you down is something other than the server.

The tools

Barkme

Ours. Built around the domain. You verify a domain once with a TXT record, and from then on every monitor, every certificate, the registration expiry, and the domain's standing on DNS filtering lists and mail blacklists are all checked on your behalf. Checks run as often as every 30 seconds, a failure is confirmed before anyone is alerted, and alerts go out through email, Slack, Telegram, Linear, Trello, or a signed webhook.

The free plan covers 1 domain and 3 monitors at 1-minute checks with email alerts. Founder is $19 a month for 5 domains and 30 monitors with 30-second checks, Slack and Telegram. Pro is $39 for 50 domains, unlimited monitors and every channel. Public status pages come with every plan, on a barkme.dev subdomain, or on your own domain with a paid plan.

Where we are weak: there are no browser or multi-step transaction checks, no on-call scheduling, and no log management. We watch whether a site is reachable and whether its domain is healthy. If you need a synthetic test that logs in and adds an item to a basket, look at Checkly.

UptimeRobot

The default choice for a decade, and still the one most people mean when they say "just put a monitor on it." The free tier is generous in monitor count and stingy on interval, at 5 minutes, which is fine for a personal project and too slow for anything with customers. Paid plans bring 1-minute checks, 30 seconds at the top end, more locations and SMS. Status pages are included. Domain-level checks stop at certificate expiry.

Pick it when you have a lot of low-stakes things to watch and want to spend nothing or nearly nothing.

Better Stack

Started as an uptime tool and grew into an incident management platform. Uptime checks down to 30 seconds, very good status pages, phone call and SMS escalation, on-call schedules, and a log and metrics product alongside. The free tier exists but is small.

Pick it when the hard part of your problem is who gets woken up and in what order, and you want that in the same place as the checks.

Pingdom

One of the oldest names, now part of SolarWinds. Uptime, transaction monitoring and real user monitoring, with pricing that assumes a business and a trial in place of a free tier. Check resolution is 1 minute. It is a competent, slightly dated product with a lot of enterprise customers.

Pick it when procurement already knows SolarWinds, or when real user monitoring matters as much as availability.

StatusCake

Broad coverage at a friendly price: uptime, SSL, domain expiry, page speed and server monitoring. The free tier runs at 5-minute intervals and paid plans go to 30 seconds. Popular with small agencies, particularly around WordPress.

Pick it when you want a bit of everything and a low bill.

Uptime Kuma

Open source and self-hosted, usually in a Docker container on a small VPS. Checks down to 20 seconds, a long list of notification integrations, status pages, and no monthly fee. It is genuinely good software.

The catch is structural. A monitor you host yourself shares a failure domain with the things it watches, unless you are careful to put it somewhere else, and then you have a second server to patch and keep online. Nobody is watching the watcher. For a homelab that is fine. For a business it is a decision you should make on purpose.

Pick it when you would rather run software than pay for it, and you have somewhere independent to run it.

Checkly

Built for developers who want monitoring defined in code. API checks and Playwright browser checks, run from a CLI or Terraform, with intervals as low as 10 seconds. There is a free tier for small projects and the paid plans climb quickly with volume.

Pick it when a passing HTTP check tells you too little and you need to know that the signup flow actually completes.

Oh Dear

From the Laravel world, and well liked there. Uptime at 1-minute intervals, certificate and domain expiry, broken link and mixed content scanning, DNS record change detection, scheduled task monitoring and status pages. No free tier, flat pricing.

Pick it when you maintain a lot of content sites and want to know about broken links and forgotten cron jobs as much as downtime.

Datadog Synthetic Monitoring

Part of a very large platform. API tests down to every 30 seconds, browser tests from many locations, and everything correlated with the traces, logs and metrics you already have in Datadog. Priced accordingly.

Pick it when you are already paying for Datadog. Do not adopt Datadog to get this.

Side by side

Intervals and tiers are as I understand them in September 2026. All of these companies change their plans regularly, so treat the table as a starting point and read the pricing page before you decide.

The check almost nobody runs

Every tool above will tell you when your server stops answering. Only one of them will tell you when your domain has been put on a list.

That matters more than it sounds. A domain can land on a DNS filtering list because a WordPress plugin got compromised, and from that moment a share of your visitors, the ones behind Cloudflare's malware-blocking resolver, Quad9, AdGuard or a corporate filter, get nothing when they type your address. Your server is fine. Your monitor is green. Your support inbox is filling up with "your site is down" from people you cannot reproduce it for. Mail blacklists do the same thing to your email, silently.

Some email-deliverability services check the mail lists, and the big all-in-one monitoring suites sometimes include a blacklist check as a line item. Among the uptime tools in this post, we are the only one running both tracks daily against every verified domain, which is a large part of why Barkme exists. I wrote up how a domain ends up blacklisted and how to get it off separately, including the case that convinced me.

How to actually choose

Count the domains you are responsible for and the people who should be woken up.

One or two domains and one person: UptimeRobot's free tier or Barkme's, whichever you like the look of. Neither will cost you anything.

A handful of domains and a small team: Barkme, StatusCake or Better Stack. Barkme if the domains themselves are the asset and you want expiry and reputation watched. Better Stack if you need escalation policies. StatusCake if you want page speed on the same bill.

Many client sites: Oh Dear or Barkme, depending on whether broken links or blacklists worry you more.

Flows that must complete end to end: Checkly.

An existing observability platform: use its synthetics, and keep one cheap independent monitor pointed at the platform's own login page. Everything fails eventually, including the thing that tells you about failures.