Latency tests
Open Advanced > Xray > latency-test settings.
Choose a timeout from 3–8 seconds and a test URL: Cloudflare, Google, or a custom HTTP/HTTPS address. The default is 5 seconds with Cloudflare.
The test measures the time for an HTTP HEAD request through a node to receive response headers. It is not an ICMP ping or a throughput benchmark.
Exit-region detection
Detect server exit region defaults to off, including for older preferences without this setting. When off, tests measure latency without sending a location request. Existing regions remain available for display, grouping and connection selection. Nodes with no previous region remain accessible by subscription.
Enabling detection makes an additional request through the node and significantly increases testing time. That request has its own timeout and is excluded from the displayed latency. A valid new region updates the cache; failed, missing or invalid region results retain the previous value. Latency is saved independently. A successful latency test with a region error shows an informational message rather than a latency failure.
The switch applies to manual and automatic tests. Saving affects subsequent tasks without reconnecting VPN; cancelling discards changes. A running task keeps the settings it read at the start. This switch does not change Smart Routing’s direct regions.
Warning while VPN is active
With VPN connected, manual tests of a node, subscription or location group ask for confirmation: requests may traverse the current VPN and latency may be inaccurate, so disconnect VPN before testing. Choose Cancel or Continue testing. The warning appears once per action, rather than for each node or batch. Continuing leaves the VPN connection in place. Cancelling or closing the dialog does not queue a test.
Confirmation is also required while VPN is connecting or disconnecting, or when a failed connection may still be running. The warning reflects the state when the action is submitted; the connection can change while a task waits or runs.
Startup tests, tests after imports or subscription updates, and tests for connection selection run automatically without a dialog. They share the same VPN-path limitation; their results are not guaranteed to represent a node’s independent latency.
Queue behavior
Automatic tests, subscription/location tests, and individual-node requests share one queue. Later requests wait, including repeated tests of a single node. Different subscriptions are not tested simultaneously. Each batch contains at most five nodes, which can be measured together.
The batch button on a subscription or location switches to Cancel. Cancellation skips pending work and stops after the current batch finishes; it does not interrupt unrelated requests.
New nodes are queued for testing after import. Finishing import does not wait for test results. Initial setup has no server-import or latency-test step.
No concurrent-count setting or automatic-test switch is exposed. A fast result means low delay to the chosen test URL, not guaranteed bandwidth or access to every website.