UptimeRobot in depth: website, server and API monitoring

UptimeRobot is an external monitoring service that regularly checks whether websites, servers, APIs and other services are reachable and, depending on the monitor type, behaving as expected.

At a glance

UptimeRobot is most interesting when you want external availability and reachability checks with relatively little setup. The free plan is already substantial for many small projects; shorter intervals, team features and advanced status/alert capabilities are where paid plans become relevant.

What is UptimeRobot?

The basic idea is simple: instead of relying on the server itself to tell you that it is reachable, an independent service checks it from outside your network. Depending on the configuration, UptimeRobot performs recurring checks and generates incidents and notifications when failures are confirmed.

Monitor types

HTTP(S) monitoring

An HTTP monitor is the classic website check. UptimeRobot requests the configured URL regularly and evaluates the response. This is excellent for answering “Can my web server be reached from outside?”, but it does not automatically answer “Is my application functionally correct?”

Ping is not the same as website monitoring

A server can answer ICMP pings while Apache/Nginx, PHP, a database or the application itself is broken. Ping is therefore a host/network check, not a complete application test.

API monitoring: one level deeper

API monitoring goes beyond simple reachability. According to the current documentation, UptimeRobot can inspect JSON responses and validate concrete fields using assertions. Supported request methods include GET, POST, PUT, PATCH, DELETE, HEAD and OPTIONS, with Basic, Digest and Bearer authentication available.

{
  "status": "healthy",
  "data": { "count": 42 }
}

An assertion can turn this into a condition such as “$.status equals healthy”.

Heartbeat / cron jobs

Here the logic is reversed: UptimeRobot provides a unique endpoint and expects your job to call it regularly. If the expected request does not arrive, the monitor is considered down. This is useful for backups, imports, reports and other scheduled jobs.

*/5 * * * * wget --spider "https://heartbeat.uptimerobot.com/YOUR-ENDPOINT"

Example pattern based on the official documentation; the actual heartbeat endpoint is generated for each monitor.

SSL and domain expiration monitoring

For HTTPS monitors, UptimeRobot can detect SSL errors and warn about certificate expiration. According to the documentation, certificate expiration is checked once every 24 hours, with default reminders at 30, 14, 7 and 0 days.

Notifications & webhooks

Current notification options include email, SMS, voice calls, mobile push and integrations such as Slack, Microsoft Teams and webhooks. Contacts must be assigned to the relevant monitors for notifications to be delivered.

Webhooks are especially useful in IT environments: UptimeRobot can send HTTP requests to your own endpoint for down, up or SSL/domain-expiry events. The documentation supports JSON, POST parameters, query strings, custom POST bodies and custom headers.

Status pages

Status Pages can expose monitored services publicly. Current documentation lists one status page on the free plan; additional branding, custom domains, translations and white-label capabilities depend on the plan.

Plans: what do you get for free?

The current pricing page lists 50 monitors and 5-minute intervals for Free; API and UDP monitoring are also listed under Free, while SSL/domain expiration monitoring is shown as paid-only. Solo currently starts at $9/month, Team at $34/month and Enterprise at $69/month on monthly billing. Annual billing is shown at lower effective prices.

Which monitor should I use?

What UptimeRobot does not guarantee

An “UP” status always means that the configured test passed. It is not automatically a full end-to-end test of your application. Complex systems should use multiple complementary checks.

Our verdict

UptimeRobot is not a full observability platform, and that is part of its strength: the entry barrier is low for many websites, small servers, APIs and scheduled jobs. The combination of reachability checks, API assertions, heartbeats and webhooks is particularly useful. For complex teams that need logs, metrics, traces and deeper incident management, we would also consider platforms such as Better Stack.

Sources & further documentation