Skip to main content
Tunnel verified at last checkLast result: 2026-09-11 17:47:51 UTC

Connection and verification

Protocol
Shadowsocks
Address
156.146.38.167:443
Transport / security
TCP / NONE
Last verified exit IP
156.146.38.167
Last verified handshake
480 ms
Last verified HTTPS first byte
811 ms
Download speed
2.173 Mbps
Source
Freedom V2Ray tested configs
First recorded check
2026-09-04 21:57:39 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)
10950 2026-09-04 21:57:39 UTC: 458 ms2026-09-08 09:32:16 UTC: 448 ms2026-09-09 17:04:10 UTC: 512 ms2026-09-10 18:39:47 UTC: 1,095 ms2026-09-11 17:47:51 UTC: 480 ms09-04 21:5709-11 17:47Check time (UTC)
HTTPS first byte (ms)
18160 2026-09-04 21:57:39 UTC: 717 ms2026-09-08 09:32:16 UTC: 711 ms2026-09-09 17:04:10 UTC: 827 ms2026-09-10 18:39:47 UTC: 1,816 ms2026-09-11 17:47:51 UTC: 811 ms09-04 21:5709-11 17:47Check 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 ok480 ms811 ms156.146.38.167
Tunnel ok1,095 ms1,816 ms156.146.38.167
Tunnel ok512 ms827 ms156.146.38.167
Tunnel ok448 ms711 ms156.146.38.167
Tunnel ok458 ms717 ms156.146.38.167

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.