Skip to main content
Tunnel verified at last checkLast result: 2026-09-12 03:22:54 UTC

Connection and verification

Protocol
VMess
Address
134.195.196.211:18000
Transport / security
TCP / NONE
Last verified exit IP
134.195.196.211
Last verified handshake
393 ms
Last verified HTTPS first byte
604 ms
Download speed
3.988 Mbps
Source
Au1rxx verified downloadable configs
First recorded check
2026-09-05 17:50:13 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)
4360 2026-09-05 17:50:13 UTC: 405 ms2026-09-09 20:59:19 UTC: 436 ms2026-09-11 04:13:42 UTC: 419 ms2026-09-12 03:22:54 UTC: 393 ms09-05 17:5009-12 03:22Check time (UTC)
HTTPS first byte (ms)
6770 2026-09-05 17:50:13 UTC: 612 ms2026-09-09 20:59:19 UTC: 677 ms2026-09-11 04:13:42 UTC: 660 ms2026-09-12 03:22:54 UTC: 604 ms09-05 17:5009-12 03:22Check 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 ok393 ms604 ms134.195.196.211
Tunnel ok419 ms660 ms134.195.196.211
Tunnel ok436 ms677 ms134.195.196.211
Policy blockedNot measuredNot measuredNot verified
Tunnel ok405 ms612 ms134.195.196.211

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.