Cron job monitoring

Cron job monitoring that tells you when a job stops running

Backups, invoice emails, data syncs — when a scheduled job breaks, nothing tells you. Give each job a check-in URL, and Uptura alerts your team the moment a run is missed or reports a failure.

or try the free Cron Expression Generator — no sign-up required

Cron jobs

4 jobs · checking in

1 missed
  • Nightly database backupdaily · 02:00on time
  • Invoice emailshourlyon time
  • Search index syncevery 15 minmissed
  • Cache cleanupevery 5 minon time
Search index sync: no check-in for 22 min

Why it matters

Scheduled jobs fail without making a sound

Uptime monitoring can't see a backup that didn't run or a queue that stopped draining — the website is still up. Cron job monitoring watches the jobs themselves, so a missed run is caught in minutes, not discovered weeks later.

Silent

is how cron jobs fail

A job that never runs doesn't throw an error anyone sees. The site stays up, the dashboard stays green, and the work just stops happening.

Days

before anyone notices

A missing backup is usually found when you need to restore one. A sync that stopped shows up as stale data a week later — long after it could have been fixed.

One line

is all it takes

Adding a check-in call to the end of a job takes a minute. From then on, every run that doesn't happen is an alert instead of a surprise.

What you get

Everything a cron job monitoring tool should do

Heartbeat monitoring for every scheduled job — backups, reports, syncs, queues — with alerts when a run is missed or fails, and a history that shows how each job is behaving.

  • One check-in URL per job

    Each job gets its own private URL. Call it with curl, PowerShell, Node, Python, or PHP when the job finishes — no agent, no SDK, works anywhere your job runs.

  • Missed check-in alerts

    Tell Uptura how often the job runs and how much slack to allow. If a check-in doesn't arrive in time, you're alerted — the job is either stuck, failing, or never started.

  • Report failures instantly

    Add /fail to the URL when your script catches an error, and Uptura opens an incident straight away instead of waiting for the next check-in to be missed.

  • Grace periods, no false alarms

    Jobs rarely finish at the same second every time. A grace period gives slow runs room, so a backup that takes ten minutes longer tonight doesn't wake anyone up.

  • Check-in history

    See every check-in on a chart — on time, late, or failed — with the interval between runs, so you can spot a job that's drifting before it breaks.

  • Recovery alerts and incidents

    When the job checks in again you get a recovery notice, and every missed run is logged as an incident with how long it lasted — next to your other website checks.

How it works

Add a job, add one line, get alerted

Cron monitoring should take a minute to set up. Uptura doesn't need access to your server — your job simply checks in each time it runs.

  1. 1

    Add a cron job

    Name it, pick how often it runs (every 15 minutes or slower on Free, down to every minute on Pro), and choose a grace period. Uptura gives you a check-in URL.

  2. 2

    Call the URL when it finishes

    Add one line to the end of your job — for example “&& curl -fsS https://…/hb/<token>” in your crontab. Each run checks in.

  3. 3

    Get alerted if a run is missed

    If a check-in doesn't arrive within the interval plus grace period, or the job reports a failure, your team is alerted by email or Slack.

Check-in examples

One call from any language or scheduler

Anything that can make an HTTP request can check in. Add the call after the job succeeds, or call /fail when it catches an error.

Crontab

0 2 * * * /path/to/backup.sh && curl -fsS -m 10 --retry 3 -o /dev/null https://backend.uptura.io/hb/<your-token>

Report a failure

/path/to/backup.sh || curl -fsS -m 10 -o /dev/null https://backend.uptura.io/hb/<your-token>/fail

PowerShell

Invoke-RestMethod -Uri "https://backend.uptura.io/hb/<your-token>" -TimeoutSec 10

Node.js

await fetch("https://backend.uptura.io/hb/<your-token>");

Python

import urllib.request
urllib.request.urlopen("https://backend.uptura.io/hb/<your-token>", timeout=10)

PHP

file_get_contents("https://backend.uptura.io/hb/<your-token>");

Compare

A Cronitor and Healthchecks.io alternative

Dedicated cron tools are great if jobs are all you watch. If you also look after the websites those jobs keep running, Uptura puts both in one dashboard at a flat price.

UpturaDedicated cron tools
What it watchesCron jobs plus uptime, SSL, DNS, API, SEO, performance, and accessibilityCron jobs and scheduled tasks
Free plan3 cron jobs (15-minute intervals and up) plus 3 monitored sitesVaries by tool
Paid plansFlat price: Pro $19/mo for 20 jobs, Scale $49/mo for 100Often priced per monitor or by usage
SetupOne check-in URL per job — no agent or SDKCheck-in URL, often with optional SDKs or CLI
AlertsEmail on Free; Slack, Discord, and webhooks on paid plansEmail, chat, and paging integrations

FAQ

Cron job monitoring, answered

  • What is cron job monitoring?

    Cron job monitoring checks that your scheduled jobs actually run. Instead of watching a website, it waits for your job to check in: each run calls a unique URL when it finishes, and if a check-in doesn't arrive on time, you get an alert. It catches the failures nothing else sees — a backup that silently stopped, an invoice email that never went out, a sync that hung.

  • How does heartbeat monitoring work?

    Heartbeat monitoring flips normal monitoring around. Uptura doesn't call your system — your job calls Uptura. You set how often the job runs and a grace period; every check-in resets the timer. If the timer runs out (last check-in + interval + grace) with no check-in, Uptura marks the job as missed and alerts you. The next successful check-in closes the incident.

  • How do I check if a cron job is running?

    On the server you can look at the cron log (for example “grep CRON /var/log/syslog”) or have the job write to its own log file — but that only helps if someone looks. The reliable way is a cron job checker that alerts you: add a check-in call to the end of the job, and Uptura tells you the moment a run doesn't happen.

  • My cron job is not running — how would I find out?

    Usually from a customer, or days later when the data is already missing. Common causes are a changed path or environment variable, a server reboot, a full disk, or a crontab that was overwritten. With cron monitoring you find out within minutes: the missed check-in raises an alert, and the check-in history shows exactly when the job last ran.

  • Can I use it for backup monitoring?

    Yes — backups are the most common use. Add the check-in call after the backup command succeeds (“backup.sh && curl …”), so a failed or skipped backup never checks in and you're alerted. Use a grace period a little longer than the backup normally takes.

  • What is a grace period?

    It's extra time Uptura waits after a check-in is due before alerting. A job that runs every day with a 30-minute grace period is only flagged if no check-in arrives within 24 hours and 30 minutes of the last one — so a slow run isn't treated as a failure.

  • Does it work with Windows Task Scheduler, Kubernetes CronJobs, or Laravel?

    Yes. Anything that can make an HTTP request can check in: crontab, Windows Task Scheduler (PowerShell “Invoke-RestMethod”), Kubernetes CronJobs, GitHub Actions schedules, Laravel's scheduler, Sidekiq or Celery tasks, or a plain script. There's nothing to install.

  • Is cron job monitoring free?

    Yes. The free plan includes 3 cron job monitors with intervals from 15 minutes up, alongside uptime, SSL, DNS, and the rest of Uptura's checks. Pro ($19/mo) includes 20 cron jobs checked as often as every minute, and Scale ($49/mo) includes 100.

  • Is Uptura a good Cronitor or Healthchecks.io alternative?

    If you only need to watch cron jobs, a dedicated tool like Cronitor or Healthchecks.io works well. Uptura fits when the same team also looks after websites: cron jobs, uptime, SSL, DNS, API, and performance checks share one dashboard and one alert stream, at a flat price instead of per monitor. Check-ins work the same way — one URL per job, no agent.

Free tool · no sign-up

Try the Cron Expression Generator free

Generate a cron expression, or translate one to plain English with its next run times.

Open tool

Know a job stopped before the data goes missing

Start free today — cron job monitoring is live alongside uptime, SSL, DNS, API, and more on one platform.

Free forever · no credit card required