Skip to main content
Tunnel verified at last checkLast result: 2026-10-09 01:24:34 UTC

Connection and verification

Protocol
VLESS
Address
138.124.180.137:443
Transport / security
TCP / REALITY
Last verified exit IP
138.124.180.137
Last verified handshake
463 ms
Last verified HTTPS first byte
653 ms
Download speed
7.628 Mbps
Source
0xRadikal verified downloadable configs
First recorded check
2026-09-13 20:02:50 UTC
Recorded tunnel checks
26
Successful tunnel checks
26
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)
10840 09-13 20:0210-09 01:24Check time (UTC)
HTTPS first byte (ms)
15350 09-13 20:0210-09 01:24Check time (UTC)

Check history

Latest 26 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 ok463 ms653 ms138.124.180.137
Tunnel ok317 ms517 ms138.124.180.137
Tunnel ok246 ms431 ms138.124.180.137
Tunnel ok438 ms723 ms138.124.180.137
Tunnel ok273 ms466 ms138.124.180.137
Tunnel ok437 ms631 ms138.124.180.137
Tunnel ok322 ms515 ms138.124.180.137
Tunnel ok467 ms653 ms138.124.180.137
Tunnel ok445 ms631 ms138.124.180.137
Tunnel ok335 ms522 ms138.124.180.137
Tunnel ok327 ms516 ms138.124.180.137
Tunnel ok542 ms729 ms138.124.180.137
Tunnel ok1,084 ms1,442 ms138.124.180.137
Tunnel ok914 ms1,535 ms138.124.180.137
Tunnel ok248 ms452 ms138.124.180.137
Tunnel ok402 ms594 ms138.124.180.137
Tunnel ok471 ms661 ms138.124.180.137
Tunnel ok255 ms441 ms138.124.180.137
Tunnel ok293 ms494 ms138.124.180.137
Tunnel ok243 ms435 ms138.124.180.137
Tunnel ok224 ms408 ms138.124.180.137
Tunnel ok238 ms423 ms138.124.180.137
Tunnel ok308 ms507 ms138.124.180.137
Tunnel ok505 ms699 ms138.124.180.137
Tunnel ok280 ms520 ms138.124.180.137
Tunnel ok477 ms672 ms138.124.180.137

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.