Skip to main content
Tunnel verified at last checkLast result: 2026-10-09 05:38:32 UTC

Connection and verification

Protocol
VLESS
Address
104.21.70.21:443
Transport / security
WEBSOCKET / TLS
Last verified exit IP
158.101.158.101
Last verified handshake
1,042 ms
Last verified HTTPS first byte
1,460 ms
Download speed
1.701 Mbps
Source
Au1rxx verified downloadable configs
First recorded check
2026-09-13 18:09:48 UTC
Recorded tunnel checks
14
Successful tunnel checks
11
Recorded tunnel success rate
78.6%

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)
53180 09-13 18:0910-09 05:38Check time (UTC)
HTTPS first byte (ms)
81690 09-13 18:0910-09 05:38Check 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 ok1,042 ms1,460 ms158.101.158.101
Tunnel ok3,579 ms3,992 ms158.101.158.101
TimeoutNot measuredNot measuredNot verified
Tunnel failedNot measuredNot measuredNot verified
Tunnel failedNot measuredNot measuredNot verified
Tunnel ok995 ms1,748 ms158.101.158.101
Tunnel ok968 ms1,377 ms158.101.158.101
Tunnel ok5,318 ms5,734 ms158.101.158.101
Tunnel ok5,318 ms8,169 ms158.101.158.101
Tunnel ok985 ms1,392 ms158.101.158.101
Tunnel ok4,309 ms4,751 ms158.101.158.101
Tunnel ok1,024 ms2,055 ms158.101.158.101
Tunnel ok984 ms1,392 ms158.101.158.101
Preflight okNot measuredNot measuredNot verified
Tunnel ok3,545 ms4,501 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.