You'll find out when you need it.
CronSignal alerts you when scheduled jobs fail — and shows you the actual error.
One line. No SDK. No SSH to dig through logs.
# Backup database every night at 2am
0 2 * * * /usr/local/bin/backup.sh && \
curl -fsS cronsignal.io/ping/abc123One line. If your job runs, we know. If it doesn't, you know.
Your server's cron daemon doesn't care if your script crashes halfway through. It doesn't care if the disk filled up, or the API timed out, or someone commented out the wrong line. It just... doesn't run the job. And doesn't tell anyone.
You find out when a customer asks why their report is missing. Or when you reach for a backup that doesn't exist. Or when the database you thought was being cleaned up is suddenly 500GB.
Most monitoring tools alert you when something fails. But cron jobs don't "fail" in a way those tools can see. They just don't run.
That's why heartbeat monitoring exists. And that's what CronSignal does.
Your URL: cronsignal.io/ping/x7k2m
No ping by 2:30 AM? You get an email. Immediately.
Your checks, their status, full history. No clutter.
Click any check to see the full details
Created Dec 15, 2025
https://api.cronsignal.io/ping/abc123xyz
curl -fsS https://api.cronsignal.io/ping/abc123xyz
Email, Slack, Discord, Telegram, or webhooks — within 60 seconds of a missed ping. Recovery alerts when it's back.
Your backup takes 20 minutes? Set a 30-minute grace period. No false alarms.
Your ping hits Cloudflare's edge in <50ms, anywhere. Not a single server in Virginia.
Every check-in logged. See patterns. Debug issues. Know exactly when things broke.
It's a URL. Curl it. Wget it. Call it from Python, Ruby, Node, Go, PHP, Bash. Whatever.
Linux cron, systemd timers, Kubernetes CronJobs, GitHub Actions, Laravel, Django. Yes.
Connect Claude Code, Cursor, Codex, or any MCP-compatible AI tool. Create, list, and manage monitors with natural language — without leaving your terminal or IDE.
Other monitoring tools tell you something broke. Then you SSH in, dig through logs, and try to figure out what happened. CronSignal captures your job's output. When something fails, you see the actual error — right in your dashboard.
Starting backup...
Connecting to postgres://localhost:5432/prod
Error: FATAL: password authentication failed
for user "backup_user"
Backup failed.
No SSH. No log hunting. Just the answer.
# Capture output and send with ping
0 2 * * * /backup.sh 2>&1 | \
curl -fsS -X POST --data-binary @- cronsignal.io/ping/abc123Instant notifications when jobs fail. Recovery alerts when they're back.
Always on
Team channels
Server alerts
Instant messages
Any service
Connect CronSignal to Claude Code, Cursor, Codex, or any MCP-compatible tool. Query monitor status, diagnose failures, and manage checks without leaving your terminal.
Yes, Daily Backup had several errors:
| Time (UTC) | Status | Error |
|---|---|---|
| 02:31:54 | ✗ | Connection refused |
| 02:31:35 | ✓ | Job completed successfully |
| 02:18:01 | ✗ | Database connection failed |
3 out of 5 recent pings failed. The errors suggest database connectivity issues — likely the database was temporarily unreachable.
Most monitoring tools charge per monitor. We don't.
Get started with essentials
For serious monitoring
Start free, upgrade when you need more
Meanwhile, at other monitoring tools:
Same features. Flat price. Your bill shouldn't scale with your infrastructure.
./backup.sh 2>&1 | curl -X POST --data-binary @- cronsignal.io/ping/xxx. We capture up to 100KB of output per ping, plus exit codes. View it all in the dashboard or ask your AI assistant to diagnose it.
Find out for sure.
We'll send you a magic link. No password to forget.
Already have an account? Log in
Also monitoring APIs or websites?
UptimeSignal checks your endpoints every minute and alerts you when they go down.
Check it out →