OnSumoTools

Healthchecks.io

Allowed use

Listens for pings from scheduled jobs and sends an alert when an expected ping arrives late.

Visit official site

Pricing summary

$0/ month

Free plan: Hobbyist

Pricing checked

Product fit

Good fit for

  • Cron jobs and scheduled tasks
  • Backup and data sync checks
  • Periodic processes with known schedules

Not built for

  • Website uptime probes
  • Application performance metrics
  • Log aggregation

Feature matrix

FeatureHealthchecks.io
Cron schedule supportIncluded
Grace periodsIncluded
Job ping logsIncluded
Projects and teamsIncluded
Start and failure signalsIncluded

Listed integrations

  • Email
  • Microsoft Teams
  • PagerDuty
  • Slack
  • SMS
  • Webhooks

Sources checked

A different kind of monitor

Healthchecks.io doesn't poll your website. It listens. Your scheduled job sends it a ping when it finishes, and if an expected ping arrives late or not at all, it sends an alert. This is sometimes called a dead man's switch.

That's useful because scheduled jobs fail quietly. A backup stops running and nothing complains until you need to restore it.

Who it suits

The record lists cron jobs and scheduled tasks, backup and data sync checks, and periodic processes with known schedules. If you can say "this should happen every night at 2", it fits.

You tell it the schedule, add a grace period for slow runs, and add one line to your script that calls the ping URL on success. Start and failure signals let you track how long a job took and report an error right away.

Who should look elsewhere

The record says it isn't for website uptime probes, application performance metrics or log aggregation. It won't notice that your homepage is down unless a job of yours checks it and pings in.

For public site checks, see UptimeRobot in the comparison.

Features and integrations

Listed features are cron schedule support, grace periods, job ping logs, projects and teams, and start and failure signals. The ping logs help when you need to see exactly when a job last ran.

Alerts can go to email, Microsoft Teams, PagerDuty, Slack, SMS and webhooks.

Pricing

The record shows a free plan named Hobbyist with a starting price of zero dollars a month, last verified on July 18, 2026. Limits differ by plan and can change, so confirm them on the vendor's page. No affiliate link is attached to this record.

Setting up a first check

The flow is short. Create a check and give it a name that you'll recognise at 2 a.m., like nightly-db-backup. Set the schedule to match your cron entry, then pick a grace period. The grace period is how long to wait after the expected time before sounding the alarm.

The tool gives you a unique ping URL. Add one line to the end of your script that calls it when the job succeeds. That's often a single curl command. Run the job once and the check turns green.

If you need more detail, the record lists start and failure signals. Send a start ping at the top of the script and a success ping at the end, and the log shows how long each run took. Send a failure signal when something breaks and you can be alerted right away instead of waiting for the grace period.

Picking a grace period

Too short and a slow run triggers a false alert. Too long and you hear about a real failure late. A good start is the job's usual duration plus a margin of a few minutes, then tune it after a week of logs.

Jobs with variable run time, like a data import, need a bigger window. Jobs that should take seconds can use a small one.

Write down why you picked the number. Six months on, nobody remembers.

What to monitor first

Start with the jobs where silence would hurt: database backups, billing runs, report emails, certificate renewals and sync tasks. Each of those can fail without a visible error, and each can be costly when it does.

One tip: ping at the end of a script only if every step worked. If you put the ping early, a later failure goes unnoticed.

  • Backups and restore tests
  • Invoice and payment jobs
  • Data imports and exports
  • Certificate and domain renewals
  • Scheduled emails and reports

Check the limits yourself

The record shows a free Hobbyist plan, verified on July 18, 2026. The number of checks, team size and log retention depend on the plan, and they change. Read the current plan page before you build around a limit.

The idea behind it

Most monitors ask your server a question from outside. Healthchecks.io flips this. Your job pings the service when it finishes, and the service raises an alarm if the ping doesn't show up on time. That makes it a good fit for backups, imports, billing runs and any scheduled script.

A typical setup is one line at the end of a cron job: a request to a unique URL. If the backup fails halfway, that line never runs, and you hear about it within the grace period you chose.

It also supports start and fail signals, so you can see how long a job takes and get told straight away when it reports failure, instead of waiting for the timeout.

Where it works best

Think of the jobs you only notice when they break. A nightly database dump. A weekly report email. A script that renews a certificate. Each one is a quiet failure waiting to happen, and a missing ping is a cheap way to catch it.

Pick the schedule type that matches the job. A simple period works for something that runs every hour. A cron expression with a time zone suits jobs that run at fixed local times, and it avoids false alarms when daylight saving shifts.

Set the grace time to a little longer than the slowest normal run. Too short and you get noise. Too long and you learn about problems late.

It can be self-hosted, which some teams prefer for privacy or control. That means you run and update it yourself, so weigh that effort against the hosted plans.

A note on accuracy

We checked the details on this page against the vendor's own documentation on July 18, 2026. Limits and prices can move, so confirm on their site first. There are no affiliate links here.