Uptime monitoring interval planner
Free, no sign-upCompare check intervals and see how long an outage could go unnoticed.
Check intervals
Alert timing
Expected time to alert
Assumes a persistent outage and on-time checks. Actual alerts can take longer; short outages may be missed.
- Estimated alert range
- Checks in period
Timing breakdown and other intervals
- Expected alert at current interval
- Checks vs current
Current and proposed alert times
| Interval | Alert delay: average / longest in model | Checks |
|---|
Calculation and limits
Expected alert delay = interval / 2 + (consecutive failures − 1) × interval + additional delay. Modelled worst case = consecutive failures × interval + additional delay.
This assumes a persistent outage starting at a uniformly random point between punctual checks. Short outages may never trigger an alert. Checks that run late, retries and notification failures can exceed the modelled worst case.
Volume counts a check at the start of the planning window, then each interval before the window ends, for every endpoint and location. Confirmations use scheduled checks; retries or extra requests are not included. Faster detection is not faster recovery, recovered revenue or a prediction of false alerts.
Your answers and calculations stay in your browser. Shared links include your inputs. Only share information you are happy to pass on.
A little more detail
Checking faster is only part of alerting faster
The check interval sets the wait for the next observation. Extra confirmation adds time, and the final alert also depends on timeouts and notification delivery.
Work out your downtime allowanceWhy is the average wait half the interval?
For outages that begin at a random point between evenly spaced checks, the first-check wait averages half the interval. It can be almost zero or nearly the full interval. That is a timing model, not a measured alert-delivery promise.
Will a shorter interval catch every outage?
No. A short outage can start and end between checks. Requiring consecutive failed checks can also miss incidents that recover before confirmation. Independent checks and timeouts affect the real behaviour.
Does checking more often create more false alarms?
It creates more observations, but there is no universal false-alarm rate. Use your actual monitoring history to judge noise. This planner does not guess a financial saving or false-alert count.
Keep an eye on your website
Let Scavo do the regular checks.
Get uptime alerts and weekly health checks, with findings you can send straight to your web team.