Skip to main content
Tunnel verified at last checkLast result: 2026-10-08 11:24:59 UTC

Connection and verification

Protocol
VLESS
Address
150.241.101.17:8443
Transport / security
TCP / REALITY
Last verified exit IP
150.241.101.17
Last verified handshake
523 ms
Last verified HTTPS first byte
729 ms
Download speed
2.12 Mbps
Source
0xRadikal verified downloadable configs
First recorded check
2026-09-23 18:32:04 UTC
Recorded tunnel checks
15
Successful tunnel checks
15
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)
5230 09-23 18:3210-08 11:24Check time (UTC)
HTTPS first byte (ms)
7320 09-23 18:3210-08 11: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 ok523 ms729 ms150.241.101.17
Tunnel ok480 ms716 ms150.241.101.17
Tunnel ok398 ms580 ms150.241.101.17
Tunnel ok326 ms509 ms150.241.101.17
Tunnel ok370 ms549 ms150.241.101.17
Tunnel ok336 ms516 ms150.241.101.17
Tunnel ok347 ms534 ms150.241.101.17
Tunnel ok323 ms506 ms150.241.101.17
Tunnel ok392 ms572 ms150.241.101.17
Tunnel ok364 ms551 ms150.241.101.17
Tunnel ok371 ms554 ms150.241.101.17
Tunnel ok365 ms560 ms150.241.101.17
Tunnel ok437 ms632 ms150.241.101.17
Tunnel ok430 ms636 ms150.241.101.17
Tunnel ok515 ms732 ms150.241.101.17

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.