VLESS server jpga01.jumpernode.site:443
TCP / REALITY · Au1rxx verified downloadable configs
TCP / REALITY · Au1rxx verified downloadable configs
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.
Hover or focus a point for check details. Click or tap to keep them open.
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.
| Checked (UTC) | Result | Handshake | HTTPS first byte | Exit IP |
|---|---|---|---|---|
| Tunnel ok | 1,171 ms | 1,656 ms | 151.242.165.75 | |
| Tunnel ok | 5,338 ms | 5,914 ms | 151.242.165.75 | |
| Tunnel ok | 1,231 ms | 1,710 ms | 151.242.165.75 | |
| Tunnel ok | 2,133 ms | 3,029 ms | 151.242.165.75 | |
| Tunnel ok | 5,158 ms | 5,688 ms | 151.242.165.75 | |
| Tunnel ok | 1,208 ms | 1,707 ms | 151.242.165.75 |
No recorded checks match this filter.
If it fails, compare the latest check time, try a different endpoint or report the problem. Public source configurations can change between checks.
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.