Skip to main content
Inactive — did not pass verificationLast result: 2026-09-09 15:29:50 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
54.37.136.194:2053
Transport / security
TCP / REALITY
Last verified exit IP
54.37.136.194
Last verified handshake
407 ms
Last verified HTTPS first byte
642 ms
Download speed
6.296 Mbps
Source
Au1rxx verified downloadable configs
First recorded check
2026-09-05 22:04:20 UTC
Recorded tunnel checks
2
Successful tunnel checks
2
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

Tunnel handshake (ms)
4070 2026-09-05 22:04:20 UTC: 364 ms2026-09-09 15:29:50 UTC: 407 ms09-05 22:0409-09 15:29Check time (UTC)
HTTPS first byte (ms)
6420 2026-09-05 22:04:20 UTC: 578 ms2026-09-09 15:29:50 UTC: 642 ms09-05 22:0409-09 15:29Check time (UTC)

Check history

Latest 2 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 ok407 ms642 ms54.37.136.194
Tunnel ok364 ms578 ms54.37.136.194

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.