Track Cron Jobs & Schedulers

Know When Your Scheduled Tasks Silently Fail

Your cron job pings us after every successful run. If the ping doesn't arrive on time, we alert you instantly — before users notice missing data.

Start Monitoring for Free
 

Missed Cron Runs Are the Most Expensive Bug You'll Never See

Your backup fails and you don't know for weeks. Your email digest stops sending and subscribers drop. Your billing job skips and invoices get delayed. Updown Monitor uses heartbeat pings to catch these failures in minutes.

 

How Heartbeat Monitoring Works

Unique Ping URL

Each heartbeat has a unique URL. Your cron job hits it after success.

Flexible Intervals

Expect pings every few seconds, hourly, daily, or monthly — any schedule.

Grace Periods

Buffer time before alerting — avoids false alarms for jobs with variable runtime.

Works in Any Language

One line of curl, wget, or HTTP client — no SDK or library needed.

Multi-Channel Alerts

Slack, email, SMS, phone call, WhatsApp, webhook — alert wherever you work.

Full Run History

See every ping received, missed run, and resolved incident over time.

 

Frequently Asked Questions

Anything that should run on a schedule: backups, data syncs, email digests, billing jobs, batch reports, queue workers, and any cron job or systemd timer.

Append curl -s https://your-heartbeat-url to the end of your cron command. Takes seconds to set up.

Only ping on success — failed jobs never reach our endpoint, and the missed ping triggers an alert.

Yes. Intervals go from seconds to months, and you can add a grace period to avoid alerts on slow but successful runs.

When the next ping arrives, the incident automatically resolves and you get a recovery notification.