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

Connection and verification

Protocol
VLESS
Address
169.40.42.74:443
Transport / security
TCP / REALITY
Last verified exit IP
185.195.57.174
Last verified handshake
555 ms
Last verified HTTPS first byte
737 ms
Download speed
4.3 Mbps
Source
Au1rxx verified downloadable configs
First recorded check
2026-09-13 18:52:30 UTC
Recorded tunnel checks
22
Successful tunnel checks
22
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)
11890 09-13 18:5210-09 03:38Check time (UTC)
HTTPS first byte (ms)
13990 09-13 18:5210-09 03:38Check time (UTC)

Check history

Latest 22 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 ok555 ms737 ms185.195.57.174
Tunnel ok642 ms879 ms185.195.57.174
Tunnel ok1,004 ms1,180 ms185.195.57.174
Tunnel ok785 ms966 ms185.195.57.174
Tunnel ok673 ms863 ms185.195.57.174
Tunnel ok642 ms813 ms185.195.57.174
Tunnel ok664 ms1,056 ms185.195.57.174
Tunnel ok528 ms703 ms185.195.57.174
Tunnel ok592 ms766 ms185.195.57.174
Tunnel ok519 ms690 ms185.195.57.174
Tunnel ok1,189 ms1,362 ms185.195.57.174
Tunnel ok719 ms907 ms185.195.57.174
Tunnel ok622 ms800 ms185.195.57.174
Tunnel ok676 ms870 ms185.195.57.174
Tunnel ok1,066 ms1,399 ms185.195.57.174
Tunnel ok546 ms739 ms185.195.57.174
Tunnel ok691 ms873 ms185.195.57.174
Tunnel ok575 ms842 ms185.195.57.174
Tunnel ok679 ms874 ms185.195.57.174
Tunnel ok630 ms818 ms185.195.57.174
Tunnel ok575 ms759 ms185.195.57.174
Tunnel ok628 ms811 ms185.195.57.174

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.