Skip to main content
Tunnel verified at last checkLast result: 2026-10-08 11:24:00 UTC

Connection and verification

Protocol
VLESS
Address
172.67.156.147:443
Transport / security
WEBSOCKET / TLS
Last verified exit IP
158.101.158.101
Last verified handshake
2,479 ms
Last verified HTTPS first byte
2,898 ms
Download speed
Not measured
Source
Au1rxx verified downloadable configs
First recorded check
2026-09-13 19:47:21 UTC
Recorded tunnel checks
15
Successful tunnel checks
11
Recorded tunnel success rate
73.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)
44800 09-13 19:4710-08 11:24Check time (UTC)
HTTPS first byte (ms)
55290 09-13 19:4710-08 11:24Check 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 ok2,479 ms2,898 ms158.101.158.101
Tunnel ok4,480 ms5,529 ms158.101.158.101
Tunnel failedNot measuredNot measuredNot verified
Tunnel ok1,066 ms1,558 ms158.101.158.101
TimeoutNot measuredNot measuredNot verified
Tunnel ok1,046 ms1,466 ms158.101.158.101
Tunnel failedNot measuredNot measuredNot verified
Tunnel ok1,725 ms2,151 ms158.101.158.101
Tunnel ok2,123 ms2,539 ms158.101.158.101
Tunnel ok3,504 ms4,023 ms158.101.158.101
Tunnel ok1,256 ms1,883 ms158.101.158.101
Tunnel ok1,000 ms1,400 ms158.101.158.101
Tunnel ok997 ms1,414 ms158.101.158.101
Tunnel failedNot measuredNot measuredNot verified
Tunnel ok4,448 ms4,867 ms158.101.158.101

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.