Skip to main content
Tunnel verified at last checkLast result: 2026-09-12 01:51:08 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
478 ms
Last verified HTTPS first byte
816 ms
Download speed
3.056 Mbps
Source
Firmfox Proxify mixed configs
First recorded check
2026-09-05 16:13:58 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)
5730 2026-09-05 16:13:58 UTC: 456 ms2026-09-09 13:54:14 UTC: 573 ms2026-09-09 20:00:08 UTC: 490 ms2026-09-11 02:50:59 UTC: 477 ms2026-09-12 01:51:08 UTC: 478 ms09-05 16:1309-12 01:51Check time (UTC)
HTTPS first byte (ms)
12240 2026-09-05 16:13:58 UTC: 724 ms2026-09-09 13:54:14 UTC: 1,224 ms2026-09-09 20:00:08 UTC: 818 ms2026-09-11 02:50:59 UTC: 763 ms2026-09-12 01:51:08 UTC: 816 ms09-05 16:1309-12 01:51Check 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 ok478 ms816 ms156.146.38.167
Tunnel ok477 ms763 ms156.146.38.167
Tunnel ok490 ms818 ms156.146.38.167
Tunnel ok573 ms1,224 ms156.146.38.167
Tunnel ok456 ms724 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.