Skip to main content
Tunnel verified at last checkLast result: 2026-09-09 18:23:34 UTC

Connection and verification

Protocol
VMess
Address
84.17.41.2:18000
Transport / security
TCP / NONE
Last verified exit IP
84.17.41.2
Last verified handshake
514 ms
Last verified HTTPS first byte
977 ms
Download speed
2.929 Mbps
Source
0xRadikal verified downloadable configs
First recorded check
2026-09-03 20:30:55 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)
5640 2026-09-03 20:30:55 UTC: 494 ms2026-09-06 20:56:25 UTC: 564 ms2026-09-09 18:23:34 UTC: 514 ms09-03 20:3009-09 18:23Check time (UTC)
HTTPS first byte (ms)
9770 2026-09-03 20:30:55 UTC: 819 ms2026-09-06 20:56:25 UTC: 886 ms2026-09-09 18:23:34 UTC: 977 ms09-03 20:3009-09 18:23Check time (UTC)

Check history

Latest 3 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 ok514 ms977 ms84.17.41.2
Tunnel ok564 ms886 ms84.17.41.2
Tunnel ok494 ms819 ms84.17.41.2

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.