Hear about the backup that didn't run.
Your cron jobs, backups and workers ping a URL when they finish. If one goes quiet, you get an alert.
Some failures are silent. The nightly backup that stopped running in March. The invoice job that died after a deploy. Nobody notices until the day they need it. Heartbeats turn silence into an alert.
How it works
- Create a heartbeat and tell Pingerer how often the job runs (every 5 minutes, hourly, daily, weekly...) and how much grace to allow.
- Add one line to the end of your job that requests its ping URL.
- If a ping doesn't arrive in time, you're alerted. When the next one arrives, it's resolved.
0 3 * * * /usr/local/bin/backup.sh && curl -fsS -m 10 --retry 3 https://pingerer.com/hb/your-tokenReport failures too
Request the same URL with /fail on the end when the job knows it failed, and you'll hear about it straight away instead of waiting for the deadline.
Works with anything that can make a web request
Cron, systemd timers, Kubernetes CronJobs, GitHub Actions, Rails, Laravel's scheduler, Node, Python, Windows Task Scheduler. The heartbeats guide has copy-and-paste snippets for each.
More of what Pingerer watches
Uptime monitoring
HTTP, keyword, ping and port checks as often as every 30 seconds, confirmed from more than one region before anyone is woken up.
SSL & domain expiry
Reminders before your SSL certificate or domain registration runs out, plus broken certificate chains and wrong hostnames.
DNS change alerts
Pingerer keeps a copy of your A, AAAA, CNAME, MX, NS and TXT records and tells you when any of them change.
Email deliverability
Plain-English checks of SPF, DKIM and DMARC, so the emails your business sends keep arriving.
Find out what's broken before your customers do.
Add your first site in under a minute. Free, no credit card.