Skip to main content
Tunnel verified at last checkLast result: 2026-10-08 20:53:50 UTC

Connection and verification

Protocol
VMess
Address
186.190.211.67:443
Transport / security
WEBSOCKET / TLS
Last verified exit IP
186.190.211.67
Last verified handshake
923 ms
Last verified HTTPS first byte
1,278 ms
Download speed
Not measured
Source
v2go hourly full-tunnel tested configs
First recorded check
2026-09-22 22:53:18 UTC
Recorded tunnel checks
13
Successful tunnel checks
12
Recorded tunnel success rate
92.3%

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

Hover or focus a point for check details. Click or tap to keep them open.

Tunnel handshake (ms)
41860 09-22 22:5310-08 20:53Check time (UTC)
HTTPS first byte (ms)
56990 09-22 22:5310-08 20:53Check time (UTC)

Check history

Latest 13 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 ok923 ms1,278 ms186.190.211.67
Tunnel ok1,425 ms1,642 ms186.190.211.67
Tunnel ok557 ms844 ms186.190.211.67
Tunnel ok4,186 ms5,699 ms186.190.211.67
Tunnel ok453 ms714 ms186.190.211.67
TimeoutNot measuredNot measuredNot verified
Tunnel ok612 ms837 ms186.190.211.67
Tunnel ok538 ms710 ms186.190.211.67
Tunnel ok441 ms634 ms186.190.211.67
Tunnel ok3,076 ms3,943 ms186.190.211.67
Tunnel ok835 ms1,452 ms186.190.211.67
Tunnel ok2,297 ms3,272 ms186.190.211.67
Tunnel ok542 ms756 ms186.190.211.67

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.

This saved detail page remains available with its check history. Search indexing requires current successful full-tunnel verification, real measurements and an available configuration.