Send one heartbeat
Add a single authenticated ping at the end of a cron job, CI pipeline, backup, sync, or scheduled task.
Cron monitoring
Catch the jobs that fail silently.
Monitor backups, billing jobs, imports, reports, and CI pipelines with a heartbeat that proves the work completed on time.
- the entire integration
- 1 curl call
- the entire integration
- schedule evaluated against real fire times, not polling
- 5-field cron
- schedule evaluated against real fire times, not polling
- configurable buffer before marking down
- grace_period_seconds
- configurable buffer before marking down
01Job runs
Your script, backup, import, or CI step does its work as scheduled.
02Heartbeat ping
curl https://api.monitero.io/api/v1/cron/<token> — one line at the end of the job.
03Schedule evaluated
The most recent expected fire time is computed from your actual cron expression.
04Silence caught
No ping within the grace window past the fire time → the monitor goes down.
How it works
The simplest check for the work nobody sees.
Check the real schedule
Use a five-field cron expression so a daily or weekday job is evaluated against when it should run.
Allow the right grace period
Give late jobs a deliberate window before Monitero marks the monitor down and alerts your team.
Catch silence
Know when a job stopped doing its work even though your website and servers still look healthy.
What makes it powerful
Catches the failure mode that leaves no trace
A background job that stops running without throwing an error is invisible to every other kind of check. The cron-expression evaluation means a job scheduled for 9 AM is judged against that exact fire time, not a generic polling interval — so on-time actually means on-time.
Keep moving