If your node list shows both latency and download speeds, don’t sort the results just yet. If a connection fails, use Tcping and the proxy latency test to distinguish an unreachable port from a failed proxy request. If downloads are slow, test throughput separately. This guide walks through repeatable comparisons and explains why a client test can succeed even when web pages won’t load in your browser.
What each test measures
Tcping: the node’s TCP port
Attempts to establish a TCP connection to the address and port in the node configuration. A successful result means the port accepted a connection during this probe; it does not verify proxy authentication or access a test URL. Even if the example port is 443, a successful TCP connection does not mean the subsequent TLS handshake will succeed. This test cannot determine whether a configuration using UDP transport is working.
Use it to check whether a TCP-based node’s entry point is reachable from your current network.
Proxy latency: access a test URL through the proxy
RecommendedThe core makes a request using the configuration being tested. The result depends not only on the node’s entry point, but also on the proxy handshake, the route from the exit node to the test site, and the site’s response. It is not a pure network round-trip time to the node, nor the time a browser takes to render a full page. The exact timing boundaries depend on the client version.
Use it to check whether the proxy route can complete a request, then compare response times.
Download test: throughput during the test window
Downloads a test file through the proxy and measures how much data transfers over time. The test server’s speed limits, other downloads on the same network, and fluctuations along the route can all affect the result. A short-lived peak does not guarantee sustained download speeds.
Use it when a node connects successfully but large downloads or sustained transfers are slow.
Low latency but slow downloads: compare under the same conditions
Select a node in the list, then right-click to find the commands for Tcping, proxy latency, and speed tests. The wording may vary slightly between versions. Note the v2rayN and core versions you’re using; don’t assume menus or test defaults from another version match your current interface.
- Pause cloud syncing and background downloads first. Keep the device, network connection, and test URL the same. Test one configuration at a time to prevent simultaneous tests from competing for bandwidth.
- Run the proxy latency test three times for each configuration, recording how many succeed and how long each takes. If all three succeed, compare the median. If any time out, keep a count of the failures. Don’t record only the fastest result or count failures as 0 ms in an average.
- Then compare throughput using the same download source. Wait for traffic to subside between rounds. If the results are close, retest in reverse order to avoid mistaking changes in network conditions over time for differences between nodes.
| Configuration | TCP connection | Proxy latency (3 tests) | Download throughput |
|---|---|---|---|
| A | 38 ms | 185 ms, 210 ms, timeout | 2.4 MB/s |
| B | 76 ms | 220、230、245 ms | 8.0 MB/s |
Retest B first with these results
Although A connects over TCP faster, one of its proxy latency tests timed out. If you’re concerned about occasional page hangs, retest B first since all three tests got a response. If downloads are your priority, check whether B’s advantage holds over multiple rounds. If the interface displays decimal MB/s, 8.0 MB/s is about 64 Mb/s. Don’t compare the number 8 directly with a broadband plan rated at 100 Mb/s.
Proxy latency test failures vs. app access problems
Choose checks based on where the failure occurs
Port reachable, but proxy test fails
- Retest that configuration by itself, then check the client logs for the time of the test. Determine whether the test core failed to start, the proxy handshake failed, or the target timed out before responding.
- If you see a TLS certificate or name error, check the server name required by the configuration and your system clock. Don’t bypass the error by disabling certificate verification.
- If several previously working configurations fail against the same test URL, try another known-good, lightweight HTTPS URL to check whether the test target is the problem.
Proxy test succeeds, but apps still can’t connect
- Make sure the main window is using the configuration you just tested. Testing a node in the list and routing your everyday traffic through it are two different things.
- If you rely on the system proxy, check that it’s enabled and that the app follows the system settings. If you configured a proxy manually in the app, go to Settings → Parameter Settings and check the current local listening port and proxy type. For example, use
127.0.0.1:10808only if that’s the address and port your configuration actually uses. - If only certain websites have problems, check the routing rules and DNS for the domains you’re actually visiting. Being able to access the test URL doesn’t mean traffic to the site you need uses the same outbound route.
Change one setting at a time, then rerun the same test. If you switch networks, cores, and test URLs all at once, it’s hard to tell what fixed the problem even if it starts working again.
Common questions about v2rayN test results
Proxy latency shows -1. Does that mean the node is dead?
Treat it as no valid latency result for this test, not as a unit of latency. Test that node on its own and check the logs from the same time. If several configurations fail together, first check the test target and whether the core started. If only this configuration keeps failing, review its settings and protocol parameters.
Tcping times out, but the proxy latency test returns a result. Which should I trust?
To determine whether a proxy request can get through, use a valid proxy latency result. First confirm both tests were run just now against the same configuration, then check whether it uses TCP or UDP transport. The tests measure different things, so their results don’t have to match.
The speed test shows 0. How can I tell if it hasn’t started or is just very slow?
Wait for the test to finish and check the logs for connection, request, or read timeouts. If the proxy latency test also fails, troubleshoot connectivity first. If it succeeds but the download test returns no valid reading, pause other network traffic and retry with that configuration on its own. Then compare with another download source you can control.
It’s slower at night than during the day. What should I record before switching configurations?
At both times of day, use the same network and test target to record three proxy latency results and download speeds. Include a known-good configuration for comparison. If both configurations slow down at night, first rule out competition for bandwidth on your home network, then compare with another network. If only one configuration stays slow, focus on its route.