Skip to main content
Tunnel verified at last checkLast result: 2026-09-12 19:28:36 UTC

Connection and verification

Protocol
VLESS
Address
169.40.42.182:443
Transport / security
TCP / REALITY
Last verified exit IP
162.120.69.83
Last verified handshake
1,066 ms
Last verified HTTPS first byte
1,245 ms
Download speed
4.299 Mbps
Source
Au1rxx verified downloadable configs
First recorded check
2026-09-10 07:43:59 UTC
Recorded tunnel checks
2
Successful tunnel checks
2
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

Tunnel handshake (ms)
10660 2026-09-11 18:59:18 UTC: 966 ms2026-09-12 19:28:36 UTC: 1,066 ms09-11 18:5909-12 19:28Check time (UTC)
HTTPS first byte (ms)
12450 2026-09-11 18:59:18 UTC: 1,148 ms2026-09-12 19:28:36 UTC: 1,245 ms09-11 18:5909-12 19:28Check time (UTC)

Check history

Latest 3 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 ok1,066 ms1,245 ms162.120.69.83
Tunnel ok966 ms1,148 ms162.120.69.83
Unsupported checkerNot measuredNot measuredNot verified

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.