Free uptime monitoring for a small site: what UptimeRobot's free plan really covers

Martin Kraus — Tue, 27 Oct 2026 13:16:23 +0000

If you run a side project, a blog or a small client site, you probably want to know when it goes down before your users do. I set up UptimeRobot's free plan for a permanent monitor on my own site and checked which features are really usable without paying. Here is the developer-relevant summary.

What the free plan gives you

50 monitors at a 5-minute interval. That is a lot for a single project. I use 2.
Monitor types: HTTP(S), keyword, ping and port. Cron/heartbeat, DNS, API and UDP monitors start with the paid Solo plan.
One public status page on an UptimeRobot subdomain. A custom domain (e.g. status.example.com) is paid.
Full REST API access with main, read-only and monitor-specific keys, plus an MCP connector so AI assistants can query your monitors.
Free alert channels: email, mobile apps, Discord, Google Chat, Splunk and Pushbullet/Pushover. Slack, Telegram, webhooks, MS Teams, Zapier and PagerDuty are on paid plans.

According to the current terms of service (checked October 2026), the free plan may also be used commercially. Older help articles still say otherwise, so check the terms that apply when you sign up.

Setup: under two minutes

"Create your first monitor" leads straight to the form. URL, type (HTTP/S) and a friendly name were filled in, and the account email was preselected as alert contact. The first check came in after one to two minutes.

Add a keyword monitor, not just a status check

A plain HTTP check only tells you that the server answered with 200. It does not tell you that the page was delivered completely. A keyword monitor fixes that: it opens an incident when a defined string is missing from the response. I use a text that appears near the end of every page, so a truncated or broken render triggers an alert even though the status code looks fine.

This also works as a lightweight check for pages with forms: you can verify that the page is reachable and that, for example, the submit button label is delivered. Actually submitting a form is not possible with the free monitor types.

Where the paywall starts

Things I ran into during the test:

SSL and domain expiry checks are visible in the edit form, but switching them on opens an upgrade dialog. Careful: the offered trial renews into a paid annual subscription unless you cancel in time.
Maintenance windows are not available for free, so planned downtime produces false alerts.
Slow response alerts and multi-location checks are paid.
Shorter intervals: 60 s (Solo), 30 s (Team), 15 s (Scale).

When it is not the right tool

Incident management stays basic on every plan. If you need on-call schedules and escalation, a tool like Better Stack fits better. If you want no monitor cap and full data ownership and already run a server, the self-hosted, open-source Uptime Kuma is the alternative.

Privacy note for EU projects

UptimeRobot s. r. o. is based in Bratislava (Slovakia). According to its terms, data is processed under the GDPR and a data processing agreement is available on request. If you store alert contacts of other people, request the DPA before production use. This is not legal advice.

Bottom line

For a single site or a few side projects, the free plan covers basic monitoring indefinitely: an HTTP check plus a keyword check, a status page and API access. Budget for Solo once you need SSL expiry warnings, maintenance windows or intervals under five minutes.

I run delavo.de, where I test AI and SaaS tools hands-on. The full UptimeRobot review with screenshots of every step and a detailed rating was first published there. This summary was written with an AI agent based on that original hands-on review.

DEV Community: Martin Kraus