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

Connection and verification

Protocol
Shadowsocks
Address
51.222.141.125:445
Transport / security
TCP / NONE
Last verified exit IP
51.222.141.125
Last verified handshake
1,717 ms
Last verified HTTPS first byte
2,426 ms
Download speed
1.826 Mbps
Source
Freedom V2Ray tested configs
First recorded check
2026-09-17 00:22:49 UTC
Recorded tunnel checks
11
Successful tunnel checks
11
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

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

Tunnel handshake (ms)
44230 09-17 00:2210-09 05:21Check time (UTC)
HTTPS first byte (ms)
57250 09-17 00:2210-09 05:21Check time (UTC)

Check history

Latest 12 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 Shadowsocks checks, newest first
Checked (UTC)ResultHandshakeHTTPS first byteExit IP
Tunnel ok1,717 ms2,426 ms51.222.141.125
Preflight okNot measuredNot measuredNot verified
Tunnel ok1,632 ms2,512 ms51.222.141.125
Tunnel ok3,760 ms5,725 ms51.222.141.125
Tunnel ok2,607 ms3,704 ms51.222.141.125
Tunnel ok2,201 ms3,206 ms51.222.141.125
Tunnel ok4,423 ms4,838 ms51.222.141.125
Tunnel ok1,397 ms2,618 ms51.222.141.125
Tunnel ok1,471 ms3,002 ms51.222.141.125
Tunnel ok761 ms1,058 ms51.222.141.125
Tunnel ok404 ms785 ms51.222.141.125
Tunnel ok3,134 ms3,645 ms51.222.141.125

How to use this Shadowsocks configuration

  1. Download the current configuration while a fresh verification is available.
  2. Import it into a Shadowsocks-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 Shadowsocks 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 Shadowsocks 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.