Skip to main content
Inactive — did not pass verificationLast result: 2026-09-11 02:21:57 UTC

This endpoint has no current downloadable verification, or a newer check did not succeed. Previous measurements below are historical. Choose another checked VMess server.

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
293 ms
Last verified HTTPS first byte
509 ms
Download speed
5.206 Mbps
Source
Au1rxx verified downloadable configs
First recorded check
2026-09-03 13:24:01 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)
55620 2026-09-03 13:24:01 UTC: 299 ms2026-09-06 13:24:08 UTC: 790 ms2026-09-09 13:24:56 UTC: 993 ms2026-09-09 20:22:30 UTC: 5,562 ms2026-09-11 02:21:57 UTC: 293 ms09-03 13:2409-11 02:21Check time (UTC)
HTTPS first byte (ms)
64390 2026-09-03 13:24:01 UTC: 508 ms2026-09-06 13:24:08 UTC: 1,000 ms2026-09-09 13:24:56 UTC: 1,208 ms2026-09-09 20:22:30 UTC: 6,439 ms2026-09-11 02:21:57 UTC: 509 ms09-03 13:2409-11 02:21Check 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 ok293 ms509 ms66.163.117.58
Tunnel ok5,562 ms6,439 ms66.163.117.58
Tunnel ok993 ms1,208 ms66.163.117.58
Tunnel ok790 ms1,000 ms66.163.117.58
Tunnel ok299 ms508 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.