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

Connection and verification

Protocol
VLESS
Address
47.253.226.114:443
Transport / security
TCP / REALITY
Last verified exit IP
47.253.226.114
Last verified handshake
563 ms
Last verified HTTPS first byte
760 ms
Download speed
2.231 Mbps
Source
Barry VLESS
First recorded check
2026-09-26 15:07:35 UTC
Recorded tunnel checks
14
Successful tunnel checks
9
Recorded tunnel success rate
64.3%

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)
7350 09-26 15:0710-09 02:20Check time (UTC)
HTTPS first byte (ms)
9380 09-26 15:0710-09 02:20Check time (UTC)

Check history

Latest 14 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 ok563 ms760 ms47.253.226.114
Tunnel ok593 ms787 ms47.253.226.114
Tunnel failedNot measuredNot measuredNot verified
Tunnel ok671 ms865 ms47.253.226.114
Tunnel ok558 ms765 ms47.253.226.114
Tunnel ok569 ms762 ms47.253.226.114
TimeoutNot measuredNot measuredNot verified
Tunnel ok584 ms780 ms47.253.226.114
Tunnel failedNot measuredNot measuredNot verified
Tunnel failedNot measuredNot measuredNot verified
Tunnel ok608 ms844 ms47.253.226.114
Tunnel failedNot measuredNot measuredNot verified
Tunnel ok735 ms938 ms47.253.226.114
Tunnel ok555 ms745 ms47.253.226.114

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.