Use case
Stop running a separate uptime tool. Monitor and schedule on one dashboard.
Crontap pings any URL on your cadence, charts 90 days of history, and sends a Resend email the moment a probe goes red. It lives next to the cron schedules you already manage.
Free plan · no credit card required
The problem
Why this is painful without the right tool
- Two dashboards to glance at every morning, two SaaS bills, two notification inboxes wired to two different on-call rotations.
- Your uptime tool can monitor the homepage but doesn't reach the endpoints behind your VPN or auth, and adding a public probe just for monitoring is a security smell.
- Cron heartbeat tools tell you a job didn't run; uptime tools tell you a URL stopped responding. You probably need both, but you don't want two dashboards.
- Free tiers on most uptime tools are loose, but the upgrade lane to 1-minute checks is a separate purchase you're already paying for elsewhere.
The fix
How Crontap solves it
The full feature lives at /uptime — including the bar-chart preview, the comparison vs UptimeRobot / Better Stack / Pingdom, and the FAQ. This page is the monitoring-shaped lane into it.
*/1 * * * *The setup is the smallest possible: paste a URL, pick an interval, done. The default failure threshold is two consecutive failed probes before the monitor flips to down, configurable up to five per monitor. Recovery is a single successful probe.
Down and recovered emails route to the same sendToEmails list you already configured in Settings for failed scheduled jobs, so there's no second inbox to manage. For the deeper patterns — per-route latency tracking against internal endpoints, or pairing schedules with an external dead-man check — the related use cases below still apply.
Pricing: free plan ships one monitor at a 1-day cadence; Pro unlocks ten monitors and the full ladder down to 1 minute. Same Pro tier as scheduling, no separate add-on.
FAQ
Common questions
- What protocols are supported in v1?
- HTTP and HTTPS GET requests with a 30-second timeout. Anything outside HTTP 200–399 (or a network error / timeout) counts as a failed probe. HEAD method, custom expected status codes, keyword/regex body matching, and response-time SLAs are on the roadmap.
- How does this differ from cron heartbeat checks?
- Heartbeats prove a job ran by the absence of a missed ping — the right tool when the failure mode is silence (a job that doesn't fire at all). Uptime monitors actively poll a URL and tell you it stopped responding correctly. For a single API the answer is uptime; for a daily reconciliation that might silently never fire, pair the schedule with a heartbeat.
- Can I monitor URLs behind auth?
- Not in v1. Probes are anonymous GETs from a single region. Custom headers (so you can pin a bearer token) are on the roadmap.
- Where do alerts come from?
- Resend, sent to the same global notification email list configured in Settings → Notifications. The 'Down' email lands on the up→down transition; a 'Recovered' email follows once a probe succeeds again.
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