Skip to main content
Inactive — did not pass verificationLast result: 2026-09-10 23:06:27 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
23.162.200.198:18000
Transport / security
TCP / NONE
Last verified exit IP
23.162.200.198
Last verified handshake
417 ms
Last verified HTTPS first byte
638 ms
Download speed
4.492 Mbps
Source
Barry VMess
First recorded check
2026-09-04 18:32:29 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)
4170 2026-09-04 18:32:29 UTC: 396 ms2026-09-07 22:12:38 UTC: 398 ms2026-09-09 18:50:51 UTC: 406 ms2026-09-10 23:06:27 UTC: 417 ms09-04 18:3209-10 23:06Check time (UTC)
HTTPS first byte (ms)
6380 2026-09-04 18:32:29 UTC: 615 ms2026-09-07 22:12:38 UTC: 609 ms2026-09-09 18:50:51 UTC: 619 ms2026-09-10 23:06:27 UTC: 638 ms09-04 18:3209-10 23:06Check 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 ok417 ms638 ms23.162.200.198
Tunnel ok406 ms619 ms23.162.200.198
Tunnel ok398 ms609 ms23.162.200.198
Tunnel ok396 ms615 ms23.162.200.198

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.