−50%

50% off your first month on any paid plan · code WELCOME50 · until Nov 30

Start free →

Cronhub Shut Down. Here Is How to Migrate to WatchCron

Cronhub shut down on June 30, 2026. Here is what migrating to WatchCron looks like — both heartbeat monitoring and HTTP scheduling.

The Cronhub shutdown hit on June 30, 2026. Dashboard went dark, no redirect, no data export tool, no "download your monitors" button on the way out. If you opened cronhub.io that morning expecting to check your jobs, you found a login page with nothing behind it. And if you need a Cronhub alternative that covers both monitoring and scheduling, this guide walks through the full migration.

The team had posted a shutdown notice back in March and gave everyone three months. Fair enough. But months later, we're still seeing people land on our site searching for "cronhub alternative," which tells us plenty of users either missed the email or kept putting off the Cronhub migration until the URLs stopped working. If that's you, or if you just noticed your cron jobs haven't been reporting anywhere since July, here's what to do next.

What Cronhub actually did

Heartbeat monitoring. Your cron job pings a URL (cronhub.io/ping/<uuid>) after each run. Miss a ping, get an alert. Cronhub also tracked /start, /finish, and /fail endpoints, so you could measure how long a job ran and catch explicit failures, not just silence.

Then there was the scheduling side. Cronhub calls your endpoint on a cron schedule. No server crontab needed. This was the product WordPress site owners and shared-hosting users relied on, because they couldn't edit crontab themselves.

Both products are gone. All ping URLs are dead. Every schedule Cronhub was firing has stopped. If your cron job still curls cronhub.io, it's silently failing to report. Have you checked? Your actual jobs are still running fine, the curl just fails quietly (especially with the -f flag). The jobs work; you just can't see whether they do.

Why WatchCron works as a Cronhub replacement

We built WatchCron around the same two problems: cron job monitoring handles the heartbeat side (your job pings us, we alert if it goes quiet), and Cloud Cron handles the scheduling side (we call your URL on a cron expression and monitor whether it succeeded). One dashboard for both.

The caveat: if you only used Cronhub's heartbeat monitoring, you have options. Healthchecks.io, Cronitor, Better Stack — they all do ping-based monitoring and they're solid. We wrote honest comparisons for each if you want the details side by side. The difference matters most when you used BOTH Cronhub products. Most alternatives cover monitoring or scheduling, not both. Splitting your setup across two tools is doable but annoying, and if you're looking for a direct Cronhub alternative that does both, that narrows the field.

A few things WatchCron does that Cronhub never offered: uptime monitoring, SSL certificate tracking, domain expiration alerts, port checks, DNS blocklist monitoring, and public status pages. Port and domain monitors are unlimited on every plan and don't count against your check limit.

Cronhub vs WatchCron pricing

Cronhub's cheapest paid plan (Developer) ran $19/month for 5 schedulers and 10 monitors. Their free tier gave you exactly 1 scheduler and 1 monitor. At the top, the Business plan was $99/month for 50 schedulers and 100 monitors.

WatchCron's free plan includes 20 checks and 1 Cloud Cron job. The Starter plan at $7/month gets you 75 checks and 5 Cloud Cron jobs — more monitors at less than half what Cronhub charged. Here's the side-by-side:

Cronhub DeveloperWatchCron Starter
Price$19/month (gone)$7/month
Heartbeat monitors1075
HTTP schedulers55 Cloud Cron jobs
Alert channelsEmail, Slack, WebhookEmail, Slack, Telegram, Discord, Microsoft Teams, PagerDuty, OpsGenie, Webhook
Uptime / SSL / Domain / PortNoIncluded
Team members1 (single-user)3

Cronhub gated team access behind their $49/month Startup plan. WatchCron's $7/month Starter includes 3 members. That was one of the more frustrating limitations Cronhub had, especially if you worked with a co-founder or a contractor who needed dashboard access.

(Side note: Cronhub's pricing page stayed up weeks after the product died. We kept checking it while writing comparisons, and the cached version on the Wayback Machine still shows the $99/month Business tier. Strange how pricing pages outlive the products.)

How to migrate from Cronhub to WatchCron

Is there an automatic import tool? No. Cronhub's API is gone and there's no way to export your old configuration, so there's nothing to pull even if we built one. You'll recreate your monitors by hand. For most setups, 5 to 15 checks, this genuinely takes about 10 minutes.

1. Sign up and create a project

Create a free account. No credit card, no trial expiration on the free plan. You land in a project, which works like a workspace for a specific app or client.

2. Recreate heartbeat monitors

WatchCron's check system is a direct Cronhub heartbeat monitoring replacement — same ping-based model, same /start and /fail endpoints. For each old Cronhub monitor, create a new check:

  • Set the schedule — cron expression or plain-English interval like "every 5 minutes." If you don't remember the exact expression, the cron expression builder helps, or check the cheat sheet
  • Set the grace period. This is what Cronhub called "tolerance" — the window after the expected time before we mark the job as late. If your nightly backup takes 20 minutes, set grace to 30
  • Copy the new ping URL

Then swap the URL in your crontab:

# Before (Cronhub — URLs are dead now)
0 2 * * * /opt/app/backup.sh && curl -fsS https://cronhub.io/ping/abc123

# After (WatchCron)
0 2 * * * /opt/app/backup.sh && curl -fsS https://watchcron.com/ping/xyz789

If you used Cronhub's /start and /fail endpoints for run-duration tracking, WatchCron supports the same pattern: /ping/ID/start before the job and /ping/ID/fail on error. The heartbeat monitoring guide walks through the full setup, including how dead man's switches work under the hood.

3. Recreate schedulers as Cloud Cron jobs

If you're specifically looking for a Cronhub scheduler alternative, Cloud Cron is the direct equivalent. Enter the target URL, pick a cron expression, WatchCron handles the rest. If your endpoint returns anything other than 2xx, you get alerted.

WordPress users who relied on Cronhub to hit wp-cron.php: there's a dedicated Cloud Cron for WordPress setup. Point it at https://yoursite.com/wp-cron.php?doing_wp_cron, set the interval to every 5 or 15 minutes, done. We wrote a separate guide on fixing WordPress cron issues if wp-cron was already unreliable before the migration.

4. Configure alert channels

Cronhub supported email and Slack on all plans. Webhooks and SMS were paid-only. WatchCron's notification channels include email, Slack, Telegram, Discord, Microsoft Teams, webhooks, PagerDuty, and OpsGenie on every plan including the free one. SMS is available on Pro ($19/month) and up.

Head to Settings, then Notification Channels. Takes about a minute per channel.

5. Verify the migration

Trigger each monitor manually to confirm it's wired correctly:

curl -fsS https://watchcron.com/ping/YOUR_CHECK_ID

The dashboard should flip to "Up" within seconds. For Cloud Cron jobs, wait for the first scheduled run and check the response code in the log. If something looks wrong, the cron job not running troubleshooting guide covers the most common causes.

Other Cronhub alternatives worth considering

We make WatchCron, so why would you trust our recommendation? Take it with the appropriate grain of salt. Here are the other tools serving as a Cronhub replacement for former users, based on what we see in the SERP and on forums:

Healthchecks.io — Open-source, self-hostable, 20 free checks. Closest thing to Cronhub's monitoring side. No HTTP scheduling though (you'd need a separate tool for the scheduler half).

Cronitor — Deeper analytics, crontab auto-import, great for teams with hundreds of jobs. Starts at $49/month, so it's a jump from what Cronhub cost.

Better Stack — Monitoring plus logs plus on-call rotation in one platform. Enterprise-leaning. Paid plans start around $29/month for monitoring.

For the full picture, see our online cron services roundup (covers scheduling tools) and the cron monitoring tools comparison.

What to set up after your Cronhub migration

Since you're rebuilding your monitoring from scratch anyway, worth grabbing what Cronhub didn't offer.

The REST API lets you create checks, pull ping history, and manage monitors programmatically. If you provision infrastructure with Terraform, Ansible, or CI/CD pipelines, you can have monitoring follow deploys automatically instead of hand-creating checks in a dashboard. Cronhub had an API too, so the workflow should feel familiar.

Incident management ties monitor failures to trackable incidents with acknowledgment, timeline, and updates. Pair it with a status page if you run anything customer-facing. Cronhub never went there.

And if you're curious about the broader cron job ecosystem — tooling, expressions, platform-specific gotchas — we maintain a pillar guide that covers everything from basic syntax to Kubernetes CronJobs.

Cronhub is gone, but the workflow doesn't have to change much. WatchCron handles both heartbeat monitoring and HTTP scheduling as a direct Cronhub alternative. Sign up free and migrate in one sitting.

Frequently asked

Yes. Cronhub shut down on June 30, 2026. All ping URLs, scheduler endpoints, and user data were deleted. The service is not coming back.

WatchCron covers both heartbeat monitoring and HTTP scheduling (Cloud Cron) in one platform. For monitoring only, Healthchecks.io is a strong open-source option. For enterprise teams, Cronitor offers deeper analytics.

Create a free WatchCron account, recreate each monitor with the same cron expression and grace period, then swap the Cronhub ping URL in your crontab with the new WatchCron URL.

Yes. WatchCron supports /ping/ID/start before a job runs and /ping/ID/fail on error, matching Cronhub run-duration tracking pattern.

Yes. Cloud Cron calls your endpoint on a cron schedule and monitors success or failure — the same function as Cronhub Scheduler product.

WatchCron free plan includes 20 checks and 1 Cloud Cron job with no trial expiration. Healthchecks.io also offers 20 free checks but has no HTTP scheduling.

Your cron jobs themselves still run, but the monitoring pings to cronhub.io silently fail. Failures go undetected. Replace the dead URLs with a working monitoring service as soon as possible.

More posts

All posts →
Pricing Docs
Log in Start free →