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

Connection and verification

Protocol
VLESS
Address
169.40.42.184:443
Transport / security
TCP / REALITY
Last verified exit IP
185.195.57.175
Last verified handshake
2,506 ms
Last verified HTTPS first byte
2,706 ms
Download speed
2.5 Mbps
Source
Au1rxx verified downloadable configs
First recorded check
2026-09-14 04:33:54 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)
47520 09-14 04:3310-09 06:24Check time (UTC)
HTTPS first byte (ms)
49290 09-14 04:3310-09 06:24Check 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 ok2,506 ms2,706 ms185.195.57.175
Tunnel ok1,607 ms1,776 ms185.195.57.175
Tunnel ok534 ms707 ms185.195.57.175
Tunnel ok596 ms779 ms185.195.57.175
Tunnel ok652 ms830 ms185.195.57.175
Tunnel ok668 ms882 ms185.195.57.175
Tunnel ok600 ms772 ms185.195.57.175
Tunnel ok661 ms832 ms185.195.57.175
Tunnel ok4,752 ms4,929 ms185.195.57.175
Tunnel ok539 ms718 ms185.195.57.175
Tunnel ok940 ms1,113 ms185.195.57.175
Tunnel ok966 ms1,159 ms185.195.57.175
Tunnel ok983 ms1,185 ms185.195.57.175
Tunnel ok577 ms770 ms185.195.57.175
Tunnel ok650 ms832 ms185.195.57.175
Tunnel ok620 ms802 ms185.195.57.175
Tunnel ok706 ms898 ms185.195.57.175
Tunnel ok564 ms755 ms185.195.57.175
Tunnel ok607 ms783 ms185.195.57.175

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.