Skip to main content
Tunnel verified at last checkLast result: 2026-09-11 21:14:51 UTC

Connection and verification

Protocol
VMess
Address
146.56.112.110:8888
Transport / security
TCP / NONE
Last verified exit IP
146.56.112.110
Last verified handshake
699 ms
Last verified HTTPS first byte
1,267 ms
Download speed
2.599 Mbps
Source
0xRadikal verified downloadable configs
First recorded check
2026-09-03 07:38:46 UTC
Recorded tunnel checks
6
Successful tunnel checks
5
Recorded tunnel success rate
83.3%

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)
7550 2026-09-03 07:38:46 UTC: 683 ms2026-09-06 07:39:31 UTC: 672 ms2026-09-09 18:41:00 UTC: 755 ms2026-09-10 22:09:57 UTC: 681 ms2026-09-11 21:14:51 UTC: 699 ms09-03 07:3809-11 21:14Check time (UTC)
HTTPS first byte (ms)
13110 2026-09-03 07:38:46 UTC: 1,239 ms2026-09-06 07:39:31 UTC: 1,242 ms2026-09-09 18:41:00 UTC: 1,311 ms2026-09-10 22:09:57 UTC: 1,242 ms2026-09-11 21:14:51 UTC: 1,267 ms09-03 07:3809-11 21:14Check time (UTC)

Check history

Latest 6 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 ok699 ms1,267 ms146.56.112.110
Tunnel ok681 ms1,242 ms146.56.112.110
Tunnel ok755 ms1,311 ms146.56.112.110
Tunnel failedNot measuredNot measuredNot verified
Tunnel ok672 ms1,242 ms146.56.112.110
Tunnel ok683 ms1,239 ms146.56.112.110

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.