Skip to main content
Tunnel verified at last checkLast result: 2026-09-12 11:27:48 UTC

Connection and verification

Protocol
VMess
Address
8.210.108.58:443
Transport / security
WEBSOCKET / TLS
Last verified exit IP
8.210.108.58
Last verified handshake
8,413 ms
Last verified HTTPS first byte
9,210 ms
Download speed
Not measured
Source
Alexant frequently refreshed configs
First recorded check
2026-09-06 17:53:58 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)
84130 2026-09-10 00:15:56 UTC: 7,381 ms2026-09-11 12:13:21 UTC: 1,238 ms2026-09-12 11:27:48 UTC: 8,413 ms09-10 00:1509-12 11:27Check time (UTC)
HTTPS first byte (ms)
92100 2026-09-10 00:15:56 UTC: 8,842 ms2026-09-11 12:13:21 UTC: 1,770 ms2026-09-12 11:27:48 UTC: 9,210 ms09-10 00:1509-12 11:27Check 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 ok8,413 ms9,210 ms8.210.108.58
Tunnel ok1,238 ms1,770 ms8.210.108.58
Tunnel ok7,381 ms8,842 ms8.210.108.58
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.