Push-based heartbeat monitoring for backups, syncs, exports, and scheduled tasks. If a client job does not ping on time, we alert you immediately.
No card required · 50 monitors free · No time limit
HEARTBEAT monitor · checked every 86400s
Push monitor · no target URL · expects your job to call /api/push/9f2c8b41…
Push endpoint
curl -X POST https://errordetector.eu/api/push/9f2c8b41-6d3e-4c7a-9f10-2b5e8a1d44c7
Drop this at the end of your backup script, cron job or scheduler. If it does not call in within the interval plus the grace period, you hear about it.
A late or missing check-in is an issue, never HTTP downtime — nothing was unreachable, a job simply did not run. Uptime for this monitor stays at 100%, and the alert still goes out.
Each feature earns its place by making the client relationship easier to protect: fewer surprises, clearer proof, and faster explanations when something changes.
Your cron job sends a simple HTTP request to your unique endpoint. No agent installation needed — works with any language and any platform.
Cron jobs often fail silently. With heartbeat monitoring, you can be sure your backup, sync, or data processing is actually running.
Set expected intervals from 1 minute to 24 hours. ErrorDetector automatically detects when a heartbeat is late or missing entirely.
Add one curl command to the end of your cron job. Done. Works with bash, Python, Node.js, PHP, and any other language.
Concrete moments from the feature: setup, the signal that matters, and the client-facing proof that makes maintenance feel easy and valuable.
Heartbeat setup · example data
The monitor hands you a push URL. The job calls it after it succeeds — nothing to install.
Expected every
15 min
Push URL
ActivePush URL
https://errordetector.eu/api/push/8f2c1b4d9e
In your crontab
*/15 * * * * /opt/acme/backup.sh && curl -fsS -X POST $PUSH_URL
Alert delay
Wait past the expected window before saying anything
Missed check-in · example data
A silent failure becomes visible without pretending a website went down.
Last ping
21 min ago
State
Issueacme-backup-nightly
Window of 15 min plus the 5 min delay closed at 02:41 UTC
Alert
"Heartbeat Missed!" delivered to Telegram and e-mail at 02:41
Uptime history
A late heartbeat is an issue — it is never counted as HTTP downtime
Recovery · example data
The job runs, the ping lands, the monitor recovers and the timeline explains the gap.
Recovered after
7 min
Monitor
Up02:41 UTC
Window closed with no ping from acme-backup-nightly
02:42 UTC
Telegram and e-mail alert delivered to the on-call contact
02:48 UTC
POST /api/push/8f2c1b4d9e received — backup finished late
Add the signal once, then let alerts, history, and reports build automatically.
Choose "Cron Job" as the monitor type and give your task a name.
You'll receive a unique URL like /api/push/8f2c1b4d9e.
Paste curl -fsS -X POST https://errordetector.eu/api/push/8f2c1b4d9e at the end of your script.
If the heartbeat is missing, you'll receive an alert immediately.
Instead of us checking your server, your cron job pings our endpoint after successful execution. If we don't receive that ping within the expected interval, we send an alert.
Absolutely. Anything that can send an HTTP request works: AWS Lambda, GitHub Actions, GitLab CI, Jenkins, Kubernetes CronJobs, and more.
If the heartbeat doesn't arrive, you'll receive an alert. Once your cron job pings again, the monitor is automatically marked as "up." You can also set up maintenance windows to prevent false alerts.
Combine uptime, SSL, domains, incidents, alerts, teams, and reports into one maintenance workspace.
An API monitor calls one endpoint with the method, headers, JSON body and auth y…
A DNS monitor asks a resolver for one record type — A, AAAA, CNAME, MX or TXT — …
A blacklist monitor asks the public DNS blocklists whether an IP address has bee…
Track every client domain expiry date and receive timely warnings before a renew…
Automatic incident detection, response notes, status updates, and reports so cli…
A keyword monitor loads one URL and searches the HTML the server returned for a …
Monitor SSL certificates and receive warnings well before they expire, so client…
Give maintenance clients transparency with a professional, automatically updated…
Invite your team, assign roles, and collaborate on monitoring, alerts, and repor…
Fifteen channels: chat, mobile push, on-call paging, or your own webhook. Mainte…
Start with cron job monitoring and build client trust with real data. Free, no credit card required.
Create free accountNo card required · 50 monitors free · No time limit