Skip to main content
Tunnel verified at last checkLast result: 2026-09-11 17:07:13 UTC

Connection and verification

Protocol
VMess
Address
82.198.246.250:180
Transport / security
TCP / NONE
Last verified exit IP
149.34.251.250
Last verified handshake
519 ms
Last verified HTTPS first byte
858 ms
Download speed
3.214 Mbps
Source
Alexant frequently refreshed configs
First recorded check
2026-09-07 09:55:53 UTC
Recorded tunnel checks
3
Successful tunnel checks
3
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)
13700 2026-09-09 17:18:04 UTC: 631 ms2026-09-10 18:06:58 UTC: 1,370 ms2026-09-11 17:07:13 UTC: 519 ms09-09 17:1809-11 17:07Check time (UTC)
HTTPS first byte (ms)
21290 2026-09-09 17:18:04 UTC: 1,058 ms2026-09-10 18:06:58 UTC: 2,129 ms2026-09-11 17:07:13 UTC: 858 ms09-09 17:1809-11 17:07Check time (UTC)

Check history

Latest 4 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 ok519 ms858 ms149.34.251.250
Tunnel ok1,370 ms2,129 ms149.34.251.250
Tunnel ok631 ms1,058 ms149.34.251.250
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.