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

Connection and verification

Protocol
VLESS
Address
169.40.42.235:443
Transport / security
TCP / REALITY
Last verified exit IP
185.195.57.170
Last verified handshake
548 ms
Last verified HTTPS first byte
819 ms
Download speed
1.767 Mbps
Source
Au1rxx verified downloadable configs
First recorded check
2026-09-15 04:38:13 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)
28520 09-15 04:3810-09 04:38Check time (UTC)
HTTPS first byte (ms)
42370 09-15 04:3810-09 04:38Check time (UTC)

Check history

Latest 19 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 ok548 ms819 ms185.195.57.170
Tunnel ok650 ms823 ms185.195.57.170
Tunnel ok769 ms940 ms185.195.57.170
Tunnel ok2,852 ms4,237 ms185.195.57.170
Tunnel ok646 ms818 ms185.195.57.170
Tunnel ok1,865 ms2,696 ms185.195.57.170
Tunnel ok728 ms906 ms185.195.57.170
Tunnel ok716 ms917 ms185.195.57.170
Tunnel ok1,216 ms1,402 ms185.195.57.170
Tunnel ok705 ms895 ms185.195.57.170
Tunnel ok1,069 ms1,258 ms185.195.57.170
Tunnel ok631 ms814 ms185.195.57.170
Tunnel ok772 ms956 ms185.195.57.170
Tunnel ok724 ms953 ms185.195.57.170
Tunnel ok573 ms763 ms185.195.57.170
Tunnel ok562 ms745 ms185.195.57.170
Tunnel ok682 ms861 ms185.195.57.170
Tunnel ok617 ms803 ms185.195.57.170
Tunnel ok673 ms855 ms185.195.57.170

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.