Crontap Uptime Monitoring
Uptime monitoring built into Crontap.
Point Crontap at a public URL and it checks 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.
What it is
Know when your site goes down before your users tell you
Uptime monitoring lives in the same dashboard as your scheduled jobs, because it answers the same question: is the thing that should be working still working? Crontap checks the URL you give it on a fixed interval and records every result.
A check is a plain GET request. A status between 200 and 399 counts as up. Timeouts, DNS failures and connection errors count as down. One blip will not page you: a monitor only goes down after a set number of failures in a row, two by default.
When a monitor goes down, you get an email. When it comes back, you get another. Down alerts have a cool-down per monitor so a flapping service cannot flood your inbox. Recovery emails always go out straight away.
History is kept for 90 days as daily uptime bars, with the last 100 checks 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 24 hours. Check a payment webhook every minute and a marketing page once a day, on the same account.
- 02
Thresholds, not hair triggers
Require up to five failures in a row before a monitor is marked down. Brief blips stay out of your inbox.
- 03
History you can read
Ninety days of results as daily bars, with the last hundred checks listed when you need the detail.
- 04
Alerts with a volume knob
A cool-down per monitor caps how often down alerts fire. Recovery notices skip 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 checks on a tick
Every minute, Crontap sends the checks that are due, following redirects along the way.
- 03
Failures add up
Failures in a row count toward your threshold. Cross it and the monitor goes down and emails you.
- 04
Recovery closes the loop
The next successful check 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 simple. Checks run from a single region and alerts are email only. There is no public status page, keyword matching or SSL expiry check yet.
Screens
What it looks like
A closer look at Crontap Uptime Monitoring.
From crontap.com/uptime
“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.
Go deeper