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

Connection and verification

Protocol
VLESS
Address
169.40.42.35:443
Transport / security
TCP / REALITY
Last verified exit IP
185.195.57.173
Last verified handshake
635 ms
Last verified HTTPS first byte
802 ms
Download speed
3.955 Mbps
Source
Au1rxx verified downloadable configs
First recorded check
2026-09-26 05:33:18 UTC
Recorded tunnel checks
11
Successful tunnel checks
11
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)
41390 09-26 05:3310-09 04:38Check time (UTC)
HTTPS first byte (ms)
43700 09-26 05:3310-09 04:38Check time (UTC)

Check history

Latest 11 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 ok635 ms802 ms185.195.57.173
Tunnel ok589 ms772 ms185.195.57.173
Tunnel ok645 ms848 ms185.195.57.173
Tunnel ok611 ms788 ms185.195.57.173
Tunnel ok4,139 ms4,370 ms185.195.57.173
Tunnel ok724 ms900 ms185.195.57.173
Tunnel ok688 ms987 ms185.195.57.173
Tunnel ok523 ms700 ms185.195.57.173
Tunnel ok1,915 ms2,102 ms185.195.57.173
Tunnel ok1,088 ms1,261 ms185.195.57.173
Tunnel ok931 ms1,099 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.