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

Connection and verification

Protocol
VLESS
Address
104.16.10.72:443
Transport / security
WEBSOCKET / TLS
Last verified exit IP
158.101.158.101
Last verified handshake
1,008 ms
Last verified HTTPS first byte
1,420 ms
Download speed
Not measured
Source
0xRadikal verified downloadable configs
First recorded check
2026-09-26 08:39:52 UTC
Recorded tunnel checks
12
Successful tunnel checks
9
Recorded tunnel success rate
75.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)
36960 09-26 08:3910-08 23:28Check time (UTC)
HTTPS first byte (ms)
51960 09-26 08:3910-08 23:28Check time (UTC)

Check history

Latest 14 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,008 ms1,420 ms158.101.158.101
Tunnel ok1,702 ms2,105 ms158.101.158.101
Tunnel failedNot measuredNot measuredNot verified
Tunnel failedNot measuredNot measuredNot verified
Tunnel ok2,061 ms2,705 ms158.101.158.101
Policy blockedNot measuredNot measuredNot verified
Policy blockedNot measuredNot measuredNot verified
Tunnel failedNot measuredNot measuredNot verified
Tunnel ok1,265 ms2,784 ms158.101.158.101
Tunnel ok3,696 ms5,196 ms158.101.158.101
Tunnel ok962 ms2,091 ms158.101.158.101
Tunnel ok3,497 ms3,916 ms158.101.158.101
Tunnel ok1,349 ms2,150 ms158.101.158.101
Tunnel ok3,514 ms4,433 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.