Uptime
Cron Job Monitoring

Know when a scheduled job doesn't run

Monitor scheduled tasks and background jobs with heartbeat pings. Get alerted when a job is late or misses its window entirely.

View Pricing
Heartbeat pingsCron expressionsLate/missed detection
Screenshot of the Uptime dashboard: a sidebar listing HTTP, DNS, and TCP monitors, cron jobs, alerts, maintenance, and status pages; summary cards for monthly ping usage, overall uptime percentage, and the slowest endpoint; per-type counts of monitors up and down; and a table of HTTP monitors with latency trend sparklines and status badges
99.9%

Uptime Target

<60s

Alert Latency

24/7

Monitoring

365d

Retention

Deep Dive

Everything you need

A closer look at what you get, from the first check to the alert that reaches you.

Simple ping URL

Your job calls one URL when it completes — no SDK required.

Cron-aware scheduling

Uptime parses your cron expression and knows exactly when to expect a ping.

Grace periods

Allow jobs a little slack before marking them late.

Healthy → late → missed

A clear state machine so you always know a job's current status.

Get started

How it works

Three steps from an empty dashboard to checks that run on their own.

Create a cron job monitor

Enter the schedule as a standard cron expression.

Call the ping URL

Add one line to your job that pings the URL on completion.

Get alerted if it's late

Uptime tracks expected run times and alerts on missed pings.

FAQ

Frequently asked questions

The questions people ask most before they start monitoring.

Do I need an API key to ping in?

No — the cron-job ping endpoint is public and rate-limited, so a single line in your job is enough.

What happens if my job runs a bit late?

A grace period absorbs normal variance before the job is marked late, then missed.

Start monitoring your services

Create your first monitor in under 2 minutes. No credit card required to start.