Verify the current egress path

An enabled rule alone does not prove that traffic used the intended path. Check the rule, node, and public result in that order.

What you should confirm

• The intended rule matches the test device.
• The target node or group is healthy.
• The public IP and region match the selected egress.
• A control test without the rule produces the expected difference.

1. Check the routing rule

Confirm the device IP or subnet is the one used by the test device. Check that the rule is enabled and that its target is the expected node, group, WAN, VPN line, or direct path. Look for another broader rule that may win first.

2. Check node status

Run a node diagnostic and confirm that the selected node is online. If the target is a node group, inspect the members and the active scheduling policy. A group can select a different member after a health check or failure.

3. Query the public IP from the test device

Use a public IP service from the test device, not from the router management page. Record the IPv4 address, region, and time. When DNS behavior matters, also check the resolver location.

4. Run a control test

Temporarily disable the test rule or use a second device without the rule. Compare the public result with the routed device. Restore the rule and repeat once if the first result was cached.

Unexpected result

Follow no routing or no internet access. Avoid changing DNS, proxy mode, node group, and rule order simultaneously; otherwise the next result cannot identify the cause.