Cron Job Monitoring
Know when a scheduled job doesn't run
Monitor scheduled tasks and background jobs with heartbeat pings. Get alerted when a job is late or misses its window entirely.
- Heartbeat pings
- Cron expressions
- Late/missed detection
Cron Jobs
Deep Dive
A job that stays silent alerts
A closer look at what you get, from the first check to the alert that reaches you.
Simple ping URL
Your job calls one URL when it completes — no SDK required.
Cron-aware scheduling
Uptime parses your cron expression and knows exactly when to expect a ping.
Grace periods
Allow jobs a little slack before marking them late.
Healthy → late → missed
A clear state machine so you always know a job's current status.
Get started
From a ping URL to a missed run
Three steps from an empty dashboard to checks that run on their own.
Create a cron job monitor
Enter the schedule as a standard cron expression.Call the ping URL
Add one line to your job that pings the URL on completion.Get alerted if it's late
Uptime tracks expected run times and alerts on missed pings.
# Nightly backup, pinging Uptime only on success UPTIME_API_KEY=uptime_your_api_key 0 2 * * * /srv/backup.sh && curl -fsS -X POST \ https://uptime.sergiodxa.com/api/v1/cron-jobs/{monitor-id}/ping \ -H "Authorization: Bearer $UPTIME_API_KEY"
#!/bin/bash set -e pg_dump mydb | gzip > backup.sql.gz curl -fsS -X POST \ https://uptime.sergiodxa.com/api/v1/cron-jobs/{monitor-id}/ping \ -H "Authorization: Bearer $UPTIME_API_KEY"
FAQ
Frequently asked questions
The questions people ask most before they start monitoring.
Do I need an API key to ping in?
No — the cron-job ping endpoint is public and rate-limited, so a single line in your job is enough.
What happens if my job runs a bit late?
A grace period absorbs normal variance before the job is marked late, then missed.
Start monitoring your services
Create your first monitor in under 2 minutes. No credit card required to start.