How to Choose a V2Ray Server: Latency, Traffic Multipliers, Locations, and Protocols

Compare V2Ray servers by real connection latency, traffic multipliers, exit locations, and VMess, VLESS, or Trojan compatibility—not just one number.

At a glance

When a subscription includes multiple servers, first rule out entries your client cannot connect to, then verify each server’s actual exit location and traffic multiplier. Test the remaining options repeatedly on the same network. Finally, check them with the sites or apps you use and keep one primary server and one backup.

Test latency: Connect first, then compare

The server TCP latency shown in v2rayN measures how long it takes to establish a TCP connection to the server’s entry point. It does not confirm that the proxy can reach a target site. Real connection latency sends a request to a test address through the server, making it more useful for an initial check. Even so, each reading reflects just one request at that moment—not download speed or response times for every site.

  1. Keep test conditions consistent

    Use v2rayN on the same device and stay on the same Wi-Fi or wired network. Pause background downloads. Test every candidate against the same address, and don’t rank results from mobile data alongside results from desktop Wi-Fi.

  2. Run a real connection test

    In v2rayN’s main window, select a candidate in the server list, right-click it, and choose “Test server real connection latency.” The menu item may include the word “multiple.” Wait for the test run to finish before starting another. Record at least three results for each candidate, including the number of timeouts.

  3. Retest during typical usage hours

    Run another round during the hours you usually go online, such as 8:00–10:00 p.m. Record successful readings and failed attempts for each round. For candidates that succeed all three times, compare the median. If a candidate times out, don’t report only its fastest result.

  4. Check performance with your actual apps

    Right-click a server in the list and choose “Set as active server,” then confirm that the app you’re testing actually accesses its target through v2rayN. Compare using the same page or the same file, if downloads are permitted. If a test address works but your usual targets often fail, base your choice on actual access results.

The readings below are illustrative only and do not represent measured results from any service on sale. Candidate A is faster when it connects, but times out once in three attempts. Candidate B is slightly slower on a single test, but is a better choice to try for everyday use first.

68 ms
Candidate A fastest reading
1 / 3
Candidate A timeouts
112 ms
Candidate B median
0 / 3
Candidate B timeouts

Traffic multipliers: Calculate quota usage

Labels such as “0.5×,” “1×,” and “2×” in server names usually indicate how much of your plan’s data quota each unit of traffic uses. The multiplier is set by the provider; it is neither a VMess, VLESS, or Trojan protocol setting nor a speed multiplier. Before calculating, check whether your plan counts downloads only, both upload and download traffic, or uses another billing method.

MultiplierBillable trafficQuota deducted
0.5×10 GB5 GB
1×10 GB10 GB
2×10 GB20 GB

This table assumes the provider deducts quota as “billable traffic × listed multiplier,” with no other rules. To check your own usage, note the remaining quota in the control panel, pause other devices using the same subscription, and transfer a file of known size through a single server. Once the panel updates, compare the before-and-after amounts. If they don’t match, check the units, upload and download accounting, and refresh interval.

Traffic multipliers can make large downloads more costly. For example, with 40 GB of billable traffic per month, the same usage deducts 20 GB on a 0.5× server and 80 GB on a 2× server. If both throughput and stability meet your needs, use a lower-multiplier server for large transfers.

Exit location: Check where your traffic appears to come from

The location in a server’s name may not match its final exit location. The entry point accepts your connection; the exit is the public IP address seen by the destination service. A server using a relay may accept connections in one location and exit in another. Even servers labeled with the same location may take different routes to the same destination.

Verify the exit location for your use case

When the location matters
  • Switch to a candidate server, then use the browser you plan to use to check your public IP address and its location.
  • If routing rules are enabled, make sure both the lookup page and the target service use the expected proxy rule.
  • Check the result on the target service itself. IP geolocation databases may not agree with how the service identifies your location.
When the location is flexible
  • Choose two candidates with different exit locations and visit the same target page at the same time.
  • Don’t judge performance from a cached page. Note whether the first visit times out and whether repeat visits are reliable.
  • For large downloads, test sustained throughput separately. A single page load is not a substitute for a download test.

If the location must match, first filter servers based on the target service’s decision, then compare stability and traffic multipliers.

If the IP address stays the same after switching servers, first check whether the lookup request is going through the proxy or connecting directly. Confirm that both requests went through their respective servers before considering whether the servers share an exit. Don’t rely on server names alone to tell whether the switch worked.

Protocol types: Check that the full configuration is compatible

VMess, VLESS, and Trojan are connection protocols, not speed tiers. Along with the protocol, check the transport method and security settings. Importing a server into the list only means the client accepted the entry; it doesn’t guarantee that its current core can connect using all the specified settings.

VLESS

Recommended

If your subscription provides VLESS + REALITY and your client uses an Xray core that supports this combination, test it with the original settings. VLESS itself does not provide encryption. Don’t change the server’s REALITY settings to standard TLS or keep only the address, port, and user ID.

Best for: Existing VLESS + REALITY configurations used with v2rayN or v2rayNG running an Xray core.

VMess

Import the server as specified by your subscription. If it uses WebSocket, keep the original path. If the configuration includes TLS, keep the server name specified by the subscription. If a previously working server suddenly stops connecting, also check that your device’s date and time are correct.

Best for: Testing a working VMess server from your subscription on your current device.

Trojan

Trojan servers commonly connect over TLS and use password authentication. After importing, check the server name and transport settings against the original configuration. If you get a certificate error, first check your device’s time and whether the server name matches. Don’t disable certificate verification just to clear the error.

Best for: Servers provided by a service that are supported by your core’s transport and security settings.

The desktop version of v2rayN can use different cores depending on the server configuration. On Android, v2rayNG uses the Xray core, while v2flyNG uses the v2fly core. A subscription appearing in both Android clients does not mean they support the same transport and security combinations. Don’t try to work around compatibility differences by manually changing the protocol; use the subscription entry that matches each client’s core.

FAQ: Timeouts, speed, and backup servers

Why is a server with lower latency slower to download?

Latency measures how quickly a test request gets a response; throughput measures how much data can be transferred over time. Download the same file from the same source at the same time and compare speeds after the transfer stabilizes. If the destination limits single-connection speeds, cross-check with another source where testing is permitted.

All servers in a group time out. Should I import the subscription again?

First, test the same address using a backup server that worked before. If that also times out, check your local network, client logs, and the test address. If only this group fails, refresh the relevant subscription group and retest the updated entries.

Why does the same server work on my computer but not my phone?

Connect both devices to the same Wi-Fi and make sure you’re testing the same subscription entry. Then confirm that the app on your phone is actually using the proxy. If it still fails, check whether the mobile client’s core supports the configuration, and look in the logs for a configuration parsing error, connection timeout, or handshake failure.

Should the backup server also have the lowest latency?

Choose a backup that works during your usual usage hours and meets the target location requirements. If possible, pick one with a different route or exit location, then switch to it and test it. Two entries with different names may still share an entry point and go down together if it fails.

For your records, note only the server name, protocol combination, exit location, multiplier, test date, and number of timeouts. Retest your primary and backup servers after changing networks or updating the subscription. When sharing your notes, don’t include subscription URLs, server passwords, or full configurations.

Download v2rayN