Back to Blog
Migration Guide 6 min read

Cronhub is shutting down. Here's how to migrate in 2 minutes.

Published March 21, 2026

Cronhub permanently shuts down June 30, 2026.

Every monitor you have on Cronhub will stop working on that date. If you wait until the last week, you're migrating under pressure. Do it now while it's calm.

If you're reading this, you probably got the email. Cronhub is done. Your cron monitors need a new home before June 30, or they simply stop working — and you're back to finding out about failures the hard way.

The good news: migration is painless. Every cron monitoring tool works the same way — your job pings a URL, the service watches for missed pings. Switching means creating new monitors and swapping the URL in your crontab. That's it.

We built PingCron specifically for developers who want fast, simple cron monitoring without the bloat. Here's how to migrate, step by step.

Migrate from Cronhub to PingCron in 4 steps

1

Sign up

Create a free account at pingcron.io. Takes 10 seconds. No credit card.

2

Recreate your monitors

For each Cronhub monitor, create a new one in PingCron with the same name and schedule. You'll get a unique ping URL like:

3

Swap the URL in your crontab

Replace the Cronhub URL with your new PingCron URL:

4

Verify

Wait for the next scheduled run and check your PingCron dashboard. You should see the first ping arrive. Done.

Your new ping URL
https://api.pingcron.io/ping/a1b2c3d4e5f6
Before → After
# Before (Cronhub)
0 2 * * * /scripts/backup.sh && curl -s https://cronhub.io/ping/xxxx

# After (PingCron)
0 2 * * * /scripts/backup.sh && curl -s https://api.pingcron.io/ping/a1b2c3

That's the entire migration. If you have 10 monitors, budget 20 minutes. Most people finish in under 10.

Ready to migrate?

Free plan. 5 monitors. No credit card. Takes 30 seconds.

Start migrating

What you get with PingCron

PingCron covers everything Cronhub did, plus a few things it didn't:

Email, Slack, Discord, and webhook alerts — all on the free plan
Uptime graphs with 7, 30, and 90-day history
Public status pages you can share with your team or customers
Team members with admin and member roles
/start and /fail ping types for job duration tracking
Grace periods to prevent false alarms
Recovery alerts when a job comes back online

Other alternatives to consider

PingCron isn't the only option. Here's a quick look at the landscape so you can decide what fits:

FeaturePingCronCronitorHealthchecksUptimeRobot
Free monitors552050
100 monitors cost$29/mo$200/mo$20/mo$16/mo
Discord alerts
Status pages
/start + /fail
Team members
Open source

Cronitor is the most feature-rich — SDKs, job logs, cron visualization. It's also 7-10x more expensive. If you're an enterprise team with budget and need deep observability, it's worth looking at. For most teams, it's overkill.

Healthchecks.io has the best free tier (20 monitors) and it's open source. The tradeoff: no status pages, more basic UI, and if you self-host, you're maintaining infrastructure for your monitoring tool. Full comparison →

UptimeRobot has the most free monitors (50) but cron monitoring isn't its focus — it's a website uptime tool with heartbeat monitoring bolted on. No /start or /fail signal support.

Don't wait until June

The worst time to migrate is the week before the deadline, when you're scrambling and your monitoring is about to go dark. The best time is now, while everything is still running and you can migrate one monitor at a time, verify it works, and move on to the next.

Twenty minutes today saves you a fire drill in June.

Migrate from Cronhub today

Free plan. No credit card. Setup in 30 seconds.

Start monitoring free