Skip to main content
Tunnel verified at last checkLast result: 2026-10-09 03:25:08 UTC

Connection and verification

Protocol
VLESS
Address
38.207.130.15:443
Transport / security
TCP / REALITY
Last verified exit IP
136.175.179.4
Last verified handshake
1,338 ms
Last verified HTTPS first byte
1,856 ms
Download speed
1.984 Mbps
Source
0xRadikal verified downloadable configs
First recorded check
2026-09-22 13:00:04 UTC
Recorded tunnel checks
18
Successful tunnel checks
18
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)
51290 09-22 13:0010-09 03:25Check time (UTC)
HTTPS first byte (ms)
80520 09-22 13:0010-09 03:25Check time (UTC)

Check history

Latest 18 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,338 ms1,856 ms136.175.179.4
Tunnel ok1,513 ms2,065 ms136.175.179.4
Tunnel ok1,276 ms1,752 ms136.175.179.4
Tunnel ok1,430 ms1,954 ms136.175.179.4
Tunnel ok1,323 ms1,814 ms136.175.179.4
Tunnel ok5,129 ms7,428 ms136.175.179.4
Tunnel ok1,291 ms1,773 ms136.175.179.4
Tunnel ok1,546 ms2,076 ms136.175.179.4
Tunnel ok1,682 ms2,225 ms38.125.120.83
Tunnel ok1,312 ms1,792 ms136.175.179.4
Tunnel ok1,587 ms2,129 ms136.175.179.4
Tunnel ok1,856 ms2,412 ms136.175.179.4
Tunnel ok3,678 ms8,052 ms136.175.179.4
Tunnel ok1,767 ms2,303 ms136.175.179.4
Tunnel ok1,454 ms1,979 ms136.175.179.4
Tunnel ok2,688 ms3,205 ms136.175.179.4
Tunnel ok1,581 ms2,069 ms136.175.179.4
Tunnel ok2,066 ms2,565 ms136.175.179.4

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.