Skip to main content
Tunnel verified at last checkLast result: 2026-10-09 05:55:50 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
654 ms
Last verified HTTPS first byte
827 ms
Download speed
4.118 Mbps
Source
Barry VLESS
First recorded check
2026-09-29 15:38:22 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)
23350 09-29 15:3810-09 05:55Check time (UTC)
HTTPS first byte (ms)
25660 09-29 15:3810-09 05:55Check 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 ok654 ms827 ms185.195.57.170
Tunnel ok641 ms811 ms185.195.57.170
Tunnel ok583 ms773 ms185.195.57.170
Tunnel ok533 ms707 ms185.195.57.170
Tunnel ok1,510 ms1,880 ms185.195.57.170
Tunnel ok1,378 ms1,621 ms185.195.57.170
Tunnel ok634 ms1,068 ms185.195.57.170
Tunnel ok2,335 ms2,566 ms185.195.57.170
Tunnel ok976 ms1,165 ms185.195.57.170
Tunnel ok628 ms803 ms185.195.57.170
Tunnel ok585 ms759 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.