Use case
Ping endpoints every minute, record response times, alert on drift.
Push the same health check at the same cadence from the same place. Every run is logged with status code, duration and response body, so the next time you need to ask 'is this slow today?' the answer is one query away.
Free plan · no credit card required
The problem
Why this is painful without the right tool
- Public uptime monitors are great for 'is the homepage up' but do not touch the three internal endpoints you actually care about.
- You want the p95 latency of one specific API route over the last week, and the monitoring tool will not give it to you cleanly.
- A simple curl in crontab on a VM works until the VM reboots, or until the cron line vanishes during a deploy and nobody notices for a week.
- When a check fails, you want the failure to land in email or a webhook, not in a log file you only check on Mondays.
The fix
How Crontap solves it
Crontap pings the URL on a schedule, records duration and status, and alerts when a run fails. Use it for the health checks your uptime tool does not cover: internal endpoints, endpoints behind auth, or ones that need a custom payload to actually exercise the code path you care about.
*/1 * * * *One concrete pattern from the dataset: a fleet-management customer running a per-minute device status feed in Europe/Warsaw. The schedule fires GET at the local minute boundary, the endpoint returns an aggregate of per-vehicle status, and Crontap records duration and response body for every run. When a run takes longer than expected three times in a row, the failure integration posts to a Slack webhook with the offending status, duration, and body.
Payload, headers and the verb are customizable per schedule, and Crontap records the response body, so you can see when the endpoint started returning an unexpected JSON shape, not just when the status went non-2xx.
FAQ
Common questions
- What's the shortest interval Crontap supports?
- Every 1 minute on paid plans. Free tier available for slower cadences. The dataset shows 52 jobs running at exactly minute cadence in real customer accounts; it is a real, supported floor.
- Does this replace my uptime monitor?
- No, complement it. Uptime tools excel at DNS and global edge checks across geographies you do not own. Crontap shines at per-route internal health pings you do own, with a payload, an auth header, and full response logs per run.
- Can I alert on body content, not just status?
- Today the product alerts on non-2xx. Body-content assertions are on the roadmap. For now, the cleanest pattern is to return the assertion outcome via your response code: 200 if the body looks right, 4xx or 5xx if it does not, then let Crontap's status-based alerting fire.
- How do I get notified when a check fails?
- Each schedule has an Integrations panel where you wire failure alerts to email / webhook (Slack / Discord / Telegram). The failure payload includes the run's status code, duration, and response body, so you can debug from the alert without opening the dashboard.
Ready to fix it?
Point Crontap at any URL. Pick any cron. Done.
WordPress, Shopify, Railway, Cloud Run, Vercel, HubSpot, Ghost, your own box. If it answers HTTP, Crontap can drive it on a clock you can read, in the timezone that actually matters, and page you when something breaks.
Free forever tier ・ No credit card required
/wp-cron.php?doing_wp_cron=1
Schedule
"every 5 minutes"
Next
in 23s