Monitor intervals and timing
Configure how often to check your services.
Overview
The check interval sets how often a monitor runs. Short intervals catch outages faster but produce more data and hit the target more often.

Available intervals
The interval dropdown is the same for every monitor type: HTTP, Ping, TCP, gRPC, Docker, SSL, hardware and PageSpeed:
| Interval | Best for |
|---|---|
| 15 seconds | Ultra-critical services |
| 30 seconds | Critical production services |
| 1-5 minutes | Standard production monitoring |
| 10-15 minutes | Less critical services |
| 30 minutes | Development/staging environments |
| 1 hour to 1 day | Low-traffic pages, daily PageSpeed audits, anything where a slow cadence is fine |
The dropdown runs from 15 seconds up to 1 day (15 s, 30 s, 1 m, 2 m, 3 m, 4 m, 5 m, 10 m, 15 m, 30 m, 1 h, 2 h, 6 h, 12 h, 1 day).
If none of the presets fit, type any number into the interval field and pick seconds, minutes, hours or days, custom values are supported. The minimum accepted interval is 10 seconds.
PageSpeed monitors
PageSpeed monitors share the same dropdown, so intervals up to 1 day are available. PageSpeed audits hit Google's PageSpeed Insights API on every run. Set an API key (Settings > Integrations) and choose the longest interval that meets your needs.
Choosing an interval
Shorten it when
The service is mission-critical, the site is high-traffic enough that minutes of downtime are expensive, or you need an incident raised before a customer notices.
Lengthen it when
The target rate-limits you, the check is expensive (PageSpeed audits hit Google's API on every run), or brief glitches are producing noise you keep dismissing.
Start with 3-minute intervals for most monitors. Decrease to 1 minute only for your most critical services.