Skip to main content
Inactive — did not pass verificationLast result: 2026-10-09 03:53:21 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.238.210.5:13779
Transport / security
TCP / REALITY
Last verified exit IP
47.238.210.5
Last verified handshake
1,235 ms
Last verified HTTPS first byte
1,684 ms
Download speed
Not measured
Source
0xRadikal verified downloadable configs
First recorded check
2026-09-19 10:41:10 UTC
Recorded tunnel checks
14
Successful tunnel checks
13
Recorded tunnel success rate
92.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)
76930 09-19 10:4110-09 03:53Check time (UTC)
HTTPS first byte (ms)
87190 09-19 10:4110-09 03:53Check time (UTC)

Check history

Latest 15 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,235 ms1,684 ms47.238.210.5
Tunnel ok2,996 ms3,648 ms47.238.210.5
Tunnel ok7,693 ms8,719 ms47.238.210.5
Tunnel ok4,705 ms5,157 ms47.238.210.5
Policy blockedNot measuredNot measuredNot verified
Tunnel ok776 ms1,504 ms47.238.210.5
Tunnel ok1,030 ms1,481 ms47.238.210.5
Tunnel ok2,587 ms3,047 ms47.238.210.5
Tunnel ok6,953 ms7,432 ms47.238.210.5
TimeoutNot measuredNot measuredNot verified
Tunnel ok1,019 ms1,471 ms47.238.210.5
Tunnel ok983 ms1,401 ms47.238.210.5
Tunnel ok1,050 ms1,472 ms47.238.210.5
Tunnel ok596 ms1,020 ms47.238.210.5
Tunnel ok3,198 ms3,618 ms47.238.210.5

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.