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

Connection and verification

Protocol
VLESS
Address
154.31.114.248:50159
Transport / security
TCP / REALITY
Last verified exit IP
154.31.114.248
Last verified handshake
1,003 ms
Last verified HTTPS first byte
1,506 ms
Download speed
2.297 Mbps
Source
0xRadikal verified downloadable configs
First recorded check
2026-09-15 18:27:30 UTC
Recorded tunnel checks
23
Successful tunnel checks
22
Recorded tunnel success rate
95.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)
11610 09-15 18:2710-09 07:00Check time (UTC)
HTTPS first byte (ms)
25200 09-15 18:2710-09 07:00Check time (UTC)

Check history

Latest 23 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,003 ms1,506 ms154.31.114.248
Tunnel ok984 ms1,490 ms154.31.114.248
Tunnel ok1,127 ms1,752 ms154.31.114.248
Tunnel ok981 ms1,488 ms154.31.114.248
Tunnel ok989 ms1,492 ms154.31.114.248
Tunnel ok969 ms1,475 ms154.31.114.248
Tunnel ok973 ms1,566 ms154.31.114.248
Tunnel ok986 ms1,485 ms154.31.114.248
Tunnel ok965 ms1,491 ms154.31.114.248
Tunnel ok1,069 ms1,568 ms154.31.114.248
Tunnel ok1,063 ms2,520 ms154.31.114.248
Tunnel ok977 ms1,464 ms154.31.114.248
Tunnel ok998 ms1,511 ms154.31.114.248
Tunnel ok1,161 ms1,663 ms154.31.114.248
Tunnel ok1,020 ms1,536 ms154.31.114.248
Tunnel ok866 ms1,315 ms154.31.114.248
Tunnel ok1,056 ms1,580 ms154.31.114.248
Tunnel failedNot measuredNot measuredNot verified
Tunnel ok856 ms1,322 ms154.31.114.248
Tunnel ok935 ms1,397 ms154.31.114.248
Tunnel ok866 ms1,321 ms154.31.114.248
Tunnel ok944 ms1,460 ms154.31.114.248
Tunnel ok1,020 ms1,515 ms154.31.114.248

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.