Compare · RealUptime Monitor
Cronhub shut down: where cron monitoring goes now
Cronhub announced its shutdown in 2026: paid subscriptions were cancelled on May 31, 2026 and the service, including schedules, monitors and ping history, was deleted on June 30, 2026. Its domain answers HTTP 522 today. Cronhub was two products in one account, a Scheduler that triggered your HTTP jobs on a cron expression and Monitoring that watched heartbeats and dead-man checks. This page is honest about which half RealUptime Monitor replaces, because only one of them is a monitoring product.
Service still running
Have
active, checking customer endpoints today
Don’t have
paid subscriptions cancelled May 31, 2026; schedules, monitors and ping history deleted June 30, 2026. cronhub.io answered HTTP 522 when this page was verified
Heartbeat and dead-man monitoring for cron jobs
Have
heartbeat monitors on every plan including Free, with a per-monitor interval and grace period; silence past interval plus grace is the alert
Don’t have
this was Cronhub's Monitoring half, deleted with the rest of the service
Running your cron jobs for you
Don’t have
RealUptime never executes your jobs. Your scheduler keeps running them and pings us when a run finishes
Have
Cronhub's Scheduler half triggered HTTP endpoints on a cron expression; that is a job runner, not a monitor, and it is the half nothing here replaces
Active uptime checks on your sites and APIs
Have
HTTP, TCP, DNS, SMTP and ping checks, each read from several named regions on the same run
Partial
Cronhub monitored scheduled work; outside-in uptime checking of a website was not what it sold
Free tier
Have
10 monitors of any type, 5 servers, no credit card, commercial use allowed
Not published
the pricing page went down with the service, so there is nothing left to quote honestly
Getting your data out
Have
monitor list, incidents and readings export from the dashboard and the REST API on Growth and Scale, any time
Don’t have
the deletion date has passed; if you did not export before June 30, 2026 there is nothing left to retrieve
Alerting on a missed run
Have
the same fan-out every other check uses: email, Slack, Discord, Microsoft Teams, Opsgenie, PagerDuty, Zapier and webhooks, plus incidents and status-page components
Don’t have
no longer running, so no alert path survives
The scheduler half, said plainly
If what you used Cronhub for was the Scheduler, calling your endpoints on a cron expression so you did not have to run a machine, RealUptime does not do that and is not going to tell you it does. Keep your jobs where they run now, on your own cron, your platform's scheduler, or a job runner, and use a heartbeat here to find out when a run stops arriving. That is the split: your scheduler runs the work, this product notices the silence. If both halves matter to you, a dedicated scheduling service plus heartbeats here is the honest shape, and we will not pretend one vendor covers it.
What the account covers beyond heartbeats
A cron monitor is rarely the only thing a team needs watched, so it is worth knowing what one signup already includes. RealUptime Monitor covers heartbeats alongside HTTP, TCP, DNS and server checks, free for 10 monitors and 5 servers, read from four named regions on Free and up to ten on Scale. RealUptime Status publishes what those checks see on a public page. RealUptime Errors catches the exception the job threw before it stopped pinging, free for 10,000 events a month. RealUptime Outages tracks the vendors your job depends on and needs no account at all. One signup provisions the free tier of each, with no card.
Moving off Cronhub in practice
For the step-by-step version, including what a heartbeat token means for the crontab lines you have to edit, see how to migrate from Cronhub. If you are weighing a dedicated cron monitor instead, our comparisons with Healthchecks.io and Cronitor are the same sourced, dated format as this page.
Is there a free tier?
RealUptime is free to start and never asks for a card. One signup turns on the free rung of every product: 10 monitors with a public status page, 5 server-agent slots, and 10,000 error events a month kept for 14 days. RealUptime Outages is free to read with no account at all.
Cronhub: unpublished. The pricing page went down with the service, so there is nothing left to quote honestly.
Is it open source or self-hosted?
RealUptime's core is a hosted service and its source is not published, so there is no self-hosted edition of the platform itself. The parts that run on your side are open source at github.com/RealUptimeHQ: the CLI and the RealUptime Errors SDKs for JavaScript, Python, Go, PHP and Ruby are MIT-licensed, and the Grafana data source is Apache 2.0.
Cronhub: a hosted product that published no source and is no longer running.
If self-hosting is a hard requirement, these are the open-source options in this category: Uptime Kuma (MIT), OpenStatus (AGPL-3.0), Healthchecks.io (BSD 3-Clause) and OneUptime (Apache 2.0).
Looking for a Cronhub alternative?
For the reasoning behind checking from more than one region at all, see why a status page can show all green during a real outage. Comparing more than just this one alternative? The status page tool checklist covers what to test before committing to any of them.