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

Connection and verification

Protocol
VLESS
Address
169.40.42.173:443
Transport / security
TCP / REALITY
Last verified exit IP
185.195.57.173
Last verified handshake
1,558 ms
Last verified HTTPS first byte
1,833 ms
Download speed
2.999 Mbps
Source
Au1rxx verified downloadable configs
First recorded check
2026-09-17 04:23:02 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)
17770 09-17 04:2310-09 05:38Check time (UTC)
HTTPS first byte (ms)
20670 09-17 04:2310-09 05:38Check 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 ok1,558 ms1,833 ms185.195.57.173
Tunnel ok651 ms831 ms185.195.57.173
Tunnel ok1,777 ms2,067 ms185.195.57.173
Tunnel ok609 ms794 ms185.195.57.173
Tunnel ok566 ms767 ms185.195.57.173
Tunnel ok625 ms806 ms185.195.57.173
Tunnel ok543 ms722 ms185.195.57.173
Preflight okNot measuredNot measuredNot verified
Tunnel ok578 ms756 ms185.195.57.173
Tunnel ok1,616 ms1,792 ms185.195.57.173
Tunnel ok574 ms742 ms185.195.57.173
Tunnel ok644 ms815 ms185.195.57.173
Tunnel ok622 ms811 ms185.195.57.173
Tunnel ok624 ms811 ms185.195.57.173
Tunnel ok1,507 ms1,801 ms185.195.57.173
Tunnel ok701 ms886 ms185.195.57.173
Tunnel ok697 ms881 ms185.195.57.173
Tunnel ok636 ms818 ms185.195.57.173

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.