Skip to main content
Inactive — did not pass verificationLast result: 2026-09-11 17:48:51 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
156.146.38.170:443
Transport / security
TCP / NONE
Last verified exit IP
156.146.38.170
Last verified handshake
1,359 ms
Last verified HTTPS first byte
2,186 ms
Download speed
3.026 Mbps
Source
Coldwater Shadowsocks
First recorded check
2026-09-04 21:59:19 UTC
Recorded tunnel checks
5
Successful tunnel checks
4
Recorded tunnel success rate
80.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)
13590 2026-09-04 21:59:19 UTC: 476 ms2026-09-08 09:37:40 UTC: 483 ms2026-09-09 17:08:20 UTC: 484 ms2026-09-10 18:43:17 UTC: 1,359 ms09-04 21:5909-10 18:43Check time (UTC)
HTTPS first byte (ms)
21860 2026-09-04 21:59:19 UTC: 748 ms2026-09-08 09:37:40 UTC: 764 ms2026-09-09 17:08:20 UTC: 772 ms2026-09-10 18:43:17 UTC: 2,186 ms09-04 21:5909-10 18:43Check 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
TimeoutNot measuredNot measuredNot verified
Tunnel ok1,359 ms2,186 ms156.146.38.170
Tunnel ok484 ms772 ms156.146.38.170
Tunnel ok483 ms764 ms156.146.38.170
Tunnel ok476 ms748 ms156.146.38.170

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.