For developers and ops

The quiet failures are the expensive ones.

Missed cron jobs, full disks and changed DNS records. Watch them next to your uptime checks, and manage it all from code.

14-day free trial · No credit card required

//_01 What keeps you up

What breaks without an error page

The backup stopped running weeks ago

Heartbeats: your job sends one request when it succeeds, and you get an alert when it does not.

The disk filled up overnight

Server monitoring for CPU, load, RAM, swap, disk, network and reboots on Linux, Windows and macOS, with your own thresholds.

A DNS record changed without a ticket

DNS monitors for A, AAAA, CNAME, MX, NS, SOA, TXT and CAA with history and change alerts.

Monitoring drifts from what is deployed

A REST API for monitors, servers, heartbeats, domains, alert channels and status pages. Keep it in your pipeline.

//_02 Features

The checks behind the checks

Cron job monitoring

Heartbeats that alert you when a scheduled job does not run.

Learn more

Server monitoring

CPU, RAM, disk, network and reboots on Linux, Windows and macOS.

Learn more

DNS monitoring

History and alerts when A, MX, NS, TXT or CAA records change.

Learn more

REST API

Manage monitors, servers, heartbeats and status pages from code.

Learn more

API monitoring

Custom methods, headers, bodies and response validation for every endpoint.

Learn more

Alerts and notifications

Email, Slack, Discord, Telegram, Teams and webhooks, with recovery notices.

Learn more

Monitoring for developers and operations teams

Uptime checks catch the loud failures. The ones that hurt most are quiet: a cron job that stopped after a server move, logs that fill a disk over a week, an MX record changed during a migration. Uptimecheck puts those checks in the same account as your uptime monitors.

Heartbeats for scheduled work

Append a request to your backup, import or billing job. If it does not arrive on schedule, you get an alert. Read how to monitor cron jobs for patterns that avoid false alarms.

Server resources with thresholds

Track CPU, load over 1, 5 and 15 minutes, RAM, swap, disk, network and reboots. Set thresholds per server so the alert comes before the outage.

DNS change history

Get alerted the moment a record changes, with the old and new value kept in history. Useful for audits, rollbacks and spotting a hijacked domain. See detecting hijacked DNS records.

Automate everything

A setup in an afternoon

  • Add a heartbeat to each scheduled job, starting with backups.
  • Install server monitoring on the machines that matter and set disk and load thresholds.
  • Add DNS monitors for your main domains: NS, A, MX and TXT.
  • Route alerts to the team channel, and a Telegram message only for what must wake someone.
  • Move the setup into code with the API once it works.

The result is monitoring that catches the quiet failures as reliably as the loud ones, in the same tool and the same alert channel. When something goes wrong at night, the person on call sees the disk, the missed job and the failing check side by side.

No agents to babysit for most checks

Uptime, API, heartbeat, SSL, domain and DNS checks run from Uptimecheck itself or through a single HTTP request from your job, so there is nothing to install for most of your monitoring. Only server resource monitoring needs access to the machine it measures.

The REST API covers monitors, DNS monitors, servers, heartbeats, domains, alert channels, status pages and statistics. Create monitors from your deploy step, route alerts to webhooks, and pull statistics into your own dashboards. API access is included on Professional and Business; see the pricing page.

“UptimeCheck makes monitoring incredibly easy for developers like us. All we have to do is enter our website's URLs, choose the channels we want notifications delivered on (email, SMS, Slack, Telegram), and we're done!”

Rasmus Danielsson

Developer

Guides for developers and ops

All guides

Guides 5 min read

How to Monitor Cron Jobs with Heartbeats

Cron jobs fail silently. A heartbeat monitor alerts you when a scheduled job does not check in on time. How heartbeats work, how to add one to a crontab and which settings to choose.

Read

Fixed price. Everything included.

Start

For personal projects and small sites

€9 / month

Billed yearly

Start free trial
  • 15 monitors, checked every minute
  • 10 heartbeats and 10 domains
  • 10 status pages
  • Email, Slack, Discord, Telegram, Teams and webhooks
  • Weekly and monthly email reports
  • 6 months of history

Professional

Most popular

For growing teams and agencies

€29 / month

Billed yearly

Start free trial
  • 100 monitors, checked every minute
  • 50 heartbeats and 50 domains
  • 25 status pages
  • REST API access
  • 10 teams with 5 members each
  • Custom CSS and JS, 1 year of history

Business

For teams with many sites and clients

€69 / month

Billed yearly

Start free trial
  • 250 monitors, checked every minute
  • 150 heartbeats and 150 domains
  • 250 status pages
  • REST API and white label
  • Unlimited teams with 10 members each
  • 2 years of history

14-day free trial · No credit card required

Compare all features

Common questions

How do heartbeats work?

Your job sends a GET or POST request to its heartbeat URL when it runs. If the request does not arrive on schedule, Uptimecheck alerts you.

Which servers can I monitor?

Linux, Windows and macOS servers, with CPU, load, RAM, swap, disk, network and reboot tracking.

Which DNS records can be monitored?

A, AAAA, CNAME, MX, NS, SOA, TXT and CAA, with history and alerts on change.

Is there an API?

Yes. A REST API on Professional and Business for monitors, DNS monitors, servers, heartbeats, domains, alert channels, status pages and statistics.

Downtime is obsolete.

Set up your first monitor in under a minute and know before your customers do.

14-day free trial · No credit card required

Start free trial