Skip to main content
Tunnel verified at last checkLast result: 2026-09-10 19:48:19 UTC

Connection and verification

Protocol
Shadowsocks
Address
156.146.38.168:443
Transport / security
TCP / NONE
Last verified exit IP
156.146.38.168
Last verified handshake
1,272 ms
Last verified HTTPS first byte
2,223 ms
Download speed
2.516 Mbps
Source
Coldwater Shadowsocks
First recorded check
2026-09-04 22:44:48 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)
12720 2026-09-04 22:44:48 UTC: 471 ms2026-09-08 10:21:27 UTC: 702 ms2026-09-08 10:36:21 UTC: 740 ms2026-09-09 17:27:33 UTC: 468 ms2026-09-10 19:48:19 UTC: 1,272 ms09-04 22:4409-10 19:48Check time (UTC)
HTTPS first byte (ms)
22230 2026-09-04 22:44:48 UTC: 745 ms2026-09-08 10:21:27 UTC: 1,113 ms2026-09-08 10:36:21 UTC: 1,171 ms2026-09-09 17:27:33 UTC: 748 ms2026-09-10 19:48:19 UTC: 2,223 ms09-04 22:4409-10 19:48Check 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 ok1,272 ms2,223 ms156.146.38.168
Tunnel ok468 ms748 ms156.146.38.168
Tunnel ok740 ms1,171 ms156.146.38.168
Tunnel ok702 ms1,113 ms156.146.38.168
Tunnel ok471 ms745 ms156.146.38.168

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.