Latency and Stats
Use Tunna latency, loss, RTT, data usage, Active nodes, Top 10, and ZAP signals to choose a healthier proxy node.
Use this page after nodes are visible. It explains the measurements Tunna uses to sort nodes, choose Top 10, pick Active nodes, and make ZAP useful.
Latency, loss, data, and stats in plain language
Latency is Tunna's quick health check for a node. Think of it as asking, How fast does this node answer? Smaller numbers usually feel better.
Use these cards as a map of the visible labels in this view. Each card names one field, control, or status item and explains what it is for before you change it or rely on it.
The number
A latency value is a round-trip time: Tunna sends a small check to the node and measures how long the answer takes to come back.
Lower is better
A smaller time usually means the node is quicker to respond.
Average
The main number is a recent average, so one odd check does not tell the whole story.
Plus or minus
The value after the plus-minus sign shows how jumpy the recent checks are. A low, steady node is usually nicer than a low but jumpy one.
The dots
Dots are recent checks. They let you scan whether a node has been healthy, slow, or failing without opening a chart.
Green, yellow, orange, red
Green is fast, yellow is slower, orange is high, and red is a failed check. A failed dot is red immediately; it does not wait for several failures.
Gray placeholder
Gray appears only when Tunna has no recent dots to draw yet.
Probing and Timeout
Probing means Tunna is still checking or has no successful sample yet. Timeout means three recent checks failed in a row.
Opening stats
Tap the latency number or dots on a node row to open that node's Stats view. The bottom picker changes the chart range between Hour, Day, Month, and Year.
Latency chart
Latency is the wait. Lower points mean the node answers quickly; tall spikes mean slow moments.
Loss chart
Loss is missed answers. More loss means Tunna asked the node for a check and did not get a useful answer often enough.
Data Usage
Data Usage is the traffic counter. Sent is what leaves your device through the node; received is what comes back.
ZAP works best after checks are warm
ZAP chooses a good node using recent latency checks. On the main list it can choose from available nodes, and on a subscription row it chooses from that group. If the tunnel is off, failed, or disconnecting, ZAP can also connect after choosing.