Skip to main content
Tunnel verified at last checkLast result: 2026-10-09 04:57:25 UTC

Connection and verification

Protocol
VLESS
Address
137.175.82.40:30556
Transport / security
TCP / REALITY
Last verified exit IP
137.175.82.40
Last verified handshake
769 ms
Last verified HTTPS first byte
1,097 ms
Download speed
2.834 Mbps
Source
Au1rxx verified downloadable configs
First recorded check
2026-09-25 10:08:01 UTC
Recorded tunnel checks
15
Successful tunnel checks
15
Recorded tunnel success rate
100.0%

Handshake is tunnel setup time; HTTPS first byte includes the request through that tunnel. Neither is an ICMP ping or a bandwidth measurement. The success rate covers stored full-tunnel attempts only; it is not continuous uptime.

Performance history

Hover or focus a point for check details. Click or tap to keep them open.

Tunnel handshake (ms)
27060 09-25 10:0810-09 04:57Check time (UTC)
HTTPS first byte (ms)
30590 09-25 10:0810-09 04:57Check time (UTC)

Check history

Latest 16 stored checks, up to 100 per configuration. Checks belong to this configuration’s stable public ID; different configurations on the same host have separate histories. Preflight and policy results do not count as successful tunnels.

Recorded VLESS checks, newest first
Checked (UTC)ResultHandshakeHTTPS first byteExit IP
Tunnel ok769 ms1,097 ms137.175.82.40
Tunnel ok732 ms1,035 ms137.175.82.40
Tunnel ok728 ms1,036 ms137.175.82.40
Tunnel ok778 ms1,082 ms137.175.82.40
Tunnel ok729 ms1,036 ms137.175.82.40
Tunnel ok797 ms1,106 ms137.175.82.40
Tunnel ok749 ms1,056 ms137.175.82.40
Tunnel ok745 ms1,049 ms137.175.82.40
Preflight okNot measuredNot measuredNot verified
Tunnel ok689 ms981 ms137.175.82.40
Tunnel ok860 ms1,207 ms137.175.82.40
Tunnel ok851 ms1,206 ms137.175.82.40
Tunnel ok862 ms1,309 ms137.175.82.40
Tunnel ok854 ms1,202 ms137.175.82.40
Tunnel ok903 ms1,637 ms137.175.82.40
Tunnel ok2,706 ms3,059 ms137.175.82.40

How to use this VLESS configuration

  1. Download the current configuration while a fresh verification is available.
  2. Import it into a VLESS-compatible client, preserving all required transport, security and authentication parameters.
  3. Connect and verify your connection with the IP tool and VPN leak test.

If it fails, compare the latest check time, try a different endpoint or report the problem. Public source configurations can change between checks.

What does a successful check prove?

The external checker completed a VLESS tunnel, carried an HTTPS request and verified a changed public exit IP. This measures technical availability at that time, not the operator’s trustworthiness or performance from your network.

Read the VLESS guide, our checking methodology and public VPN risks.

This saved detail page remains available with its check history. Search indexing requires current successful full-tunnel verification, real measurements and an available configuration.