Skip to main content
Inactive — did not pass verificationLast result: 2026-10-24 22:24:56 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
82.39.171.12:443
Transport / security
TCP / REALITY
Last verified exit IP
91.239.157.84
Last verified handshake
657 ms
Last verified HTTPS first byte
889 ms
Download speed
6.901 Mbps
Source
0xRadikal verified downloadable configs
First recorded check
2026-09-14 11:23:08 UTC
Recorded tunnel checks
14
Successful tunnel checks
14
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)
10340 09-14 11:2310-24 22:24Check time (UTC)
HTTPS first byte (ms)
12820 09-14 11:2310-24 22:24Check time (UTC)

Check history

Latest 14 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 ok657 ms889 ms91.239.157.84
Tunnel ok624 ms847 ms91.239.157.84
Tunnel ok582 ms806 ms91.239.157.84
Tunnel ok520 ms736 ms91.239.157.84
Tunnel ok516 ms728 ms91.239.157.84
Tunnel ok560 ms770 ms91.239.157.84
Tunnel ok1,034 ms1,282 ms91.239.157.84
Tunnel ok612 ms828 ms91.239.157.84
Tunnel ok514 ms724 ms91.239.157.84
Tunnel ok545 ms751 ms91.239.157.84
Tunnel ok691 ms889 ms91.239.157.84
Tunnel ok656 ms868 ms91.239.157.84
Tunnel ok621 ms825 ms91.239.157.84
Tunnel ok840 ms1,170 ms91.239.157.84

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.