Skip to main content
Tunnel verified at last checkLast result: 2026-09-12 15:18:39 UTC

Connection and verification

Protocol
VMess
Address
82.198.246.97:180
Transport / security
TCP / NONE
Last verified exit IP
149.34.251.245
Last verified handshake
574 ms
Last verified HTTPS first byte
1,014 ms
Download speed
2.856 Mbps
Source
Alexant frequently refreshed configs
First recorded check
2026-09-07 09:43:06 UTC
Recorded tunnel checks
4
Successful tunnel checks
2
Recorded tunnel success rate
50.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)
8180 2026-09-10 16:27:45 UTC: 818 ms2026-09-12 15:18:39 UTC: 574 ms09-10 16:2709-12 15:18Check time (UTC)
HTTPS first byte (ms)
12480 2026-09-10 16:27:45 UTC: 1,248 ms2026-09-12 15:18:39 UTC: 1,014 ms09-10 16:2709-12 15:18Check 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 ok574 ms1,014 ms149.34.251.245
Tunnel failedNot measuredNot measuredNot verified
Tunnel ok818 ms1,248 ms149.34.251.245
TimeoutNot measuredNot measuredNot verified
Policy blockedNot 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.