Add a unique ping URL to your scheduled jobs. Receive alerts when cron jobs, backups, reports, scripts, or background tasks stop checking in.
#!/bin/bashset -e /usr/bin/pg_dump -U postgres > backup.sql PING_URL="https://cronhealth.io/ping/your-monitor-token"curl -fsS "$PING_URL"
Works with anything that can send an HTTP request
Uptime monitoring checks if your server is online. CronHealth checks whether your scheduled jobs are still running successfully.
A backup job silently fails for days. The server is healthy, but the safety net you rely on is gone.
Payment, CRM, analytics, or third-party API syncs stop checking in while the rest of the app looks normal.
Scheduled reports, exports, digests, or cleanup jobs can stop running without triggering application errors.
CronHealth starts intentionally simple: create monitors, receive pings, track status, and get email alerts when something is late.
Every monitor gets a secure URL. Call it only after your scheduled task completes successfully.
Choose a preset interval or use a custom cron expression, then add a grace period for normal delays.
Receive alerts through Email, Slack, Discord, or Webhooks when a monitor becomes late and when it recovers.
See whether a monitor is pending, healthy, late, or paused without digging through logs.
Review recent executions, last ping time, next expected ping, and missed/recovered alert history.
Temporarily pause monitors during maintenance or deployment windows and resume when ready.
CronHealth does not run your jobs. Your automations stay in your environment. CronHealth simply waits for expected success pings and warns you when they stop arriving.
Name the job, choose how often it should run, and set a grace period.
Call your unique URL at the end of the cron job, backup script, sync process, or scheduled command.
If the expected ping does not arrive after the grace period, CronHealth marks it late and sends an email.
# Daily backup at 03:00 0 3 * * * /app/bin/backup.sh && curl -fsS https://cronhealth.io/ping/your-monitor-token
Monitor the scheduled jobs that keep your business running.
Know whether your backup script successfully checked in after running.
Monitor recurring Stripe, Paddle, or external API sync jobs.
Catch missing scheduled billing jobs before they become a customer or revenue problem.
Make sure scheduled emails, exports, and internal reports continue checking in.
Track cleanup scripts, cache warmups, indexing jobs, and recurring maintenance tasks.
A lightweight layer for founders who do not want to operate a full monitoring stack.
No SDK required. No agents. No installations. Just call one URL after your job succeeds.
Start free, then upgrade when you need more monitors, longer history, and additional alert destinations.
Perfect for personal projects, hobby apps, and trying CronHealth.
For indie hackers and small production projects.
For developers managing multiple projects and environments.
No. Cron jobs are the common starting point, but any scheduled task, script, command, or worker can call a ping URL after successful completion.
No. Your jobs keep running in your own infrastructure. CronHealth only receives success pings and alerts when expected pings stop arriving.
CronHealth supports Email, Slack, Discord, and Webhook notifications. More integrations may be added based on customer demand.
Uptime monitoring checks whether a service responds. CronHealth checks whether expected background executions are still reporting success.
Create your first monitor in under a minute and get notified when scheduled jobs stop checking in.
Create your free account