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

Connection and verification

Protocol
VLESS
Address
104.19.48.107:443
Transport / security
WEBSOCKET / TLS
Last verified exit IP
158.101.158.101
Last verified handshake
1,970 ms
Last verified HTTPS first byte
2,384 ms
Download speed
1.398 Mbps
Source
0xRadikal verified downloadable configs
First recorded check
2026-09-26 08:46:44 UTC
Recorded tunnel checks
9
Successful tunnel checks
6
Recorded tunnel success rate
66.7%

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)
69390 09-27 09:3310-08 23:24Check time (UTC)
HTTPS first byte (ms)
73630 09-27 09:3310-08 23:24Check 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,970 ms2,384 ms158.101.158.101
Tunnel ok6,939 ms7,363 ms158.101.158.101
Policy blockedNot measuredNot measuredNot verified
Policy blockedNot measuredNot measuredNot verified
TimeoutNot measuredNot measuredNot verified
Policy blockedNot measuredNot measuredNot verified
Tunnel ok1,772 ms2,817 ms158.101.158.101
Policy blockedNot measuredNot measuredNot verified
TimeoutNot measuredNot measuredNot verified
Policy blockedNot measuredNot measuredNot verified
Tunnel ok1,025 ms1,438 ms158.101.158.101
Tunnel ok2,695 ms3,446 ms158.101.158.101
Tunnel ok2,043 ms2,550 ms158.101.158.101
Tunnel failedNot 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.