Know when a job
doesn't run.
One HTTP request at the end of the job. No ping on time, you get an alert.
&& curl -fsS https://watchcron.com/ping/<uuid>
Cron jobs, uptime, SSL certificates, domains, Cloud Cron and IP blocklists. One account, one alert setup, 22 channels to hear about it first.
Each job pings its own URL when it finishes. If the ping doesn't arrive on schedule plus a grace period, you get an alert.
Read more about cron monitoring →HTTP checks on your sites and APIs, as often as every 30 seconds.
Read more about uptime monitoring →Every monitor type uses the same alert setup, so a failed job and a down site reach you the same way.
Read more about alert channels →WatchCron reads the certificate on your domain and warns you ahead of the expiry date.
Read more about SSL monitoring →Show the state of your monitors on a public page, with incidents detected automatically.
Read more about status pages →WatchCron checks WHOIS expiry dates and reminds you before a renewal slips.
Read more about domain monitoring →Your jobs report in. WatchCron watches the clock and tells you the moment one goes quiet.
Add a ping to the end of the job. If it doesn't arrive on schedule, WatchCron raises the alarm. Anything that can make an HTTP request can report in.
# m h dom mon dow command0 3 * * * /opt/scripts/backup-db.sh && curl -fsS -m 10 --retry 3 https://watchcron.com/ping/<check-id> */15 * * * * /opt/scripts/sync-orders.sh
use Illuminate\Support\Facades\Schedule; Schedule::command('backup:run') ->dailyAt('03:00') ->thenPing('https://watchcron.com/ping/<check-id>');
<?php cleanupExpiredSessions();file_get_contents('https://watchcron.com/ping/<check-id>');
import cron from 'node-cron'; cron.schedule('0 * * * *', async () => { await sendHourlyReport(); await fetch('https://watchcron.com/ping/<check-id>');});
import requests sync_orders()requests.get("https://watchcron.com/ping/<check-id>", timeout=10)
func main() { if err := buildReport(); err != nil { log.Fatal(err) } http.Get("https://watchcron.com/ping/<check-id>")}
on: schedule: - cron: '0 2 * * *'jobs: build: runs-on: ubuntu-latest steps: - run: ./scripts/nightly-build.sh - run: curl -fsS https://watchcron.com/ping/<check-id>
services: sync: image: acme/sync-worker command: > sh -c "python sync.py && curl -fsS https://watchcron.com/ping/<check-id>"
Six monitors, one dashboard, one alert setup.
One HTTP request at the end of the job. No ping on time, you get an alert.
HTTP checks on your sites and APIs, as often as every 30 seconds.
When a job misses its run, a site goes down or a certificate is about to expire, WatchCron pings the channels your team already watches.
See all channels AMonitor api.example.com every minute, alert on Slack if down
Created HTTP monitor api.example.com — checking every 60s, alerts → #ops-alerts
What's been down in the last 24 hours?
All 12 monitors UP. Last incident: staging-api, 47 min ago, resolved automatically.
Connect WatchCron to your AI assistant through MCP. Create monitors, ask what's down and check incidents in plain words, right from the editor or chat you already use.
npx watchcron-mcp
For personal projects and testing.
For small teams and growing projects.
For teams running production infrastructure.
For organizations with many services.
Can't find it here? Write to us.