Skip to content

Migrate from Cronhub

Moving off Cronhub? Bring your check-ins to CronRadar.

Third-party reports say Cronhub ended service on May 31, 2026, and cronhub.io did not respond when checked on November 16, 2026. We found no official statement. If your jobs still ping Cronhub, nothing is watching them.

10 monitors free · No credit card · Checked November 16, 2026

At a glance

CronRadar and Cronhub, side by side.

Each competitor cell comes from the linked source. Prices are list prices in USD per month before tax.

Cronhub facts checked November 16, 2026. Vendors change products and prices; check the sources below.
FeatureCronRadarCronhub
ServiceRunningReported ended May 31, 2026; cronhub.io returned a Cloudflare 522 error on November 16, 2026
Free plan10 monitors, no cardNot applicable
SchedulesFive-field cron or @daily-style shortcuts, in the application’s time zoneNot applicable
Framework discoveryHangfire, Quartz.NET, Celery and Laravel: every recurring job is found automatically, with an explicit opt-outNot applicable
Alert channelsemail, Slack, webhook, Discord, PagerDuty. No SMS or phone calls.Not applicable

Fit

Which one fits your jobs?

Why CronRadar for former Cronhub jobs

  • Each Cronhub ping can become a CronRadar ping URL with ?schedule=, and the monitor creates itself on its first ping.
  • Jobs in Hangfire, Quartz.NET, Celery or Laravel need no per-job URLs at all: the package finds them.
  • Free covers 10 monitors without a card.

Setup

Setup, side by side.

A manual ping URL per job versus discovery from the framework that already knows every job.

Cronhub

  1. Find every place your code or crontab calls a Cronhub URL.
  2. Note each job’s schedule and who should hear about it.

CronRadar

  1. Install the package for your framework and set CRONRADAR_API_KEY.
  2. Deploy. The package reports every recurring job it finds, with its name and schedule.
  3. Or, for any other scheduler, call the ping URL with ?schedule= and the monitor creates itself on the first ping.

See every integration and its package status

Migration

Move from Cronhub one job at a time.

There is no importer. Replacing each ping is the migration.

  1. Step 1

    Find the old pings

    Search crontabs, deploy scripts and job code for Cronhub URLs. Each one is a job that is currently unmonitored.
  2. Step 2

    Create an application and key

    Sign in to CronRadar, create an application per environment and copy its API key.
  3. Step 3

    Replace each ping

    Swap the Cronhub URL for a CronRadar ping URL with the job’s schedule in ?schedule=, or install the package for your framework and remove the URLs entirely.
  4. Step 4

    Verify one run and one alert

    Wait for a real run to arrive, then confirm an alert reaches its destination using a harmless job in a test application.

FAQ

Questions, answered.

Primary sources

Checked November 16, 2026. Vendor products and pricing can change.

Other comparisons: Cronitor · Sentry Crons · Healthchecks.io · Better Stack · Cronwatch · Dead Man’s Snitch · All tools

Start with one job your customers depend on.

10 monitors free, no card. Confirm a real run and an alert before moving the rest.