For jobs that fail silently
A scheduled job — a backup, a cron task, a background worker — gets a unique URL to ping when it runs. Miss enough pings, and we alert you before anyone notices the job just stopped.
One HTTP call, at the end of your job
Add a single request — a plain
curl
call is enough — to the end of your script. As long as the ping
keeps arriving on schedule, nothing happens. Miss the expected
window, and it's treated as a real failure.
- No agent or library to install — any script that can make an HTTP request works
- Works with cron, scheduled tasks, CI pipelines, or a manual trigger
- Also used as a cross-check: if a site's uptime check fails but its heartbeat is still arriving, that's treated as a network issue on our side, not your site being down
The details
- One unique URL per job
- Expected interval set to match your job's real schedule
- Independent of your website's uptime checks — runs on its own
Questions people ask
Any scheduled task that can call a URL when it finishes — backups, cron jobs, scheduled emails, sync scripts, CI steps.
No — just add one HTTP call, like curl, at the end of the job. No agent, no library.
Set the expected interval to match your job's actual schedule, with some buffer — it doesn't need to be exact to the minute.
Point a real job at it.
Tell us what job you'd want watched — we'll show you the one-line setup.