Skip to main content
Tunnel verified at last checkLast result: 2026-10-09 09:58:12 UTC

Connection and verification

Protocol
VMess
Address
132.145.80.230:80
Transport / security
WEBSOCKET / NONE
Last verified exit IP
132.145.80.230
Last verified handshake
954 ms
Last verified HTTPS first byte
1,464 ms
Download speed
2.362 Mbps
Source
Au1rxx verified downloadable configs
First recorded check
2026-09-22 04:37:29 UTC
Recorded tunnel checks
10
Successful tunnel checks
7
Recorded tunnel success rate
70.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)
9800 09-29 12:2210-09 09:58Check time (UTC)
HTTPS first byte (ms)
19390 09-29 12:2210-09 09:58Check time (UTC)

Check history

Latest 12 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 ok954 ms1,464 ms132.145.80.230
Tunnel failedNot measuredNot measuredNot verified
Tunnel ok949 ms1,447 ms132.145.80.230
Tunnel ok928 ms1,420 ms132.145.80.230
Preflight failedNot measuredNot measuredNot verified
Tunnel ok963 ms1,484 ms132.145.80.230
Tunnel ok928 ms1,422 ms132.145.80.230
Policy blockedNot measuredNot measuredNot verified
Tunnel ok930 ms1,939 ms132.145.80.230
Tunnel failedNot measuredNot measuredNot verified
Tunnel ok980 ms1,518 ms132.145.80.230
Tunnel failedNot measuredNot measuredNot verified

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.