Uptime.com issues alerts to users containing technical details of the downtime incident/check failure.
We recommend users configure checks with at least three probe server locations, and sensitivity and retry values of 2.
We will assume these settings as we outline the conditions that affect when you will receive alerts.
Sensitivity and Special Cases
Uptime.com will issue an alert when the number of probe servers reporting DOWN matches the sensitivity set for the particular check. Each probe server will retry its check based on the number of retries configured.
When using 3 or fewer locations, a check will return to UP status once all locations have returned to UP status. When using 3 or more locations with a sensitivity of 3 or higher, the check will return to UP status once all but one location has returned to UP status.
Uptime.com will also issue a warning to you when only one probe server location has been down for 3 days or longer.
See our documentation on sensitivity, retries, and timeouts for more details. Please note that Group Checks do not utilize sensitivity, retry, or timeout conditions. Please note that Group Checks do not utilize sensitivity, retry, or timeout conditions.
Use Case: HTTP(S) Check With 3 Locations and Sensitivity and Retry Values Set to 2
When a single probe server location reports as DOWN, it will retry its operation. If only one location goes down then no alert is issued as our sensitivity is set to 2. However, the failed location’s status will be visible in your check’s real-time analysis screen.
If a second probe server fails before the first failed location recovers, Uptime.com will issue an alert (as there are now 2 failed locations).
Uptime.com will issue additional alerts to any contacts you have assigned to the check’s escalations settings.