Skip to main content
Inactive — did not pass verificationLast result: 2026-10-22 02:59:34 UTC

This endpoint has no current downloadable verification, or a newer check did not succeed. Previous measurements below are historical. Choose another checked VMess server.

Connection and verification

Protocol
VMess
Address
nl-2a972c8052.shamanapp.online:33736
Transport / security
WEBSOCKET / NONE
Last verified exit IP
31.59.150.197
Last verified handshake
645 ms
Last verified HTTPS first byte
869 ms
Download speed
6.76 Mbps
Source
Matin VMess
First recorded check
2026-10-08 00:09:27 UTC
Recorded tunnel checks
13
Successful tunnel checks
8
Recorded tunnel success rate
61.5%

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)
40560 10-08 00:0910-18 06:15Check time (UTC)
HTTPS first byte (ms)
48430 10-08 00:0910-18 06:15Check time (UTC)

Check history

Latest 13 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 failedNot measuredNot measuredNot verified
Tunnel failedNot measuredNot measuredNot verified
Tunnel ok645 ms869 ms31.59.150.197
Tunnel ok731 ms943 ms147.45.61.188
Tunnel failedNot measuredNot measuredNot verified
Tunnel failedNot measuredNot measuredNot verified
Tunnel ok2,024 ms2,740 ms147.45.61.188
Tunnel ok1,641 ms1,884 ms147.45.61.188
Tunnel failedNot measuredNot measuredNot verified
Tunnel ok632 ms838 ms94.183.221.234
Tunnel ok2,230 ms3,219 ms147.45.61.188
Tunnel ok4,056 ms4,843 ms147.45.61.188
Tunnel ok2,570 ms3,481 ms147.45.61.188

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.