Skip to main content
Tunnel verified at last checkLast result: 2026-09-10 14:27:46 UTC

Connection and verification

Protocol
VMess
Address
82.198.246.97:180
Transport / security
TCP / NONE
Last verified exit IP
149.34.251.245
Last verified handshake
523 ms
Last verified HTTPS first byte
847 ms
Download speed
1.29 Mbps
Source
0xRadikal verified downloadable configs
First recorded check
2026-09-03 20:27:18 UTC
Recorded tunnel checks
5
Successful tunnel checks
5
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)
6110 2026-09-03 20:27:18 UTC: 611 ms2026-09-06 20:52:49 UTC: 515 ms2026-09-09 14:10:45 UTC: 539 ms2026-09-09 14:26:18 UTC: 560 ms2026-09-10 14:27:46 UTC: 523 ms09-03 20:2709-10 14:27Check time (UTC)
HTTPS first byte (ms)
9480 2026-09-03 20:27:18 UTC: 948 ms2026-09-06 20:52:49 UTC: 845 ms2026-09-09 14:10:45 UTC: 877 ms2026-09-09 14:26:18 UTC: 918 ms2026-09-10 14:27:46 UTC: 847 ms09-03 20:2709-10 14:27Check 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 ok523 ms847 ms149.34.251.245
Tunnel ok560 ms918 ms149.34.251.245
Tunnel ok539 ms877 ms149.34.251.245
Tunnel ok515 ms845 ms149.34.251.245
Tunnel ok611 ms948 ms149.34.251.245

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.