Skip to main content
Tunnel verified at last checkLast result: 2026-09-11 15:28:57 UTC

Connection and verification

Protocol
VLESS
Address
31.58.50.200:8443
Transport / security
TCP / REALITY
Last verified exit IP
31.58.50.200
Last verified handshake
902 ms
Last verified HTTPS first byte
1,264 ms
Download speed
3.06 Mbps
Source
0xRadikal verified downloadable configs
First recorded check
2026-09-07 14:02:57 UTC
Recorded tunnel checks
2
Successful tunnel checks
2
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

Tunnel handshake (ms)
10820 2026-09-09 16:14:10 UTC: 1,082 ms2026-09-11 15:28:57 UTC: 902 ms09-09 16:1409-11 15:28Check time (UTC)
HTTPS first byte (ms)
15080 2026-09-09 16:14:10 UTC: 1,508 ms2026-09-11 15:28:57 UTC: 1,264 ms09-09 16:1409-11 15:28Check time (UTC)

Check history

Latest 3 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 ok902 ms1,264 ms31.58.50.200
Tunnel ok1,082 ms1,508 ms31.58.50.200
Preflight okNot measuredNot measuredNot verified

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.