Skip to main content
Tunnel verified at last checkLast result: 2026-09-11 16:57:25 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
408 ms
Last verified HTTPS first byte
933 ms
Download speed
2.525 Mbps
Source
0xRadikal verified downloadable configs
First recorded check
2026-09-05 12:22:34 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)
5010 2026-09-05 12:22:34 UTC: 431 ms2026-09-09 01:58:36 UTC: 501 ms2026-09-09 15:34:37 UTC: 432 ms2026-09-10 16:07:54 UTC: 479 ms2026-09-11 16:57:25 UTC: 408 ms09-05 12:2209-11 16:57Check time (UTC)
HTTPS first byte (ms)
10230 2026-09-05 12:22:34 UTC: 836 ms2026-09-09 01:58:36 UTC: 886 ms2026-09-09 15:34:37 UTC: 869 ms2026-09-10 16:07:54 UTC: 1,023 ms2026-09-11 16:57:25 UTC: 933 ms09-05 12:2209-11 16:57Check 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 Shadowsocks checks, newest first
Checked (UTC)ResultHandshakeHTTPS first byteExit IP
Tunnel ok408 ms933 ms51.222.141.125
Tunnel ok479 ms1,023 ms51.222.141.125
Tunnel ok432 ms869 ms51.222.141.125
Tunnel ok501 ms886 ms51.222.141.125
Tunnel ok431 ms836 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.