Every probe has a current status, worked out from its recent checks. The same five states apply to every probe type, so once you know them you can read any probe or status page at a glance.
The states
| Status | What it means |
|---|---|
| Up | Recent checks are succeeding and responding normally. The thing you’re watching is healthy. |
| Degraded | Still working, but not cleanly: recent checks are intermittently failing, or responses are slow. An early warning, before a full outage. For a Domain probe, it means the registration has entered the warn window you set. |
| Down | The check is failing. For HTTP and TCP probes, several checks in a row have failed — a bad response, a timeout, or a connection, TLS, or DNS error. For a Domain probe, the domain has expired, the registry lookup failed, or expiry is inside your critical window. |
| No data | No recent check has reported, so the current status is unknown — a probe that has only just been created, or one whose checks have stopped arriving. Not the same as Down: Uptimeprobe is saying it can’t tell, not that the service is failing. |
| Paused | The probe is turned off. It runs no checks and reports no status until you enable it again. |
How status is worked out
Status is computed from your recent checks each time it’s read, not frozen when a check runs. A service coming back healthy, or widening a Domain probe’s day thresholds, shows up right away, and the history re-colours to match. Each probe type has its own rule for Up, Degraded, and Down — see the HTTP, Domain, and TCP guides for the specifics.
When a probe changes state
Each move between Up, Degraded, and Down is recorded on your Alerts page, so you can see when a service broke and when it recovered. Paused and No data are treated as no signal: pausing a probe, or a quiet gap in checks, doesn’t create an alert entry.