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

Connection and verification

Protocol
VMess
Address
20.235.220.189:443
Transport / security
WEBSOCKET / TLS
Last verified exit IP
47.83.19.148
Last verified handshake
2,168 ms
Last verified HTTPS first byte
2,740 ms
Download speed
Not measured
Source
Alexant frequently refreshed configs
First recorded check
2026-09-06 10:23:43 UTC
Recorded tunnel checks
3
Successful tunnel checks
2
Recorded tunnel success rate
66.7%

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)
26570 2026-09-11 02:09:18 UTC: 2,657 ms2026-09-12 01:11:46 UTC: 2,168 ms09-11 02:0909-12 01:11Check time (UTC)
HTTPS first byte (ms)
32490 2026-09-11 02:09:18 UTC: 3,249 ms2026-09-12 01:11:46 UTC: 2,740 ms09-11 02:0909-12 01:11Check 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 ok2,168 ms2,740 ms47.83.19.148
Tunnel ok2,657 ms3,249 ms47.83.19.148
Tunnel failedNot measuredNot measuredNot verified
Policy blockedNot 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.