Skip to main content
Inactive — did not pass verificationLast result: 2026-10-09 01:54:42 UTC

This endpoint has no current downloadable verification, or a newer check did not succeed. Previous measurements below are historical. Choose another checked VLESS server.

Connection and verification

Protocol
VLESS
Address
104.16.111.202:443
Transport / security
WEBSOCKET / TLS
Last verified exit IP
158.101.158.101
Last verified handshake
1,016 ms
Last verified HTTPS first byte
1,735 ms
Download speed
Not measured
Source
0xRadikal verified downloadable configs
First recorded check
2026-09-26 08:47:51 UTC
Recorded tunnel checks
13
Successful tunnel checks
11
Recorded tunnel success rate
84.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)
76970 09-27 09:1610-09 01:54Check time (UTC)
HTTPS first byte (ms)
81100 09-27 09:1610-09 01:54Check 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,016 ms1,735 ms158.101.158.101
Tunnel ok1,138 ms2,843 ms158.101.158.101
Tunnel failedNot measuredNot measuredNot verified
Tunnel failedNot measuredNot measuredNot verified
Tunnel ok1,735 ms2,192 ms158.101.158.101
Tunnel ok1,709 ms2,129 ms158.101.158.101
Tunnel ok971 ms1,375 ms158.101.158.101
Tunnel ok2,569 ms3,002 ms158.101.158.101
Tunnel ok2,698 ms3,128 ms158.101.158.101
Tunnel ok1,909 ms2,536 ms158.101.158.101
Tunnel ok7,697 ms8,110 ms158.101.158.101
Tunnel ok3,584 ms3,997 ms158.101.158.101
Tunnel ok2,406 ms3,180 ms158.101.158.101
Policy blockedNot measuredNot measuredNot verified

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.