> ## Documentation Index
> Fetch the complete documentation index at: https://docs.axottle.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Conditions and severity

> Statuses of individual samples, summary states of nodes and circuits, severity levels and quorum logic of input nodes.

The health system works with two layers of status: the result of a single sample (as shown by a particular test) and the summary state (nodes, connection circuits, the entire fleet), the aggregate state is obtained by combining samples according to the principle of “worst-significant”, this page explains what each status means and how the samples form the overall picture.

> [!NOTE]
>
> For whom: Panel Administrator, SRE. Required rights: Administrator session.

## Status of individual samples

Each inspection returns one of the statuses below: "not applicable" status means that no verification is required for this purpose.

| Status | What is | Nature |
| - | - | - |
| `ok` | Test passed | Success |
| `degraded` | Partial degradation, works with reservations | Warning |
| `failed` | Check failed | Failure |
| `timeout` | Response not received in allotted time | Failure |
| `unreachable` | Target Unattainable | Failure |
| `dns_failed` | Failed to resolve domain name | Failure |
| `port_closed` | Port closed / connection denied | Failure |
| `not_required` | Inspection intentionally not applicable to this purpose | Information, no failure |
| `absent` | Service not installed; treated with runtime | Information |
| `skipped` | Check missed (e.g., basic achievability no longer passed) | Information |
| `not_implemented` | Check for this case is not yet implemented | Information, service status |
| `unsupported` | Verification is not applicable for this type of target | Information |
| `unknown` | Data not yet available | Neutral |
| `external_probe_unavailable` | No available external provider for regional testing (external inspection level only) | Information |

> [!NOTE]
>
> The statuses `not_required`, `absent`, `skipped`, `not_implemented`, `unsupported` are service states and do not increase the severity of nodes.

## WARP status

For WARP, a separate set of states is used: `installed`, `missing`, `port_closed`, `unreachable`, `pending_install`, `not_required`, `unknown`. If WARP is not required by the circuit assembly plan, the status is `not_required`, not a failure.

## Summary states

Sample statuses are reduced to the general state of the node, circuit or entire park:

| State of | What is | What is | |
| - | - | - | - |
| `healthy` | Proven and all right | Nothing; maintain | surveillance |
| `degraded` | Partial capacity loss or | consultative problem Diagnose without panic: some input nodes are not available (but ≥ half live), problems on transit / route, no NET\_ADMIN, agent in degraded. See [Runbook' and](https://docs.axottle.com/en/health/runbooks.md) | |
| `critical` | User Traffic Affected | Runbook: gateway unavailable, input node quorum lost, node disabled in Remnawave, persistent | through-sample failure |
| `unknown` | Data is not yet - it is **ne** failure | Wait for the first run or run manual check | |
| `unsupported` | There is nothing to check (for example, no nodes are assigned to the circuit) | Assign nodes or consider the state expected | |

## Severity and incidents

The level of severity of the incident is deduced from the consolidated state:

| Consolidated state/event | Severity incident |
| - | - |
| `critical` | `error` |
| `degraded` | `warning` |
| Transition to `healthy` (restore) | `info` |
| `*.failed` | `error` |

## How the state of the node develops

The panel combines three signals - the state of the node in Remnawave, the results of health checks and the heartbeat of the agent:

* **critical** — Remnawave reports that nodes `disconnected`; **or** agent `offline`; **or** network reachability `unreachable`/`failed`.
* **degraded** — Achievability `timeout`/`dns_failed`/`port_closed`; **or** agent `degraded`; **or** service `failed`/`timeout`/`degraded`.
* **healthy** - achievability **and** service `ok`/`not_implemented` or service `ok` with an online agent.
* **unknown** is nothing definite yet.

> [!TIP]
>
> The inaccessibility of the SSH port is fixed for diagnosis, but in itself does not increase severity if the input ports and agent are available. The failure of the input ports translates the node and affected circuits into degradation.

## Freshness and Flow version

The draft, the version used and the observed health are displayed separately. The checks relate to the working image; the presence of the applied version does not make Flow healthy without sufficient checks. The absence of a proven client pass can leave the state of `unknown` or `degraded` even with available nodes.

The late result of the old version does not replace the current one. Use the latest information from the current version to restore it. [Diagnosis of Flow](https://docs.axottle.com/en/connection-units/diagnostics.md).

## Quorum of input nodes at the connection scheme

For the connection scheme (Flow), the summary takes into account the roles of nodes - input (entry) and transit (transit) - and works by quorum:

| Condition | Outcome |
| - | - |
| Gateway unavailable | **critical** |
| Nodes | **unsupported** (nothing to check, it is not degradation) |
| Persistent failure of the through sample from the node | forced **critical** |
| All input nodes are healthy, nothing drops | **healthy** |
| All entrances are healthy, but there are failures on the transit/route | **degraded** (additional end-to-end checks and minimum number of healthy pool participants) |
| Healthy input nodes - 0 | **critical** |
| Healthy input nodes 50% or more | **degraded** |
| Healthy input nodes less than 50% | **critical** |

> [!NOTE]
>
> Example: in a balanced circuit with three input nodes, the failure of one of them gives **degraded**, and not **critical** - the remaining two hold more than half the capacity.

Losing the required minimum number of healthy transit pool participants can elevate Flow to **critical**, even if input nodes are available.

## Summary throughout the park (global dashboard)

The global state on the dashboard becomes **critical** when the node, circuit or route becomes `critical`. The offline agent maximizes the state to `degraded`; the availability of the node is separately checked by network samples. The state of `healthy` requires at least one healthy entity and no `degraded`/`critical` signals; the empty installation gives `unknown`.

## Causes of failure (classification “why”)

In addition to status, the system captures the cause: the unavailability of the gateway, the fall of the input or transit node, the stop of the service part, the missing agent, the configuration drift, the incorrect conditional connection, the absence or closed WARP port, the inaccessibility or refusal of the authorization of the proxy, the inaccessibility of the source of the CDN, the DNS mismatch, the expired TLS, the failure of the external regional sample, the waiting for target selection and “unknown.” [Reconstruction](https://docs.axottle.com/en/health/self-heal.md).

## Verification

Open **Health** and press **Run check**. Summary status and causes are displayed on the dashboard cards.

## Rollback

Change operations (confirmation of recovery action, node suppression) and their rollbacks are described on the pages of [Restoration](https://docs.axottle.com/en/health/self-heal.md) and [Node](https://docs.axottle.com/en/health/suppression.md) Suppression.

## Typical errors

> [accordion] Accepted the unknown for failure.
>
> `unknown` means "no data yet," not "bad," and after the first run of checks or manual run, the state will be clarified.

> [accordion] Expected critical, and the scheme degraded
>
> Partial loss of inputs can be degraded when the quorum is saved, but the loss of the required minimum of pool participants or sustained end-to-end failure can be critical; see the reason for the particular check.

> [accordion] Offline agent, and dashboard's not red.
>
> That's what it's designed to be: an offline agent doesn't raise the global state above degraded. The node's real inaccessibility will be independently demonstrated by its reachability tests.

Linked pages: [Levels of checks](https://docs.axottle.com/en/health/probes.md), [Dashboard health](https://docs.axottle.com/en/health/dashboard.md), [Recovery](https://docs.axottle.com/en/health/self-heal.md), [Node Life Cycle](https://docs.axottle.com/en/nodes/lifecycle.md).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.