Skip to content

Latency tests

Open Xray → Latency tests. Choose Cloudflare, Google or a custom HTTP/HTTPS URL and a 3–8 second timeout. Defaults are Cloudflare and 5 seconds.

After changing the test URL or timeout, returning to Xray refreshes its summary immediately. In Servers → Nodes, Test servers tests the testable ordinary nodes matching the source, search and favorites filters at the moment you press it. Changing filters later does not change that request or hide its Cancel action; completed results are kept, the current batch finishes and cancellation skips later batches. Testing does not change the connection selection.

The measurement is a node’s HTTP HEAD request up to response headers, not ICMP ping or throughput. Exit-region requests and their setting have been removed. Provider-managed complete configurations are not measured as individual outbounds; their own Observatory remains provider-controlled.

When VPN is running

Manual node and App-managed subscription tests warn that the request may traverse the current VPN and the result may be inaccurate. Cancel or continue once per action; continuing does not stop or change VPN. Starting, stopping and a failed state that may still be running also require confirmation. Cancelling, closing the dialog or leaving the page submits no test.

Automatic tests after startup, import or subscription refresh do not show this dialog and may also be affected by VPN. The path may change while work is queued.

Queue and cancellation

Automatic, subscription and single-node requests share a FIFO queue. Each batch contains at most five ordinary nodes; nodes in a batch can run together. The source detail shows Test, Cancel or Cancelling for its own request and rejects duplicate submissions. Cancel skips that source’s pending work after the current batch and leaves other sources and VPN running. Import completes without waiting for queued tests.

A successful test is not a prerequisite for connecting. Unknown, failed and timed-out nodes remain selectable; startup does not wait for this queue.

Runtime least-latency routing probes only active proxy chains, uses a separate result stream, and never overwrites these manual latency results. Routing settings · Latency labels

Last updated on