Skip to main content
Tunnel verified at last checkLast result: 2026-10-09 06:41:19 UTC

Connection and verification

Protocol
VLESS
Address
154.12.38.202:443
Transport / security
WEBSOCKET / REALITY
Last verified exit IP
154.12.38.202
Last verified handshake
993 ms
Last verified HTTPS first byte
1,311 ms
Download speed
1.931 Mbps
Source
Au1rxx verified downloadable configs
First recorded check
2026-10-03 10:25:11 UTC
Recorded tunnel checks
7
Successful tunnel checks
6
Recorded tunnel success rate
85.7%

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)
32300 10-04 11:3910-09 06:41Check time (UTC)
HTTPS first byte (ms)
38010 10-04 11:3910-09 06:41Check time (UTC)

Check history

Latest 7 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 ok993 ms1,311 ms154.12.38.202
Tunnel ok1,092 ms1,382 ms154.12.38.202
Tunnel ok3,230 ms3,801 ms154.12.38.202
Tunnel ok913 ms1,206 ms154.12.38.202
Tunnel ok2,075 ms2,396 ms154.12.38.202
Tunnel ok1,093 ms1,488 ms154.12.38.202
Tunnel failedNot measuredNot measuredNot verified

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.