Skip to main content
Tunnel verified at last checkLast result: 2026-09-11 00:55:27 UTC

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
390 ms
Last verified HTTPS first byte
605 ms
Download speed
4.569 Mbps
Source
0xRadikal verified downloadable configs
First recorded check
2026-09-03 20:40:14 UTC
Recorded tunnel checks
4
Successful tunnel checks
3
Recorded tunnel success rate
75.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)
54320 2026-09-03 20:40:14 UTC: 5,432 ms2026-09-09 19:44:08 UTC: 404 ms2026-09-11 00:55:27 UTC: 390 ms09-03 20:4009-11 00:55Check time (UTC)
HTTPS first byte (ms)
56490 2026-09-03 20:40:14 UTC: 5,649 ms2026-09-09 19:44:08 UTC: 611 ms2026-09-11 00:55:27 UTC: 605 ms09-03 20:4009-11 00:55Check 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 ok390 ms605 ms23.162.200.198
Tunnel ok404 ms611 ms23.162.200.198
Tunnel failedNot measuredNot measuredNot verified
Tunnel ok5,432 ms5,649 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.