Cron job monitoring
Cron job monitoring that catches the loud failures first.
Crontap fires your HTTP cron, stores every run, and alerts when the call fails. For silent skips (the job never ran), pair a dead-man ping with Healthchecks.io. For public URLs, add built-in uptime in the same dashboard.
At a glance
Failure alerts on every run
Crontap fires your URL, retries 5xx responses, and pages you on timeout or error. Response body, status, and duration land in the run log.
Run history per schedule
Search past fires instead of grepping syslog. See which deploy broke the nightly sync without SSH.
Uptime on public URLs
Same account can probe customer-facing endpoints on a 1-minute cadence (Pro). Schedules and monitors share one alert inbox.
Dead-man when jobs go silent
Crontap does not alert on absence today. Pair a success ping to Healthchecks.io (or your own watcher) for the “never ran at all” case.
How it works
Three layers, one dashboard.
Paste the job URL and cron
Set the five-field expression, IANA timezone, headers, and where alerts go (email, Slack, Discord, Telegram).
Crontap fires on the clock
External HTTP cron hits your endpoint on schedule. Failed runs retry on 5xx before the alert fires.
Catch loud failures and silent skips
Loud: 4xx/5xx/timeout → Crontap alert. Silent skip: add a success ping to a dead-man URL after the job finishes. Public URL down: add an uptime monitor.
Why developers pick Crontap
- Scheduler plus monitoring in one product. Cronitor assumes you bring the clock; Healthchecks assumes you bring the job. Crontap includes both for HTTP cron.
- 1-minute Pro cadence floor, per-schedule IANA timezones, stored auth headers for webhooks.
- Free tier: one schedule with firing included. Pro is $3.25/mo annual flat for unlimited HTTP schedules (not per-monitor pricing).
- Retries on 5xx before alerting. Healthchecks does not retry failed HTTP calls because it does not fire them.
- Built-in uptime checks live next to schedules when you also need “is this URL up for customers?”
Compare
Crontap vs Cronitor vs Healthchecks.io
No rankings: pick by whether you need the clock, the watcher, or both. Crontap is built for teams that want HTTP scheduling and failure alerts without a second bill for the timer.
| Cronitor | Healthchecks.io | Crontap | |
|---|---|---|---|
| Fires HTTP cron jobs | No (monitor only) | No (heartbeat only) | Yes |
| Alerts when HTTP run fails | Yes | No (ping-based) | Yes |
| Alerts when job never runs (absence) | Yes | Yes | Pair with Healthchecks |
| 1-minute cadence on paid | Yes | Yes | Yes (Pro) |
| Paid entry (2026) | ~$49/mo+ | Tiered per check | $3.25/mo annual |
Go deeper
FAQ
Cron job monitoring questions
- Is Crontap a replacement for Cronitor or Healthchecks.io?
- For HTTP cron you schedule externally, Crontap replaces both the clock and failure alerting. For absence detection (the job never fired at all), Healthchecks.io is still the right watcher until Crontap ships native absence alerts. Many teams run Crontap plus Healthchecks on success pings.
- Does Crontap monitor cron jobs on my Linux server?
- Crontap is external HTTP cron: it calls a URL you expose. For scripts that only run on-box, either wrap them in a small HTTP handler or keep system cron and use Crontap to hit a health endpoint. See our Linux cron guide and troubleshooting post for local setup.
- What's the difference between cron monitoring and uptime monitoring?
- Uptime asks “is this URL responding now?” Cron monitoring asks “did my scheduled job run and succeed?” Crontap covers both: schedule failure alerts for calendar jobs, uptime monitors for public endpoints. Neither alone catches a silent skip with no failed HTTP run.
- How do I get alerted when a cron job stops running entirely?
- Add a dead-man ping at the end of your job (curl Healthchecks on success only). Crontap fires the job; Healthchecks pages you if the ping stops. Step-by-step in our Healthchecks pairing post and monitoring heartbeats use case.
- What does the free tier include?
- One schedule with external firing and failure alerts on that schedule. Pro unlocks unlimited schedules, 1-minute cadence, retries, and uptime monitors on the same plan.
Ready to fix it?
Point Crontap at any URL. Pick any cron. Done.
WordPress, Shopify, Railway, Cloud Run, Vercel, HubSpot, Ghost, your own box. If it answers HTTP, Crontap can drive it on a clock you can read, in the timezone that actually matters, and page you when something breaks.
Free forever tier ・ No credit card required
/wp-cron.php?doing_wp_cron=1
Schedule
"every 5 minutes"
Next
in 23s