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

Connection and verification

Protocol
VLESS
Address
23.95.222.127:8443
Transport / security
TCP / REALITY
Last verified exit IP
23.95.222.127
Last verified handshake
5,084 ms
Last verified HTTPS first byte
5,625 ms
Download speed
1.743 Mbps
Source
0xRadikal verified downloadable configs
First recorded check
2026-09-26 13:57:42 UTC
Recorded tunnel checks
12
Successful tunnel checks
12
Recorded tunnel success rate
100.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)
50840 09-26 13:5710-09 02:00Check time (UTC)
HTTPS first byte (ms)
56250 09-26 13:5710-09 02:00Check 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 ok5,084 ms5,625 ms23.95.222.127
Tunnel ok1,490 ms1,785 ms23.95.222.127
Policy blockedNot measuredNot measuredNot verified
Policy blockedNot measuredNot measuredNot verified
Tunnel ok732 ms1,041 ms23.95.222.127
Tunnel ok810 ms1,129 ms23.95.222.127
Tunnel ok900 ms1,386 ms23.95.222.127
Tunnel ok791 ms1,101 ms23.95.222.127
Tunnel ok778 ms1,092 ms23.95.222.127
Tunnel ok737 ms1,045 ms23.95.222.127
Tunnel ok1,167 ms1,482 ms23.95.222.127
Tunnel ok746 ms1,047 ms23.95.222.127
Tunnel ok869 ms1,306 ms23.95.222.127
Tunnel ok783 ms1,105 ms23.95.222.127

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.