Skip to main content
Tunnel verified at last checkLast result: 2026-10-24 19:52:57 UTC

Connection and verification

Protocol
VLESS
Address
87.239.249.137:443
Transport / security
TCP / REALITY
Last verified exit IP
87.239.249.137
Last verified handshake
1,281 ms
Last verified HTTPS first byte
1,463 ms
Download speed
2.93 Mbps
Source
0xRadikal verified downloadable configs
First recorded check
2026-09-13 21:13:30 UTC
Recorded tunnel checks
33
Successful tunnel checks
13
Recorded tunnel success rate
39.4%

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)
13900 10-03 08:3210-24 19:52Check time (UTC)
HTTPS first byte (ms)
16040 10-03 08:3210-24 19:52Check time (UTC)

Check history

Latest 34 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,281 ms1,463 ms87.239.249.137
Tunnel failedNot measuredNot measuredNot verified
Tunnel failedNot measuredNot measuredNot verified
Tunnel failedNot measuredNot measuredNot verified
Tunnel failedNot measuredNot measuredNot verified
Tunnel failedNot measuredNot measuredNot verified
Tunnel failedNot measuredNot measuredNot verified
Tunnel ok1,329 ms1,544 ms87.239.249.137
Tunnel ok1,325 ms1,526 ms87.239.249.137
Tunnel ok1,348 ms1,535 ms87.239.249.137
Tunnel ok1,307 ms1,498 ms87.239.249.137
Tunnel ok1,375 ms1,557 ms87.239.249.137
Policy blockedNot measuredNot measuredNot verified
Tunnel ok1,342 ms1,519 ms87.239.249.137
Tunnel ok1,319 ms1,515 ms87.239.249.137
Tunnel ok1,343 ms1,523 ms87.239.249.137
Tunnel ok1,336 ms1,533 ms87.239.249.137
Tunnel ok1,315 ms1,500 ms87.239.249.137
Tunnel ok1,390 ms1,604 ms87.239.249.137
Tunnel ok1,312 ms1,493 ms87.239.249.137
Tunnel failedNot measuredNot measuredNot verified
Tunnel failedNot measuredNot measuredNot verified
Tunnel failedNot measuredNot measuredNot verified
Tunnel failedNot measuredNot measuredNot verified
Tunnel failedNot measuredNot measuredNot verified
Tunnel failedNot measuredNot measuredNot verified
Tunnel failedNot measuredNot measuredNot verified
Tunnel failedNot measuredNot measuredNot verified
Tunnel failedNot measuredNot measuredNot verified
Tunnel failedNot measuredNot measuredNot verified
Tunnel failedNot measuredNot measuredNot verified
Tunnel failedNot measuredNot measuredNot verified
Tunnel failedNot measuredNot measuredNot verified
Tunnel failedNot 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.