Cron monitors let you track scheduled jobs (like backups, batch processing, or recurring scripts) and get notified if they don’t run on time. This helps you make sure critical background processes are always working as expected.
Just like with other monitors, when a cron job fails, you can collaborate with your team to resolve the incident and optionally update your status page.
Here’s an example of how your cron monitor list looks:

When you click on a cron monitor, you can see more details:

To add a monitor, go to your project → Monitors → Add monitor.

Select Cron/Heartbeat as the monitor type.

A unique URL will be generated for you. Your cron job should send an HTTP request (HEAD, GET or POST) to this URL each time it runs.
A cron monitor succeeds when your job pings the generated URL on schedule. You can configure:
If the period time is reached and the job doesn't ping, the monitor will be marked as degraded.
If the grace time is reached and the job doesn't ping, the monitor will be marked as down.
You can set up alerts to get notified when a job fails, degrades or recovers.
Sometimes you want to explicitly mark a job as failed, even if it ran and pinged the monitor.
You can do this by sending a request to the monitor’s URL with /fail appended.
This is useful if your script encounters an error and you want Instatus to record the job as failed right away.
https://cron.instatus.com/your-unique-urlhttps://cron.instatus.com/your-unique-url/failWhen a failure signal is received, the monitor will be marked as down, and alerts will be sent immediately according to your alert settings.