Get Tunna

Outbound List

Read and maintain the Tunna outbound list, including selected-node badges, subscription groups, latency dots, swipe actions, and ZAP.

487 words 3 min
Outbound Nodes, Subscription Rows, Latency

Use this page when the Outbound list already has nodes and you need to understand what each row, badge, dot, swipe action, and refresh signal means.

List signals at a glance

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.

Visible choices

These are controls, states, or measurements in the view. Read them as reference, not as feature claims.

Health donut

Shows how many nodes in a subscription group are fast, slow, failing, or unknown.

Count bar

Turns the same health mix into a compact bar so large subscriptions can be scanned quickly.

Status and fetch dots

Subscription dots separate normal status from active fetching, so you can tell whether a provider row is stale, failed, or being updated.

Selected badge

The selected-node badge follows the node Tunna will use for Proxy traffic, even when it sits inside a folded subscription group.

Using the list

Tap a node row to select it. A selected-node badge marks the node that Proxy routing will use. Tap the latency number or latency dots to open Stats. Local nodes have an info button for viewing and editing the node. Swipe local rows for Delete or Share, and swipe subscription rows for the available Delete, Share, or Update actions. The plus menu offers Node, Scan, and Paste.

Sorting does not jump on every check

The sort button cycles through Latency, Date, and Name, and each mode can be ascending or descending. Tunna keeps the visible order steady while checks arrive. When fresh checks would change the order, a small red dot means a pending sort is ready; tap the sort button to apply it.

Reading a subscription group

A folded subscription row summarizes the group without showing every node. It can show status dots, a fetching dot while Tunna refreshes, a health donut and count bar for node colors, the selected-node badge when the current node belongs to that group, expiry, and usage when the provider sends quota data. Tap the subscription row to unfold it and choose individual nodes.

Subscription groups can change after refresh

When a subscription updates, Tunna rebuilds that provider group from the fetched node links. Matching nodes keep stable identity where possible, new nodes are added, and removed provider nodes disappear from the group.

A healthy node lifecycle

  1. 1
    Import or create

    Bring the node in from a link, QR code, subscription, or manual entry.

  2. 2
    Name it

    Use a friendly name for important nodes so they stay recognizable later.

  3. 3
    Warm checks

    Let Tunna collect latency before sorting, choosing Top 10, or using ZAP.

  4. 4
    Connect

    Select the node and start the tunnel with simple routing for the first test.

  5. 5
    Maintain

    Refresh subscriptions, remove dead nodes, and update rules that point at removed subscription nodes.