Cron job monitoring with heartbeat checks
An uptime check asks your site if it's up. A cron job can't answer that question, so it works the other way round: your job pings QuickStatus.dev when it finishes. If the ping doesn't arrive on time, you get an alert.
This is sometimes called a dead man's switch: silence is the alarm, so it still fires when the server is off and your code never runs.
Add it to any job
- Click Add check, then Heartbeat. Name it, for example “Nightly backup”.
- Pick Expected every: how often the job runs. It goes from 1 minute to 1 day, with a 5-minute minimum on Free.
- Pick Grace, the extra wait before a late ping counts as missed. It starts at the same value as Expected every. For a daily job, pick something a bit longer than the job's longest normal run, such as 1 hour, or you'll hear about a missed run a day late.
- Copy the ping URL. It's shown only once.
0 3 * * * /usr/local/bin/backup.sh && curl -fsS -m 10 --retry 3 <ping URL>
The && means the ping only goes out if the job succeeded. Add /fail to the ping URL to report a failed run. If you lose the URL, get a new one from the check page, and the old one stops working.
What it catches
- A server that rebooted and never restarted cron
- A backup script that exits early
- A crontab line someone deleted or broke
- A GitHub Actions or Kubernetes CronJob schedule that silently stopped
- A job that runs but fails, reported with
/fail
Guides for your scheduler
- GitHub Actions scheduled workflows: one curl step at the end of the job
- Kubernetes CronJobs: ping from the Job, so the alert still fires when the cluster is down
- Backups: a backup script that pings after the upload and reports
/failon error
Same account as your uptime checks
Heartbeats sit in the same list as your HTTP, MCP, DNS and TCP checks. The free plan also includes a public status page. Link a heartbeat to a status-page component so a missed backup shows up where your team already looks. Planned downtime? A heartbeat inside a maintenance window isn't marked late.
Pricing
The Free plan gives you 10 checks of any type, heartbeats included, plus email and Telegram alerts (2 chats) and 14 days of results, with no card needed. Pro is $15 a month for 25 checks, a 1-minute minimum for Expected every, 90 days of results, and Slack, Discord, PagerDuty, Pushover, webhook and unlimited Telegram alerts. See pricing
Not sure what your schedule means? Try the cron expression generator. Field-by-field details are in the checks docs.
Cron job monitoring FAQ
What is heartbeat monitoring?
Your job sends an HTTP request to a unique URL each time it runs. If the request doesn't arrive within the expected period plus the grace period, the check goes down and you're alerted.
Do I need to install an agent?
No. Anything that can make an HTTP request works, whether that's curl, wget, or a line in your code.
Can a job report that it failed?
Yes. Call the ping URL with /fail added.
Can I monitor a weekly or monthly job?
Not yet. Expected every goes up to 1 day, so heartbeat checks fit jobs that run at least once a day.
What happens during planned maintenance?
A heartbeat inside a maintenance window isn't marked late. When the window ends, it gets a full Expected every plus Grace before a missing ping counts.
Is it really free?
Yes. The Free plan is permanent, not a trial: 10 checks of any type, no card.