Uptime checks: regions, intervals and degraded thresholds

Three settings shape an uptime monitor: where it checks from, how often, and what "too slow" means.

Regions

CertSentry runs uptime checks from up to three regions across different continents. More regions buys you two things: a stricter quorum (a problem is only "real" when several vantage points agree, cutting false positives) and a clearer read on where latency comes from.

Check interval

The interval is how often the check runs. Pick the cadence that matches how quickly you'd want to know — a payment flow might warrant every minute, while a marketing site is fine at five. Faster intervals detect and confirm outages sooner.

Degraded threshold

A site can be up but unacceptably slow. Set a degraded threshold in milliseconds and CertSentry flags checks that pass but exceed it. Degraded results are tracked separately from failures, so a slowdown shows up as its own signal — an early warning before it tips into a real outage.

Advanced HTTP options

For uptime monitors you can also set:

• the request method (GET, POST, HEAD, …),
• custom headers (values are treated as secrets and masked in the UI),
• a request body,
• the expected status range,
• a keyword that must appear, or must not appear, in the response.

Together these let a single check stand in for a real user journey rather than just "did the server answer".