Skip to main content
Tunnel verified at last checkLast result: 2026-10-09 01:13:04 UTC

Connection and verification

Protocol
VLESS
Address
104.18.42.98:443
Transport / security
WEBSOCKET / TLS
Last verified exit IP
158.101.158.101
Last verified handshake
1,925 ms
Last verified HTTPS first byte
2,342 ms
Download speed
1.103 Mbps
Source
0xRadikal verified downloadable configs
First recorded check
2026-09-26 08:38:55 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)
86380 09-26 08:3810-09 01:13Check time (UTC)
HTTPS first byte (ms)
90500 09-26 08:3810-09 01:13Check 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,925 ms2,342 ms158.101.158.101
Tunnel ok1,083 ms1,498 ms158.101.158.101
TimeoutNot measuredNot measuredNot verified
Policy blockedNot measuredNot measuredNot verified
Policy blockedNot measuredNot measuredNot verified
Tunnel failedNot measuredNot measuredNot verified
Tunnel ok1,079 ms1,496 ms158.101.158.101
Tunnel ok4,021 ms4,434 ms158.101.158.101
Tunnel ok2,373 ms2,790 ms158.101.158.101
Tunnel ok7,810 ms8,466 ms158.101.158.101
Tunnel ok3,520 ms4,110 ms158.101.158.101
Tunnel ok8,638 ms9,050 ms158.101.158.101
Tunnel ok1,551 ms2,312 ms158.101.158.101
Tunnel ok2,594 ms3,508 ms158.101.158.101

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.