Crontap Uptime Monitoring
Uptime monitoring built into Crontap.
Point Crontap at a public URL. It probes it on an interval, from every minute to once a day. You get 90 days of history, daily uptime bars, and an email when it stops responding.
- Fastest probe interval
- 1 min
- Probe history kept
- 90 days
- Counts as up
- 200–399
What it is
The probe that notices before your users do
Uptime monitoring lives in the same dashboard as your scheduled jobs, because the question is the same: is the thing that should be working still working? Crontap probes the URL you give it on a fixed interval and records every result.
A probe is a plain anonymous GET request. A status between 200 and 399 is up. Timeouts, DNS failures and connection errors are down. A single blip does not page you: a monitor only goes down after a set number of consecutive failures, two by default and adjustable from one to five.
When a monitor goes down, you get an email. When it comes back, you get another. Down alerts respect a per-monitor cool-down, so a flapping service cannot flood your inbox. Recovery emails always go out immediately.
History is kept for 90 days. You see it as daily uptime bars over 7, 30 and 90 day windows, with the last 100 probes listed one by one when you need the detail.
Why it is built this way
The ideas behind it
- 01
Intervals that match the stakes
Nine steps from one minute to twenty-four hours. Check a payment webhook every minute and a marketing page once a day, on the same account.
- 02
Thresholds instead of hair triggers
Require up to five consecutive failures before a monitor is marked down. Brief blips stay out of your inbox.
- 03
History you can read
Ninety days of probe results as daily bars, with the last hundred probes listed raw when you need the detail.
- 04
Alerts with a volume knob
A per-monitor cool-down caps how often down alerts can fire. Recovery notices ignore the cool-down.
Flow
How it works
- 01
Add a URL
Give Crontap a public HTTP or HTTPS URL and pick how often to probe it.
- 02
Crontap probes on a tick
Every minute, Crontap sends the probes that are due. It validates the target first and follows redirects.
- 03
Failures accumulate
Consecutive failures count toward your threshold. Cross it and the monitor goes down and emails your notification list.
- 04
Recovery closes the loop
The next successful probe marks the monitor up and sends a recovery email. Every incident gets an end as well as a start.
Specifics
What you get
- Probe any HTTP or HTTPS URL with an anonymous GET request
- Nine interval options, from every minute to every 24 hours
- A 200–399 response counts as up. Timeouts and network errors count as down.
- Set the failure threshold: 1 to 5 consecutive failures before a monitor is marked down
- One successful probe marks the monitor up again and sends a recovery email
- Daily uptime bars over 7, 30 or 90 day windows, plus the last 100 raw probes
- A per-monitor alert cool-down, so one bad afternoon does not become fifty emails
- Run a probe by hand at any time, and pause a monitor without losing its history
Scope
Version one is deliberately narrow. Probes run from a single region. Alerts are email only. There is no public status page, keyword matching or SSL expiry check yet.
Captured from the live site
What it looks like
Captured from crontap.com/uptime by this site's asset pipeline, with navigation and overlays removed.
Straight from the source
“Uptime monitoring built into Crontap.”
Built-in uptime monitoring next to your scheduled jobs. Ping any URL from 1 minute to 24 hours, see 90 days of history, get alerted the moment it goes down.
Read from crontap.com/uptime on 2026-09-08
Go deeper