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

Connection and verification

Protocol
VLESS
Address
jumpernode.online:443
Transport / security
TCP / REALITY
Last verified exit IP
136.175.179.4
Last verified handshake
1,668 ms
Last verified HTTPS first byte
2,175 ms
Download speed
2.11 Mbps
Source
0xRadikal verified downloadable configs
First recorded check
2026-09-23 12:10:08 UTC
Recorded tunnel checks
15
Successful tunnel checks
15
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)
101290 09-23 12:1010-09 00:57Check time (UTC)
HTTPS first byte (ms)
106760 09-23 12:1010-09 00:57Check time (UTC)

Check history

Latest 18 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,668 ms2,175 ms136.175.179.4
Policy blockedNot measuredNot measuredNot verified
Tunnel ok3,746 ms4,253 ms136.175.179.4
Tunnel ok1,480 ms1,955 ms136.175.179.4
Tunnel ok7,234 ms8,994 ms136.175.179.4
Tunnel ok2,033 ms3,049 ms136.175.179.4
Tunnel ok1,839 ms2,325 ms136.175.179.4
Tunnel ok4,300 ms6,891 ms136.175.179.4
Preflight okNot measuredNot measuredNot verified
Tunnel ok7,637 ms8,570 ms136.175.179.4
Tunnel ok1,632 ms2,124 ms136.175.179.4
Policy blockedNot measuredNot measuredNot verified
Tunnel ok1,685 ms2,198 ms136.175.179.4
Tunnel ok10,129 ms10,676 ms136.175.179.4
Tunnel ok2,408 ms2,938 ms136.175.179.4
Tunnel ok1,640 ms2,280 ms136.175.179.4
Tunnel ok6,986 ms7,560 ms136.175.179.4
Tunnel ok1,700 ms2,171 ms136.175.179.4

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.