Free VLESS REALITY configs and checked servers — Page 4

Checked VLESS REALITY servers

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.

What makes a VLESS REALITY configuration different?

Use a client with explicit REALITY support and import the full profile. Preserve the supplied server name, public key, short ID, fingerprint and flow settings when present. Guessing these fields or copying them from a different server can prevent the handshake. Open the profile’s check history if importing succeeds but connecting fails, then try another recently checked configuration.

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.

Can a normal VLESS TLS profile be changed to REALITY?

Changing the security selector alone is not enough. The server must support REALITY and the client needs the matching connection parameters. Download a REALITY profile from this selection and keep its supplied settings.

For the connection fields, see the official Xray transport documentation.

How to connect with a VLESS configuration

1. Choose a row with a recent check and open its details to review the saved results.
2. Download the complete configuration and import it into a client that supports VLESS and the row’s transport and security settings.
3. Enable the client’s intended proxy or tunnel mode. Confirm that the application you are testing is included in its routing rules.
4. 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.

Explore other countries and protocols

All VLESS servers · Compare all protocols