← Back to help centre

Monitoring basics

How WebCheck calculates uptime

Understand completed-period uptime, current availability, degraded checks, incidents and newly added sites.

WebCheck calculates availability from completed runs for enabled checks on enabled targets. Each completed run counts once: Passed and Degraded count as available, while Failed and Blocked count as unavailable.

How to read the percentage

The percentage is based on recorded check runs, not a minute-by-minute measurement. If you monitor several check types, each run contributes one result even when those checks run at different intervals. A failed DNS or TLS check can therefore affect the figure as well as a failed HTTP check.

Why a new site shows current availability

WebCheck labels the result Current availability until the site has existed for the full reporting period, such as 24 hours, 7 days or 30 days. After that, it shows a completed-period percentage based on the runs it has recorded.

A failed run is not always an incident

Eligible connection failures on HTTP checks are retried within a bounded window. WebCheck then applies the target’s consecutive-failure threshold before opening an incident. An HTTP error response is evaluated as a result; it is not retried as a connection failure.