Free VLESS configs with a Japan exit IP

Checked VLESS in Japan 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.

Checking a Japanese VLESS exit

After connecting, compare the public IP reported by your browser with the chosen row’s exit IP. If they differ, first check whether the browser is included in the client’s proxy or tunnel routing. A split-routing configuration may send some applications directly. Repeat the comparison when changing networks, because a successful checker result describes its own network and time.

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 Japan label identify Tokyo or Osaka?

No. This catalog uses country-level GeoIP. It does not establish the city, datacenter or physical location of the endpoint, and it does not verify access to Japan-specific services.

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