Skip to main content
Inactive — did not pass verificationLast result: 2026-09-10 03:01:57 UTC

This endpoint has no current downloadable verification, or a newer check did not succeed. Previous measurements below are historical. Choose another checked Shadowsocks server.

Connection and verification

Protocol
Shadowsocks
Address
51.222.155.32:5003
Transport / security
TCP / NONE
Last verified exit IP
51.222.155.32
Last verified handshake
422 ms
Last verified HTTPS first byte
834 ms
Download speed
3.554 Mbps
Source
0xRadikal verified downloadable configs
First recorded check
2026-09-04 12:26:34 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)
41890 2026-09-04 12:26:34 UTC: 4,189 ms2026-09-07 23:56:43 UTC: 1,982 ms2026-09-10 03:01:57 UTC: 422 ms09-04 12:2609-10 03:01Check time (UTC)
HTTPS first byte (ms)
52780 2026-09-04 12:26:34 UTC: 5,278 ms2026-09-07 23:56:43 UTC: 2,907 ms2026-09-10 03:01:57 UTC: 834 ms09-04 12:2609-10 03:01Check 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 Shadowsocks checks, newest first
Checked (UTC)ResultHandshakeHTTPS first byteExit IP
Tunnel ok422 ms834 ms51.222.155.32
Tunnel ok1,982 ms2,907 ms51.222.155.32
Tunnel ok4,189 ms5,278 ms51.222.155.32

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.