Skip to main content
Tunnel verified at last checkLast result: 2026-10-09 04:39:00 UTC

Connection and verification

Protocol
VLESS
Address
188.114.97.6:443
Transport / security
WEBSOCKET / TLS
Last verified exit IP
158.101.158.101
Last verified handshake
1,004 ms
Last verified HTTPS first byte
1,422 ms
Download speed
1.124 Mbps
Source
Au1rxx verified downloadable configs
First recorded check
2026-09-14 16:31:16 UTC
Recorded tunnel checks
11
Successful tunnel checks
9
Recorded tunnel success rate
81.8%

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)
44120 09-14 16:3110-09 04:39Check time (UTC)
HTTPS first byte (ms)
51200 09-14 16:3110-09 04:39Check time (UTC)

Check history

Latest 11 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 ok1,004 ms1,422 ms158.101.158.101
Tunnel ok1,041 ms1,472 ms158.101.158.101
TimeoutNot measuredNot measuredNot verified
Tunnel failedNot measuredNot measuredNot verified
Tunnel ok994 ms1,408 ms158.101.158.101
Tunnel ok1,256 ms1,872 ms158.101.158.101
Tunnel ok3,463 ms3,916 ms158.101.158.101
Tunnel ok2,125 ms2,564 ms158.101.158.101
Tunnel ok4,412 ms5,120 ms158.101.158.101
Tunnel ok2,330 ms2,754 ms158.101.158.101
Tunnel ok2,364 ms3,384 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.