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

Connection and verification

Protocol
VLESS
Address
104.16.10.21:443
Transport / security
WEBSOCKET / TLS
Last verified exit IP
129.146.86.61
Last verified handshake
2,685 ms
Last verified HTTPS first byte
3,004 ms
Download speed
1.97 Mbps
Source
0xRadikal verified downloadable configs
First recorded check
2026-09-26 01:06:18 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)
41000 09-26 01:0610-09 00:43Check time (UTC)
HTTPS first byte (ms)
46840 09-26 01:0610-09 00:43Check 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 ok2,685 ms3,004 ms129.146.86.61
Tunnel ok1,894 ms2,346 ms129.146.86.61
Tunnel ok1,736 ms3,491 ms129.146.86.61
Tunnel ok1,819 ms2,972 ms129.146.86.61
Tunnel ok1,724 ms2,079 ms129.146.86.61
Tunnel ok4,100 ms4,684 ms129.146.86.61
Tunnel ok2,584 ms3,253 ms129.146.86.61
TimeoutNot measuredNot measuredNot verified
TimeoutNot measuredNot measuredNot verified
Tunnel ok1,658 ms2,380 ms129.146.86.61
Tunnel ok1,114 ms1,518 ms129.146.86.61
Tunnel ok1,474 ms2,594 ms129.146.86.61
TimeoutNot measuredNot measuredNot verified
Tunnel ok984 ms1,573 ms129.146.86.61

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.