Skip to main content
Tunnel verified at last checkLast result: 2026-10-08 21:29:46 UTC

Connection and verification

Protocol
VLESS
Address
38.207.130.15:443
Transport / security
TCP / REALITY
Last verified exit IP
38.207.130.15
Last verified handshake
1,061 ms
Last verified HTTPS first byte
1,580 ms
Download speed
2.435 Mbps
Source
0xRadikal verified downloadable configs
First recorded check
2026-09-26 08:42:54 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)
36640 09-26 08:4210-08 21:29Check time (UTC)
HTTPS first byte (ms)
48410 09-26 08:4210-08 21:29Check 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 ok1,061 ms1,580 ms38.207.130.15
Tunnel ok937 ms1,416 ms38.207.130.15
Tunnel ok1,507 ms2,032 ms38.207.130.15
Tunnel ok1,062 ms1,574 ms38.207.130.15
Tunnel ok3,664 ms4,206 ms38.207.130.15
Tunnel ok2,878 ms3,707 ms38.207.130.15
Tunnel ok1,203 ms1,759 ms38.207.130.15
Tunnel ok2,950 ms4,841 ms38.207.130.15
Tunnel ok934 ms1,423 ms38.207.130.15
Tunnel ok969 ms1,462 ms38.207.130.15
Tunnel ok1,037 ms1,624 ms38.207.130.15
Tunnel ok1,168 ms2,845 ms38.207.130.15
Tunnel ok1,091 ms1,619 ms38.207.130.15
Tunnel ok1,125 ms1,665 ms38.207.130.15

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.