Skip to main content
Inactive — did not pass verificationLast result: 2026-10-08 10:24:43 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
47.251.25.74:443
Transport / security
TCP / REALITY
Last verified exit IP
47.251.25.74
Last verified handshake
1,281 ms
Last verified HTTPS first byte
1,596 ms
Download speed
Not measured
Source
0xRadikal verified downloadable configs
First recorded check
2026-09-27 09:10:13 UTC
Recorded tunnel checks
12
Successful tunnel checks
11
Recorded tunnel success rate
91.7%

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)
146570 09-27 09:1010-08 10:24Check time (UTC)
HTTPS first byte (ms)
162940 09-27 09:1010-08 10:24Check time (UTC)

Check history

Latest 12 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,596 ms47.251.25.74
TimeoutNot measuredNot measuredNot verified
Tunnel ok1,440 ms2,160 ms47.251.25.74
Tunnel ok719 ms1,025 ms47.251.25.74
Tunnel ok13,732 ms14,515 ms47.251.25.74
Tunnel ok2,889 ms3,710 ms47.251.25.74
Tunnel ok707 ms1,009 ms47.251.25.74
Tunnel ok14,657 ms16,294 ms47.251.25.74
Tunnel ok1,640 ms2,240 ms47.251.25.74
Tunnel ok2,085 ms2,397 ms47.251.25.74
Tunnel ok2,389 ms3,592 ms47.251.25.74
Tunnel ok2,566 ms2,879 ms47.251.25.74

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.