Cronhub shut down on June 30, 2026.
If your scripts still ping Cronhub URLs, those heartbeats are no longer being monitored. Move them to an active monitoring service now.
If you previously used Cronhub to watch cron jobs, backups, scheduled scripts, or other recurring tasks, you need a new heartbeat endpoint for those jobs.
For heartbeat monitoring, the migration is simple: create the same monitor in PingCron and replace the Cronhub ping URL in your existing job. Your scheduler keeps running exactly where it runs today.
Replace your first Cronhub monitor now
5 monitors free · No credit card · Upgrade only when you need more
Start monitoring freeFirst: were you using Cronhub Monitoring or Cronhub Scheduler?
If you used Cronhub Monitoring
PingCron uses the same heartbeat pattern: your job runs on your server or platform, then pings a unique URL. If the ping is late or missing, PingCron alerts you. This is the direct migration path below.
If you used Cronhub Scheduler
PingCron monitors scheduled jobs; it does not execute remote HTTP jobs for you. Move execution to your existing system cron, GitHub Actions, Vercel Cron, Laravel Scheduler, or another scheduler, then install a PingCron heartbeat after the required work succeeds. A heartbeat reports completion; it does not prove the output is correct.
Migrate from Cronhub Monitoring to PingCron in 4 steps
Create a free PingCron account
Start with up to 5 monitors. No credit card is required.
Recreate each monitor
Record the job name, schedule, timezone, and grace period from your own configuration. Save and test the owning account’s alert destination.
Replace the Cronhub URL
Swap the old Cronhub heartbeat URL in your script or crontab for the new PingCron URL.
Run once and verify
Run the actual workload and confirm its first successful heartbeat. If you trigger it manually, verify a later automatic run separately.
Replace the placeholder with your monitor’s actual URL and keep it private. The success request must follow all required work. Review shell control flow before editing a complex command.
Looking for a Cronhub crontab checker?
Use the free crontab validator for a crontab or the cron expression checker for a schedule. Both lead into Cron Doctor’s supported configuration analysis. Review the timezone and predicted times; a valid schedule does not install or execute a job. Remove secrets before submitting configuration.
Why PingCron fits former Cronhub Monitoring users
You do not need to redesign your jobs. You replace the heartbeat endpoint and keep the monitoring workflow familiar:
If you want a deeper look at the monitoring model itself, see our cron job monitoring guide or compare PingCron with Healthchecks.io.
Cronhub alternatives: current pricing snapshot
Pricing changes frequently. These public prices were checked on September 12, 2026 and are included to give you a starting point, not to replace each vendor's pricing page. Sources: Cronitor pricing and Healthchecks.io pricing. Compare included features and user charges as well as monitor counts.
| Service | Free tier | 100 monitored jobs |
|---|---|---|
| PingCron | 5 monitors | $29/mo includes 200 |
| Cronitor | 5 monitors | $2/monitor/mo + $5/user/mo; extras may apply |
| Healthchecks.io | 20 jobs | $20/mo |
Cronitor is broader and more observability-heavy. Its current Business pricing is usage-based at $2 per monitor per month, plus users.
Healthchecks.io offers hosted monitoring as well as an open-source self-hosting option. Read the full comparison →
Finish with a verified job and alert destination
Start with one noncritical job. Create the PingCron monitor, replace the old URL, run the job once, and verify the heartbeat. Then repeat for the rest. You can move five monitors before paying anything.
Put your first Cronhub replacement monitor live
5 monitors free · No credit card · Verify your first check-in
Start monitoring free