Cron Job Monitoring
Most tools only check if your job ran. They don't check if it worked. DeadManCheck catches all three failure modes — missing jobs, slow jobs, and jobs that run but produce nothing.
The classic dead man's switch. Your nightly backup didn't ping. Your ETL didn't run. DeadManCheck alerts when expected pings go missing.
Your 2-minute backup job is now taking 45 minutes. It will technically "succeed" — but something is wrong. DeadManCheck tracks duration and alerts on anomalies automatically.
Unique to DeadManCheckExit code 0. On time. But it exported 0 rows, synced 0 records, or returned nothing. DeadManCheck checks whether your job actually produced real results — not just that it ran.
Unique to DeadManCheckAdd a ping to the end of your job. DeadManCheck handles the rest — no agents, no SDKs, no config files.
| Feature | DeadManCheck | Healthchecks.io | Cronitor |
|---|---|---|---|
| Missing ping detection | ✓ | ✓ | ✓ |
| Long-running job detection automatic baseline | ✓ automatic | Manual grace period | Manual only |
| Output assertions | ✓ | ✗ | ✗ |
| Uptime monitoring | ✓ | ✗ | ✓ |
| Public status pages | ✓ free | ✗ | +$25/mo |
| Open source / self-hosted | ✓ | ✓ | ✗ |
| Flat monthly pricing | ✓ | ✓ | ✗ per-monitor |
| Prometheus metrics | ✓ | ✓ | ✗ |
Whether you're dealing with a scheduled task that stopped running, a cron job that's taking too long, or a job that ran but returned no data — DeadManCheck covers all three.
Most cron monitoring tools were built to solve one problem: the missing ping. DeadManCheck was built to solve all three ways scheduled jobs fail — including the two that look like success.
Free plan includes 5 monitors. No credit card. No agent to install.
Start monitoring free →