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

Connection and verification

Protocol
VLESS
Address
169.40.42.179:443
Transport / security
TCP / REALITY
Last verified exit IP
185.195.57.174
Last verified handshake
789 ms
Last verified HTTPS first byte
958 ms
Download speed
4.709 Mbps
Source
Barry VLESS
First recorded check
2026-09-29 15:37:42 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)
114110 09-29 15:3710-09 05:59Check time (UTC)
HTTPS first byte (ms)
120120 09-29 15:3710-09 05:59Check 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 ok789 ms958 ms185.195.57.174
Tunnel ok548 ms722 ms185.195.57.174
Tunnel ok4,091 ms4,486 ms185.195.57.174
Tunnel ok614 ms787 ms185.195.57.174
Tunnel ok3,809 ms4,628 ms185.195.57.174
Tunnel ok3,398 ms6,092 ms185.195.57.174
Tunnel ok613 ms785 ms185.195.57.174
Tunnel ok608 ms777 ms185.195.57.174
Tunnel ok848 ms1,032 ms185.195.57.174
Tunnel ok11,411 ms12,012 ms185.195.57.174
Tunnel ok655 ms825 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.