Skip to main content
Tunnel verified at last checkLast result: 2026-10-09 05:38:23 UTC

Connection and verification

Protocol
VLESS
Address
169.40.42.229:443
Transport / security
TCP / REALITY
Last verified exit IP
162.120.69.84
Last verified handshake
524 ms
Last verified HTTPS first byte
692 ms
Download speed
4.366 Mbps
Source
Au1rxx verified downloadable configs
First recorded check
2026-09-16 10:45:22 UTC
Recorded tunnel checks
17
Successful tunnel checks
17
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)
51190 09-16 10:4510-09 05:38Check time (UTC)
HTTPS first byte (ms)
52890 09-16 10:4510-09 05:38Check time (UTC)

Check history

Latest 17 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 ok524 ms692 ms162.120.69.84
Tunnel ok5,119 ms5,289 ms162.120.69.84
Tunnel ok2,754 ms2,925 ms162.120.69.84
Tunnel ok1,467 ms1,886 ms162.120.69.84
Tunnel ok543 ms718 ms162.120.69.84
Tunnel ok3,362 ms4,085 ms162.120.69.84
Tunnel ok535 ms708 ms162.120.69.84
Tunnel ok612 ms781 ms162.120.69.84
Tunnel ok561 ms845 ms162.120.69.84
Tunnel ok684 ms1,083 ms162.120.69.84
Tunnel ok568 ms754 ms162.120.69.84
Tunnel ok1,810 ms2,248 ms162.120.69.84
Tunnel ok762 ms945 ms162.120.69.84
Tunnel ok1,033 ms1,216 ms162.120.69.84
Tunnel ok1,890 ms2,421 ms162.120.69.84
Tunnel ok688 ms868 ms162.120.69.84
Tunnel ok2,312 ms2,497 ms162.120.69.84

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.