This page narrows the VLESS catalog to observed German exit IPs. It is useful when you want to test a German route without mixing results from other exit countries. The country lookup is applied after the tunnel check, independently of the location advertised by a community source.
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.
Selecting a German VLESS endpoint
Compare the connection column before importing: VLESS is the proxy protocol, while transport and security are separate settings that must match the endpoint. To compare VLESS with VMess using the same country, open the German VMess selection below and repeat the same request from your device. A shared exit country does not mean the two protocols use the same machine or operator.
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 I reuse a German VMess profile in a VLESS client profile?
Do not change only the protocol label. Import the complete VLESS configuration into a client that supports its transport and security settings. VMess and VLESS profiles are separate connection formats.
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.