Skip to main content
Tunnel verified at last checkLast result: 2026-09-11 12:03:54 UTC

Connection and verification

Protocol
Shadowsocks
Address
156.146.38.169:443
Transport / security
TCP / NONE
Last verified exit IP
156.146.38.169
Last verified handshake
819 ms
Last verified HTTPS first byte
1,288 ms
Download speed
2.081 Mbps
Source
Freedom V2Ray tested configs
First recorded check
2026-09-04 03:07:00 UTC
Recorded tunnel checks
4
Successful tunnel checks
4
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)
18260 2026-09-04 03:07:00 UTC: 464 ms2026-09-07 05:33:09 UTC: 1,826 ms2026-09-10 01:47:02 UTC: 458 ms2026-09-11 12:03:54 UTC: 819 ms09-04 03:0709-11 12:03Check time (UTC)
HTTPS first byte (ms)
23110 2026-09-04 03:07:00 UTC: 742 ms2026-09-07 05:33:09 UTC: 2,311 ms2026-09-10 01:47:02 UTC: 730 ms2026-09-11 12:03:54 UTC: 1,288 ms09-04 03:0709-11 12:03Check 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 ok819 ms1,288 ms156.146.38.169
Tunnel ok458 ms730 ms156.146.38.169
Tunnel ok1,826 ms2,311 ms156.146.38.169
Tunnel ok464 ms742 ms156.146.38.169

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.