Skip to main content
Tunnel verified at last checkLast result: 2026-10-09 06:09:32 UTC

Connection and verification

Protocol
VLESS
Address
85.192.48.142:443
Transport / security
TCP / REALITY
Last verified exit IP
144.31.128.106
Last verified handshake
1,332 ms
Last verified HTTPS first byte
1,832 ms
Download speed
1.005 Mbps
Source
0xRadikal verified downloadable configs
First recorded check
2026-09-29 15:53:43 UTC
Recorded tunnel checks
11
Successful tunnel checks
11
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)
14060 09-29 15:5310-09 06:09Check time (UTC)
HTTPS first byte (ms)
18320 09-29 15:5310-09 06:09Check time (UTC)

Check history

Latest 11 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,332 ms1,832 ms144.31.128.106
Tunnel ok860 ms1,073 ms144.31.128.106
Tunnel ok1,193 ms1,619 ms144.31.128.106
Tunnel ok973 ms1,187 ms144.31.128.106
Tunnel ok293 ms496 ms144.31.128.106
Tunnel ok329 ms530 ms144.31.128.106
Tunnel ok1,118 ms1,611 ms144.31.128.106
Tunnel ok1,254 ms1,728 ms144.31.128.106
Tunnel ok1,406 ms1,782 ms144.31.128.106
Tunnel ok480 ms807 ms144.31.128.106
Tunnel ok398 ms607 ms144.31.128.106

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.