UptimeRobot alternative: when "the site answers" isn't enough

UptimeRobot alternative: the short answer

UptimeRobot asks one question very often: does this address answer? It sends a request to a URL, a port or a host and looks at the answer. That's exactly what you need to hear about an outage within minutes, and UptimeRobot does it for many endpoints at a low price.

Relvato is a monitoring platform for one website at a time. Uptime is one of its monitors, next to SSL, domain and DNS, cron-job heartbeats, security, visual changes, performance, SEO and, on WordPress and WooCommerce, real checkout, login and form flows. It also re-runs those monitors after the site changes.

So the honest answer depends on the gap you're trying to close. If UptimeRobot's alerts are fine but you keep finding out from customers that something else broke, add Relvato. If you need uptime for 50 servers and APIs, stay with UptimeRobot.

How UptimeRobot decides a site is down

According to UptimeRobot's help centre, an HTTP monitor sends a HEAD request by default and switches to GET on a retry. Any 2xx or 3xx answer counts as up, unless you change the accepted status codes. Before it marks a monitor down, it retries: up to 3 times, 20 seconds apart, after a connection failure, and up to 3 times, 10 seconds apart, after a wrong status code or a keyword mismatch.

On where the requests come from, the same article says that UptimeRobot checks from one region at a time, North America by default, and that paid plans with multi-location rotate through the regions you pick (North America, Europe, Asia and Australia). It adds that there is no quorum: one region's failed, retried check is enough to mark the monitor down. The pricing table separately lists "Re-check from a second data center" on every plan, including Free.

Besides HTTP, UptimeRobot has keyword, ping, port, UDP, API, DNS, SSL, domain-expiry and heartbeat monitors. Each one looks at a single layer: an answer, a string on the page, a certificate, a record.

How Relvato's uptime monitor works

Relvato's uptime monitor requests your homepage (or another page of the site you choose) with a GET from two regions, Europe and the US. No answer, a timeout, a TLS failure, a 5xx, a 404 or a 410 count as down. A 401, 403 or 429 counts as blocked rather than down, because it usually means a firewall is challenging the probe, not that visitors can't reach you. You can set your own accepted status codes, text that must or must not appear, and rules for a JSON answer.

A site is marked down only when every region that's reporting sees it down, or, if only one is reporting, when its last two samples agree. When an outage is confirmed, Relvato alerts you and then takes a screenshot of what visitors see, so you know whether it's an error page, a host's suspension notice or a blank screen.

The probes run every 5 minutes on Free, every minute on Pro and Business and every 30 seconds on Agency. They aren't runs, so they don't count against your plan's runs. They start once the site's ownership is proven, by verifying the domain or installing the free WordPress plugin.

What each catches, and what it misses

UptimeRobot catches outages across many endpoints quickly: a web server that stops answering, a port that closes, a host that stops replying to ping, an API that returns an error. With a keyword monitor it can also catch a page that answers but shows the wrong content. What it isn't built for is anything that takes more than one request: adding to the cart and paying, logging in, sending a form.

That's the class of failure that hurts most on a working website. A plugin update can leave every page returning 200 while the checkout throws an error, the login form loops back to itself or the contact form stops sending email. Our guide on why websites break goes through how that happens.

Relvato covers those flows. With the free plugin on WordPress and WooCommerce, the checkout monitor adds a product to the cart and goes through checkout like a shopper, and other monitors log in through the real form or submit your contact forms and confirm the email went out. It also watches what an uptime service doesn't: cron jobs that stop checking in, visual and structure changes, Core Web Vitals, SEO, accessibility and signs of a hack. What it misses: ping, UDP and API monitors for endpoints that aren't your website, and dozens of separate servers.

Pricing as of October 2026

UptimeRobot (prices as shown to visitors in Europe, in euros): Free costs €0 with 50 monitors at a 5-minute interval, HTTP, keyword, ping and port monitors, 5 basic integrations, 1 basic status page and 3 months of data. Solo costs €10 a month or €108 a year for 10 monitors at a 60-second interval, and adds SSL, domain-expiry, DNS, heartbeat and API monitors, maintenance windows, Slack and 3 status pages on your own domain. A 50-monitor Solo tier costs more. Team adds a 30-second interval, seats, webhooks, Zapier and PagerDuty; Scale adds 15 seconds and 200 or 500 monitors. Check the pricing page for those prices.

Relvato (in US dollars, per account): Free costs $0 for one site, Pro $29 a month ($24 billed yearly) for one site, Business $79 a month for 5 sites and Agency $199 a month for 25 sites. Nearly every monitor is on every plan (custom monitors start on Business); what changes is how often they run, the alert channels and the number of sites.

The two price by different units: UptimeRobot by the number of monitors and the interval, Relvato by the number of sites. Like for like, Free against Free: UptimeRobot gives you 50 monitors with email alerts; Relvato gives you one site with all its monitors, alerts in the app and an email each time a monitor starts failing. Among paid plans, UptimeRobot Solo is clearly cheaper if uptime is all you need. Relvato Pro costs more because it also runs the checkout, security, visual and other monitors and re-runs them after updates.

When to pick which

Stay with UptimeRobot when you monitor many servers, APIs or ports, when you need SMS or voice-call alerts, when you need a status page on a low plan, or when uptime is the whole job. Its Free plan alone covers 50 monitors with email alerts.

Pick Relvato when the site you care about is one where "up" isn't the same as "working": a WooCommerce store, a membership site, a site with forms that bring in leads. It also fits when you want SSL, domain, DNS and heartbeat monitoring without paying for a higher uptime plan, or when you want monitors to re-run on their own after every plugin, theme or core update.

Don't pick Relvato as a pure uptime replacement for a fleet: it has no ping, UDP or API monitors for other endpoints, its Free plan alerts by email only, and public status pages start on Business.

Running them together

The two don't overlap much, so running both is reasonable. Keep UptimeRobot on your servers, APIs and secondary domains, and use Relvato for the main website and what visitors do on it. If you get two alerts for the same outage, that's two confirmations, not a conflict.

If either one keeps reporting a site as down while it works in your browser, look at your firewall or CDN first: bot protection often challenges monitoring requests. Relvato's firewall allowlist guide explains what to allow.

How Relvato does it

On the Free plan you get nearly every monitor for one site. Once the domain is verified, the uptime probes run every 5 minutes, and the other monitors run when you press Run or on a weekly schedule. Alerts appear in the app, plus an email each time a monitor starts failing. Two heartbeats and one TCP port monitor are included.

Pro ($29 a month) probes uptime every minute, runs the other monitors daily, re-runs them after every plugin, theme or core update and every GitHub deploy, and sends alerts by email, Slack, Teams, Discord, Google Chat and webhook. Business ($79 a month) covers 5 sites and adds hourly runs and public status pages. Agency covers 25 sites and probes every 30 seconds.