Skip to main content
Inactive — did not pass verificationLast result: 2026-09-09 14:20:23 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
38.180.186.202:443
Transport / security
TCP / REALITY
Last verified exit IP
38.180.186.202
Last verified handshake
1,411 ms
Last verified HTTPS first byte
1,892 ms
Download speed
1.704 Mbps
Source
Firmfox Proxify mixed configs
First recorded check
2026-09-09 13:45:17 UTC
Recorded tunnel checks
3
Successful tunnel checks
2
Recorded tunnel success rate
66.7%

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)
17060 2026-09-09 14:05:19 UTC: 1,706 ms2026-09-09 14:20:23 UTC: 1,411 ms09-09 14:0509-09 14:20Check time (UTC)
HTTPS first byte (ms)
21940 2026-09-09 14:05:19 UTC: 2,194 ms2026-09-09 14:20:23 UTC: 1,892 ms09-09 14:0509-09 14:20Check time (UTC)

Check history

Latest 3 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,411 ms1,892 ms38.180.186.202
Tunnel ok1,706 ms2,194 ms38.180.186.202
TimeoutNot measuredNot measuredNot verified

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.