Skip to main content
Tunnel verified at last checkLast result: 2026-10-08 20:12:10 UTC

Connection and verification

Protocol
VLESS
Address
144.31.50.236:443
Transport / security
TCP / REALITY
Last verified exit IP
45.13.186.30
Last verified handshake
1,252 ms
Last verified HTTPS first byte
1,758 ms
Download speed
Not measured
Source
rjsxrd secure tunnel-tested configs
First recorded check
2026-09-24 19:09:48 UTC
Recorded tunnel checks
11
Successful tunnel checks
10
Recorded tunnel success rate
90.9%

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)
50100 09-24 19:0910-08 20:12Check time (UTC)
HTTPS first byte (ms)
55570 09-24 19:0910-08 20:12Check 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,252 ms1,758 ms45.13.186.30
Tunnel ok526 ms982 ms45.13.186.30
TimeoutNot measuredNot measuredNot verified
Tunnel ok1,072 ms2,037 ms45.13.186.30
Tunnel ok5,010 ms5,557 ms45.13.186.30
Tunnel ok2,044 ms2,980 ms45.13.186.30
Tunnel ok1,690 ms3,131 ms45.13.186.30
Tunnel ok507 ms736 ms45.13.186.30
Tunnel ok450 ms654 ms45.13.186.30
Tunnel ok462 ms657 ms45.13.186.30
Tunnel ok655 ms906 ms45.13.186.30

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.