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

Connection and verification

Protocol
VMess
Address
151.243.173.119:33736
Transport / security
WEBSOCKET / NONE
Last verified exit IP
151.243.173.119
Last verified handshake
298 ms
Last verified HTTPS first byte
476 ms
Download speed
7.533 Mbps
Source
Au1rxx verified downloadable configs
First recorded check
2026-09-18 22:22:42 UTC
Recorded tunnel checks
15
Successful tunnel checks
15
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

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

Tunnel handshake (ms)
84100 09-18 22:2210-08 21:37Check time (UTC)
HTTPS first byte (ms)
96640 09-18 22:2210-08 21:37Check time (UTC)

Check history

Latest 15 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 ok298 ms476 ms151.243.173.119
Tunnel ok291 ms464 ms151.243.173.119
Tunnel ok1,183 ms1,630 ms151.243.173.119
Tunnel ok302 ms486 ms151.243.173.119
Tunnel ok389 ms586 ms151.243.173.119
Tunnel ok314 ms501 ms151.243.173.119
Tunnel ok313 ms493 ms151.243.173.119
Tunnel ok293 ms468 ms151.243.173.119
Tunnel ok319 ms504 ms151.243.173.119
Tunnel ok336 ms518 ms151.243.173.119
Tunnel ok293 ms472 ms151.243.173.119
Tunnel ok390 ms747 ms151.243.173.119
Tunnel ok8,410 ms9,664 ms151.243.173.119
Tunnel ok437 ms681 ms151.243.173.119
Tunnel ok340 ms535 ms151.243.173.119

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.