Skip to main content
Tunnel verified at last checkLast result: 2026-10-08 21:25:28 UTC

Connection and verification

Protocol
VLESS
Address
51.158.206.25:23576
Transport / security
TCP / REALITY
Last verified exit IP
51.158.206.25
Last verified handshake
315 ms
Last verified HTTPS first byte
501 ms
Download speed
7.262 Mbps
Source
Au1rxx verified downloadable configs
First recorded check
2026-09-13 20:15:18 UTC
Recorded tunnel checks
12
Successful tunnel checks
12
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)
5120 09-13 20:1510-08 21:25Check time (UTC)
HTTPS first byte (ms)
7290 09-13 20:1510-08 21:25Check time (UTC)

Check history

Latest 12 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 ok315 ms501 ms51.158.206.25
Tunnel ok324 ms505 ms51.158.206.25
Tunnel ok309 ms497 ms51.158.206.25
Tunnel ok301 ms479 ms51.158.206.25
Tunnel ok304 ms486 ms51.158.206.25
Tunnel ok512 ms729 ms51.158.206.25
Tunnel ok319 ms501 ms51.158.206.25
Tunnel ok284 ms458 ms51.158.206.25
Tunnel ok351 ms538 ms51.158.206.25
Tunnel ok276 ms448 ms51.158.206.25
Tunnel ok267 ms443 ms51.158.206.25
Tunnel ok322 ms515 ms51.158.206.25

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.