Skip to main content
Inactive — did not pass verificationLast result: 2026-10-09 04:52:49 UTC

This endpoint has no current downloadable verification, or a newer check did not succeed. Previous measurements below are historical. Choose another checked VLESS server.

Connection and verification

Protocol
VLESS
Address
jumpernode.site:443
Transport / security
TCP / REALITY
Last verified exit IP
163.128.99.254
Last verified handshake
3,128 ms
Last verified HTTPS first byte
3,907 ms
Download speed
2.089 Mbps
Source
0xRadikal verified downloadable configs
First recorded check
2026-10-04 09:39:41 UTC
Recorded tunnel checks
6
Successful tunnel checks
6
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)
31280 10-04 09:3910-09 04:52Check time (UTC)
HTTPS first byte (ms)
39070 10-04 09:3910-09 04:52Check time (UTC)

Check history

Latest 6 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 ok3,128 ms3,907 ms163.128.99.254
Tunnel ok2,308 ms3,024 ms163.128.99.254
Tunnel ok1,985 ms2,704 ms163.128.99.254
Tunnel ok3,025 ms3,825 ms163.128.99.254
Tunnel ok2,027 ms2,730 ms163.128.99.254
Tunnel ok1,834 ms2,621 ms163.128.99.254

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.