Skip to main content
Tunnel verified at last checkLast result: 2026-10-09 07:09:14 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
629 ms
Last verified HTTPS first byte
796 ms
Download speed
2.663 Mbps
Source
0xRadikal verified downloadable configs
First recorded check
2026-09-17 15:22:59 UTC
Recorded tunnel checks
19
Successful tunnel checks
19
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)
90470 09-17 15:2210-09 07:09Check time (UTC)
HTTPS first byte (ms)
98050 09-17 15:2210-09 07:09Check time (UTC)

Check history

Latest 20 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 ok629 ms796 ms162.120.69.84
Tunnel ok5,527 ms5,794 ms162.120.69.84
Tunnel ok660 ms836 ms162.120.69.84
Tunnel ok803 ms976 ms162.120.69.84
Tunnel ok5,688 ms6,220 ms162.120.69.84
Tunnel ok735 ms964 ms162.120.69.84
Tunnel ok772 ms997 ms162.120.69.84
Policy blockedNot measuredNot measuredNot verified
Tunnel ok5,829 ms6,004 ms162.120.69.84
Tunnel ok9,047 ms9,805 ms162.120.69.84
Tunnel ok540 ms723 ms162.120.69.84
Tunnel ok3,092 ms3,347 ms162.120.69.84
Tunnel ok2,823 ms3,160 ms162.120.69.84
Tunnel ok526 ms701 ms162.120.69.84
Tunnel ok4,264 ms4,489 ms162.120.69.84
Tunnel ok729 ms912 ms162.120.69.84
Tunnel ok625 ms812 ms162.120.69.84
Tunnel ok1,549 ms1,732 ms162.120.69.84
Tunnel ok1,737 ms2,728 ms162.120.69.84
Tunnel ok778 ms978 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.