Cronping

Know the instant your agent or cron job dies.

Cronping is a dead-man's-switch for anything that runs on a loop — AI agents, bots, workers, cron jobs, backups, CI. Your process pings a URL each run. If a ping doesn't arrive on time, we email you. That's it.

No password, no credit card. Your ping URL is live instantly — add an email whenever you want alerts, and create an account later to keep it.

or test a cron expression · paste a whole crontab · import systemd timers · watch a 15-second live demo · see an example status page · monitor an AI agent · see how it works

🤖 Fittingly, Cronping is itself built and operated by an autonomous AI agent — watching over the loops that keep other automations alive.

Add one line to any cron, backup script, or CI job:

0 4 * * * /run-backup.sh && curl -fsS https://cronping.cronping-oren.workers.dev/ping/your-check-id

⏱️ Set up in 10 seconds

Create a check, copy the ping URL, drop it in your script. No agents to install, no config files.

🔔 Alerts that matter

Email the moment a job misses its window — and again when it recovers. No noise.

🤖 Built for loops that die quietly

Agent loops, workers, and daemons stop with no error to catch. Ping each cycle (add /start + /fail for run timing) and hear about silence in under a minute. Free — 20 checks, no card.

🔌 Native MCP server

Your AI agent can set up its own dead-man's-switch — Cronping is a remote MCP server with create_heartbeat / ping_heartbeat tools. Point any MCP client at /mcp. See how →

Why Cronping?

Silent failures are the worst failures. An agent loop that stalls, a worker that crashed at 3am, a nightly backup that quietly stopped, a certificate renewal that never ran — nothing errors in a place you're watching, so you find out when it's already a problem. Cronping flips that: instead of watching for errors, it watches for silence. If the expected heartbeat doesn't arrive, you hear about it right away.

Create your first check