Skip to main content
Tunnel verified at last checkLast result: 2026-09-10 21:39:44 UTC

Connection and verification

Protocol
VMess
Address
149.88.23.202:18000
Transport / security
TCP / NONE
Last verified exit IP
149.88.23.202
Last verified handshake
513 ms
Last verified HTTPS first byte
989 ms
Download speed
3.344 Mbps
Source
0xRadikal verified downloadable configs
First recorded check
2026-09-03 20:32:31 UTC
Recorded tunnel checks
5
Successful tunnel checks
5
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)
5460 2026-09-03 20:32:31 UTC: 521 ms2026-09-06 20:56:37 UTC: 546 ms2026-09-06 21:12:01 UTC: 525 ms2026-09-09 18:29:36 UTC: 516 ms2026-09-10 21:39:44 UTC: 513 ms09-03 20:3209-10 21:39Check time (UTC)
HTTPS first byte (ms)
10540 2026-09-03 20:32:31 UTC: 1,016 ms2026-09-06 20:56:37 UTC: 1,054 ms2026-09-06 21:12:01 UTC: 1,010 ms2026-09-09 18:29:36 UTC: 1,031 ms2026-09-10 21:39:44 UTC: 989 ms09-03 20:3209-10 21:39Check 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 ok513 ms989 ms149.88.23.202
Tunnel ok516 ms1,031 ms149.88.23.202
Tunnel ok525 ms1,010 ms149.88.23.202
Tunnel ok546 ms1,054 ms149.88.23.202
Tunnel ok521 ms1,016 ms149.88.23.202

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.