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

Connection and verification

Protocol
VLESS
Address
204.216.216.23:1114
Transport / security
TCP / REALITY
Last verified exit IP
204.216.216.23
Last verified handshake
636 ms
Last verified HTTPS first byte
876 ms
Download speed
5.144 Mbps
Source
0xRadikal verified downloadable configs
First recorded check
2026-09-18 16:37:36 UTC
Recorded tunnel checks
12
Successful tunnel checks
10
Recorded tunnel success rate
83.3%

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)
7770 09-23 00:5610-09 07:24Check time (UTC)
HTTPS first byte (ms)
10130 09-23 00:5610-09 07:24Check 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 ok636 ms876 ms204.216.216.23
Tunnel ok768 ms1,013 ms204.216.216.23
Tunnel ok725 ms947 ms204.216.216.23
Tunnel ok727 ms949 ms204.216.216.23
Tunnel ok739 ms958 ms204.216.216.23
Tunnel ok777 ms997 ms204.216.216.23
Tunnel ok726 ms945 ms204.216.216.23
Tunnel ok572 ms779 ms204.216.216.23
Tunnel ok701 ms911 ms204.216.216.23
TimeoutNot measuredNot measuredNot verified
TimeoutNot measuredNot measuredNot verified
Policy blockedNot measuredNot measuredNot verified
Tunnel ok714 ms924 ms204.216.216.23
Unsupported checkerNot measuredNot measuredNot verified
Unsupported checkerNot 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.

This saved detail page remains available with its check history. Search indexing requires current successful full-tunnel verification, real measurements and an available configuration.