Skip to main content
Tunnel verified at last checkLast result: 2026-10-08 10:59:35 UTC

Connection and verification

Protocol
VLESS
Address
144.31.50.236:443
Transport / security
TCP / REALITY
Last verified exit IP
45.13.186.30
Last verified handshake
439 ms
Last verified HTTPS first byte
638 ms
Download speed
4.885 Mbps
Source
Barry VLESS
First recorded check
2026-09-23 18:38:27 UTC
Recorded tunnel checks
15
Successful tunnel checks
15
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)
41810 09-23 18:3810-08 10:59Check time (UTC)
HTTPS first byte (ms)
58550 09-23 18:3810-08 10:59Check time (UTC)

Check history

Latest 15 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 ok439 ms638 ms45.13.186.30
Tunnel ok1,968 ms2,922 ms45.13.186.30
Tunnel ok4,181 ms5,855 ms45.13.186.30
Tunnel ok1,080 ms1,441 ms45.13.186.30
Tunnel ok1,792 ms2,320 ms45.13.186.30
Tunnel ok4,032 ms4,755 ms45.13.186.30
Tunnel ok2,081 ms2,909 ms45.13.186.30
Tunnel ok708 ms1,027 ms45.13.186.30
Tunnel ok909 ms1,124 ms45.13.186.30
Tunnel ok707 ms951 ms45.13.186.30
Tunnel ok475 ms710 ms45.13.186.30
Tunnel ok934 ms1,190 ms45.13.186.30
Tunnel ok740 ms1,038 ms45.13.186.30
Tunnel ok528 ms739 ms45.13.186.30
Tunnel ok526 ms739 ms45.13.186.30

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.