Skip to main content
Inactive — did not pass verificationLast result: 2026-09-11 04:23:09 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
141.164.45.187:8888
Transport / security
TCP / NONE
Last verified exit IP
141.164.45.187
Last verified handshake
9,003 ms
Last verified HTTPS first byte
10,089 ms
Download speed
Not measured
Source
0xRadikal verified downloadable configs
First recorded check
2026-09-05 07:54:17 UTC
Recorded tunnel checks
4
Successful tunnel checks
2
Recorded tunnel success rate
50.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)
90030 2026-09-05 07:54:17 UTC: 1,430 ms2026-09-11 04:23:09 UTC: 9,003 ms09-05 07:5409-11 04:23Check time (UTC)
HTTPS first byte (ms)
100890 2026-09-05 07:54:17 UTC: 2,739 ms2026-09-11 04:23:09 UTC: 10,089 ms09-05 07:5409-11 04:23Check time (UTC)

Check history

Latest 4 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 ok9,003 ms10,089 ms141.164.45.187
TimeoutNot measuredNot measuredNot verified
TimeoutNot measuredNot measuredNot verified
Tunnel ok1,430 ms2,739 ms141.164.45.187

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.