Skip to main content
Inactive — did not pass verificationLast result: 2026-09-11 09:22:03 UTC

This endpoint has no current downloadable verification, or a newer check did not succeed. Previous measurements below are historical. Choose another checked VMess server.

Connection and verification

Protocol
VMess
Address
140.238.2.250:443
Transport / security
TCP / NONE
Last verified exit IP
140.238.2.250
Last verified handshake
1,281 ms
Last verified HTTPS first byte
2,057 ms
Download speed
1.871 Mbps
Source
Barry VMess
First recorded check
2026-09-03 18:25:38 UTC
Recorded tunnel checks
4
Successful tunnel checks
4
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)
12810 2026-09-03 18:25:38 UTC: 754 ms2026-09-06 22:23:48 UTC: 749 ms2026-09-10 00:22:12 UTC: 760 ms2026-09-11 09:22:03 UTC: 1,281 ms09-03 18:2509-11 09:22Check time (UTC)
HTTPS first byte (ms)
20570 2026-09-03 18:25:38 UTC: 1,354 ms2026-09-06 22:23:48 UTC: 1,345 ms2026-09-10 00:22:12 UTC: 1,368 ms2026-09-11 09:22:03 UTC: 2,057 ms09-03 18:2509-11 09:22Check time (UTC)

Check history

Latest 4 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 VMess checks, newest first
Checked (UTC)ResultHandshakeHTTPS first byteExit IP
Tunnel ok1,281 ms2,057 ms140.238.2.250
Tunnel ok760 ms1,368 ms140.238.2.250
Tunnel ok749 ms1,345 ms140.238.2.250
Tunnel ok754 ms1,354 ms140.238.2.250

How to use this VMess configuration

  1. Download the current configuration while a fresh verification is available.
  2. Import it into a VMess-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 VMess 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 VMess guide, our checking methodology and public VPN risks.