Node Offline

What are Node Offline alerts?

According to the Flow Operation Documentation, nodes that are not online can cause severe degradation of network performance and will be subjected to slashing of rewards. The Flow network monitors the online status of all nodes on the Flow network. The node offline alerts are designed to help node operators avoid downtime and reduce slashing. Minor ‘blips’ in node online status will not trigger alerts as long as they are short-lived (in the order of seconds).

Please note, the node agent can remain online whilst the node offline alert is firing. The status of the node is determined by the Flow network rules, rather than the status of the node agent. In this case, it’s likely that the issue is caused by latency in node response time rather than internet connectivity. Please investigate the other factors outlined in the ‘How do I resolve it?’ section below.

How are Node Offline alerts triggered?

The Flow network monitors the online status of all nodes on the Flow network. When a node’s status changes from ‘online’ to ‘offline’, and this status is maintained for more than 10 minutes, then a ‘Node offline’ Alert will be triggered. This status is checked every minute by our platform.

What notifications will I receive?

For each period that one of your nodes is offline for 10 minutes or longer, a single alert will be triggered. You will then receive a follow-up clearing alert when the node comes back online.

How do I resolve it?

A ‘Node Offline’ alert is most often caused by the node not having internet connectivity, it’s worth checking if the node has an active internet connection. If the node has an active internet connection, other issues that may be impacting the nodes ability to process and respond to incoming requests can be found below:

• Check that the clock of your node has not drifted.

• Check that key system-level metrics (e.g., CPU usage, RAM usage, Disk Space) of your node exhibit normal behavior.

• Check that your node is configured to receive requests and respond to other nodes on the network.

• Check that your node meets the minimum requirements for hardware outlined here.

• Check that your node meets the minimum requirements for networking outlined here.