Skip to main content
Inactive — did not pass verificationLast result: 2026-09-11 19:34:18 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.95.29.163:2083
Transport / security
TCP / NONE
Last verified exit IP
141.95.29.163
Last verified handshake
2,084 ms
Last verified HTTPS first byte
2,486 ms
Download speed
2.105 Mbps
Source
Barry Shadowsocks
First recorded check
2026-09-07 08:43:42 UTC
Recorded tunnel checks
4
Successful tunnel checks
3
Recorded tunnel success rate
75.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)
38180 2026-09-07 08:43:42 UTC: 3,818 ms2026-09-09 17:40:05 UTC: 316 ms2026-09-10 20:13:07 UTC: 2,084 ms09-07 08:4309-10 20:13Check time (UTC)
HTTPS first byte (ms)
41400 2026-09-07 08:43:42 UTC: 4,140 ms2026-09-09 17:40:05 UTC: 618 ms2026-09-10 20:13:07 UTC: 2,486 ms09-07 08:4309-10 20:13Check 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
TimeoutNot measuredNot measuredNot verified
Tunnel ok2,084 ms2,486 ms141.95.29.163
Tunnel ok316 ms618 ms141.95.29.163
Tunnel ok3,818 ms4,140 ms141.95.29.163

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.