Cron jobs fail silently.
PingCron doesn't.
Find scheduled GitHub Actions, review their monitoring setup, and get alerts when expected check-ins are missed. Also works with cron jobs, backups, and scripts that can send an HTTP heartbeat.
5 monitors free · No credit card · Verify your first check-in
nightly-pg-backup
Every day at 02:00
Healthy
last ping 4h ago
stripe-reconciliation
Every hour
Late
2m past schedule
etl-orders-sync
Every 15 minutes
Alert sent
no ping in 22m
For teams running scheduled GitHub Actions
Know which workflows still need monitoring.
Start with one backup, billing job, or data sync. Connect selected repositories with read-only access, discover scheduled workflows, and review what remains before the first successful check-in.
01
Discover the work
Inspect workflows from the default branch. Review their schedules and findings before creating a monitor.
02
Review the installation
For supported single-job Ubuntu workflows, prepare a patch and a monitor-specific secret name. You review and apply the change. Other workflows use manual installation.
03
Verify the protection
Check the first successful heartbeat and confirm an alert test arrived. Then opt into repository coverage checks to review changes over time.
Keep an eye on changes after setup
Optional coverage checks flag unlinked scheduled workflows, changed schedules, missing supported reporting steps, and lost repository access. Review the last successful scan and each source’s verification time. Checks can be delayed; source checks and workload receipts are separate evidence.
5 monitors free. Connecting a repository does not install a heartbeat, edit a workflow, or enable coverage checks.
Cronhub shut down June 30. Former Cronhub Monitoring users can move the same heartbeat workflow to PingCron.Read the migration guide →
The integration
One line. No agent. No SDK.
Send a heartbeat after your required work succeeds. Match the monitor to your schedule, then verify the first receipt and your alert destination.
Your cron job today
# Database backup — runs nightly
0 2 * * * /scripts/backup.shAfter PingCron
# Database backup — runs nightly, monitored
0 2 * * * /scripts/backup.sh && curl -fsS https://api.pingcron.io/ping/abc123If the script fails, the success heartbeat is skipped. Once monitoring is established, a missed check-in can trigger an alert after the expected time and grace period. Replace the example URL with your monitor’s actual URL.
How it works
From setup to a verified check-in.
Create a monitor
Pick a name and the schedule your job runs on — every minute, hourly, daily, anywhere in between.
Add the curl line
Append the unique ping URL to the end of your script with &&. Works in any language.
PingCron waits for pings
Successful runs check in. Late or missing pings start the grace-period countdown.
Alert fires if missed
A missed expectation can trigger alerts after grace. Confirm your alert destination and review delivery status.
Free tools · no signup required
Check your cron schedule before the next run
Use Cron Doctor to review a schedule, inspect supported configuration, and understand reliability findings. Choose your scheduler to see an example and the limits of static analysis.
Cron expression checker
Explain a five-field cron expression, inspect timezone assumptions, and preview scheduled times with Cron Doctor.
Crontab validator
Inspect one crontab job with environment, CRON_TZ and command context. Find supported shell and monitoring reliability risks.
GitHub Actions cron validator
Review scheduled GitHub Actions workflow triggers, timezone context, concurrency and timeout signals in one evidence-backed report.
Kubernetes CronJob validator
Check a supported batch/v1 CronJob manifest for schedule, timezone, concurrency, suspension and Job runtime settings.
systemd timer checker
Inspect supported systemd timer and service settings, calendar triggers, persistence, timing windows and missing execution context.
Laravel scheduler checker
Analyze a supported static Laravel scheduled task, its timezone and overlap settings while keeping dynamic PHP uncertainty explicit.
Configuration is sent to PingCron for analysis, is not saved, and is never executed. A diagnosis does not install a heartbeat or prove a job ran.
Use cases
What developers monitor with PingCron
Concrete jobs that fail silently — and the kind of work PingCron actually catches.
Database backups
Nightly pg_dump, mysqldump, mongodump runs that need to actually complete.
Read the guide →Billing & reconciliation
Daily jobs that match payments to invoices and catch failed charges.
Read the guide →ETL & data sync
Hourly pipelines feeding warehouses, dashboards, and downstream tools.
Read the guide →Laravel scheduler
artisan schedule:run plus individual scheduled tasks in your app.
Read the guide →Python & Node scripts
Cron-driven scripts, APScheduler, Celery beat, node-cron, BullMQ.
Read the guide →GitHub Actions schedules
Scheduled workflows affected by delays, failed steps, or disabled schedules.
Read the guide →What's in the box
Built for developers who ship
Email, Slack, Discord & webhooks
Configure account-level alert destinations. Recovery alerts report a successful heartbeat after a monitor was down.
Run history & graphs
Review reported successes, failures, and starts over 7, 30, 90 days, or 1 year depending on plan.
Missed-ping detection
Configure grace for expected runtime and scheduler delays. Review missed check-ins and alert delivery attempts.
Team members & roles
Invite teammates with admin or member roles. Shared monitors, shared visibility, no per-seat surprise pricing.
Pricing
Simple, transparent pricing
Start free. Upgrade when you need more monitors or your team grows.
Cancel anytime. Email, Slack, and Discord alerts on every plan including Free.
FAQ
Frequently asked questions
Stop finding out the hard way.
Your cron jobs are running right now. If one fails tonight, will you know before your customers do?
Start monitoring free5 monitors free · No credit card · Verify your first check-in