Skip to main content
Tunnel verified at last checkLast result: 2026-09-10 00:34:06 UTC

Connection and verification

Protocol
VMess
Address
66.163.117.58:22324
Transport / security
TCP / NONE
Last verified exit IP
66.163.117.58
Last verified handshake
5,403 ms
Last verified HTTPS first byte
5,630 ms
Download speed
3.985 Mbps
Source
Barry VMess
First recorded check
2026-09-03 12:45:05 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)
54030 2026-09-03 12:45:05 UTC: 264 ms2026-09-06 12:45:40 UTC: 342 ms2026-09-06 13:01:22 UTC: 238 ms2026-09-09 13:01:48 UTC: 3,651 ms2026-09-10 00:34:06 UTC: 5,403 ms09-03 12:4509-10 00:34Check time (UTC)
HTTPS first byte (ms)
56300 2026-09-03 12:45:05 UTC: 464 ms2026-09-06 12:45:40 UTC: 692 ms2026-09-06 13:01:22 UTC: 445 ms2026-09-09 13:01:48 UTC: 4,193 ms2026-09-10 00:34:06 UTC: 5,630 ms09-03 12:4509-10 00:34Check 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 ok5,403 ms5,630 ms66.163.117.58
Tunnel ok3,651 ms4,193 ms66.163.117.58
Tunnel ok238 ms445 ms66.163.117.58
Tunnel ok342 ms692 ms66.163.117.58
Tunnel ok264 ms464 ms66.163.117.58

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.