Skip to main content
Inactive — did not pass verificationLast result: 2026-09-11 21:00:02 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
47.244.120.197:23026
Transport / security
WEBSOCKET / NONE
Last verified exit IP
47.244.120.197
Last verified handshake
4,263 ms
Last verified HTTPS first byte
4,781 ms
Download speed
Not measured
Source
Barry VMess
First recorded check
2026-09-04 16:26:37 UTC
Recorded tunnel checks
5
Successful tunnel checks
3
Recorded tunnel success rate
60.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)
109030 2026-09-04 16:26:37 UTC: 10,903 ms2026-09-09 18:36:40 UTC: 1,047 ms2026-09-10 21:59:50 UTC: 4,263 ms09-04 16:2609-10 21:59Check time (UTC)
HTTPS first byte (ms)
114180 2026-09-04 16:26:37 UTC: 11,418 ms2026-09-09 18:36:40 UTC: 1,554 ms2026-09-10 21:59:50 UTC: 4,781 ms09-04 16:2609-10 21:59Check time (UTC)

Check history

Latest 5 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 failedNot measuredNot measuredNot verified
Tunnel ok4,263 ms4,781 ms47.244.120.197
Tunnel ok1,047 ms1,554 ms47.244.120.197
Tunnel failedNot measuredNot measuredNot verified
Tunnel ok10,903 ms11,418 ms47.244.120.197

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.