Skip to main content
Tunnel verified at last checkLast result: 2026-10-23 07:04:03 UTC

Connection and verification

Protocol
VMess
Address
145.239.55.210:80
Transport / security
WEBSOCKET / NONE
Last verified exit IP
145.239.55.210
Last verified handshake
4,392 ms
Last verified HTTPS first byte
4,990 ms
Download speed
2.562 Mbps
Source
Freedom V2Ray tested configs
First recorded check
2026-10-06 01:23:14 UTC
Recorded tunnel checks
15
Successful tunnel checks
7
Recorded tunnel success rate
46.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

Hover or focus a point for check details. Click or tap to keep them open.

Tunnel handshake (ms)
43920 10-06 01:2310-23 07:04Check time (UTC)
HTTPS first byte (ms)
49900 10-06 01:2310-23 07:04Check time (UTC)

Check history

Latest 15 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 ok4,392 ms4,990 ms145.239.55.210
TimeoutNot measuredNot measuredNot verified
Tunnel ok923 ms1,379 ms145.239.55.210
Tunnel ok954 ms1,332 ms145.239.55.210
Tunnel ok659 ms1,015 ms145.239.55.210
Tunnel ok1,017 ms1,427 ms145.239.55.210
Tunnel ok1,835 ms2,476 ms145.239.55.210
Tunnel failedNot measuredNot measuredNot verified
Tunnel failedNot measuredNot measuredNot verified
Tunnel failedNot measuredNot measuredNot verified
Tunnel failedNot measuredNot measuredNot verified
Tunnel failedNot measuredNot measuredNot verified
Tunnel failedNot measuredNot measuredNot verified
Tunnel failedNot measuredNot measuredNot verified
Tunnel ok366 ms569 ms145.239.55.210

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.