This selection is for testing a VLESS connection whose observed public exit IP is assigned to the United States. The destination website sees that exit address when its traffic follows the tunnel. A server name containing “USA” is not enough for inclusion: the country comes from the exit IP measured by the checker.
Rows come from the current published tunnel checks and are ordered by their last check time. Compare the exit IP, connection settings and saved history before choosing a configuration. A snapshot update does not mean every row was checked at that moment.
Speed and HTTPS response time are measurements from the checker’s network. Weekly success is the share of saved successful attempts in the last seven days, with the sample count shown; it is not continuous uptime. Missing measurements stay unknown.
Choosing a US VLESS exit
A country-level label does not identify the US coast, city or physical server location. Compare the measured HTTPS time and recent check history across several endpoints, then measure your own connection. Keep the transport and TLS or REALITY settings from the downloaded profile; choosing a US exit does not determine which settings a server accepts.
How the exit country is determined
The country beside each row comes from the public IP observed through the tunnel, using the active DB-IP Country Lite dataset. Country-level GeoIP is approximate and can differ from a website’s own location database. It does not establish a city, a physical server location or the operator’s jurisdiction. Country data by DB-IP, CC BY 4.0.
Does a USA exit guarantee access to a US service?
No. Services can classify the same IP differently or restrict shared proxy addresses. This catalog verifies a tunnel and HTTPS traffic; it does not test access to individual streaming, shopping or account services.
How to connect with a VLESS configuration
Choose a row with a recent check and open its details to review the saved results.
Download the complete configuration and import it into a client that supports VLESS and the row’s transport and security settings.
Enable the client’s intended proxy or tunnel mode. Confirm that the application you are testing is included in its routing rules.
Check your public IP and run a leak test. Compare the observed exit with the selected row, then measure performance from your own network.
If a download is no longer available, return to the current selection and choose another recent row. Public endpoints change between checks. A successful tunnel test does not verify the operator’s privacy practices; read the public endpoint risk guide.