Skip to main content
Inactive — did not pass verificationLast result: 2026-10-09 06:54:47 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
137.74.16.237:443
Transport / security
TCP / REALITY
Last verified exit IP
137.74.16.237
Last verified handshake
3,770 ms
Last verified HTTPS first byte
4,524 ms
Download speed
2.807 Mbps
Source
0xRadikal verified downloadable configs
First recorded check
2026-09-25 11:20:06 UTC
Recorded tunnel checks
10
Successful tunnel checks
10
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)
37700 09-25 11:2010-09 06:54Check time (UTC)
HTTPS first byte (ms)
45240 09-25 11:2010-09 06:54Check time (UTC)

Check history

Latest 10 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 ok3,770 ms4,524 ms137.74.16.237
Tunnel ok827 ms1,055 ms137.74.16.237
Tunnel ok422 ms629 ms137.74.16.237
Tunnel ok403 ms611 ms137.74.16.237
Tunnel ok388 ms584 ms137.74.16.237
Tunnel ok661 ms891 ms137.74.16.237
Tunnel ok480 ms694 ms137.74.16.237
Tunnel ok409 ms628 ms137.74.16.237
Tunnel ok384 ms593 ms137.74.16.237
Tunnel ok2,183 ms2,394 ms137.74.16.237

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.