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

Connection and verification

Protocol
VLESS
Address
169.40.42.15:443
Transport / security
TCP / REALITY
Last verified exit IP
162.120.69.88
Last verified handshake
3,211 ms
Last verified HTTPS first byte
3,487 ms
Download speed
4.747 Mbps
Source
Au1rxx verified downloadable configs
First recorded check
2026-09-21 00:23:47 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)
32110 09-21 23:2410-09 06:25Check time (UTC)
HTTPS first byte (ms)
34870 09-21 23:2410-09 06:25Check time (UTC)

Check history

Latest 18 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 ok3,211 ms3,487 ms162.120.69.88
Tunnel ok619 ms790 ms162.120.69.88
Tunnel ok652 ms838 ms162.120.69.88
Tunnel ok653 ms887 ms162.120.69.88
Tunnel ok652 ms825 ms162.120.69.88
Tunnel ok1,311 ms1,551 ms162.120.69.88
Tunnel ok849 ms1,032 ms162.120.69.88
Tunnel ok652 ms828 ms162.120.69.88
Tunnel ok676 ms857 ms162.120.69.88
Tunnel ok582 ms751 ms162.120.69.88
Tunnel ok582 ms762 ms162.120.69.88
Tunnel ok861 ms1,031 ms162.120.69.88
Tunnel ok524 ms695 ms162.120.69.88
Tunnel ok631 ms826 ms162.120.69.88
Tunnel ok688 ms872 ms162.120.69.88
Tunnel ok615 ms798 ms162.120.69.88
Tunnel ok689 ms868 ms162.120.69.88
Policy blockedNot 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.

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