Skip to main content
Inactive — did not pass verificationLast result: 2026-09-10 07:38:56 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.168:443
Transport / security
TCP / NONE
Last verified exit IP
156.146.38.168
Last verified handshake
1,522 ms
Last verified HTTPS first byte
1,994 ms
Download speed
Not measured
Source
Au1rxx verified downloadable configs
First recorded check
2026-09-04 05:54:35 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)
15220 2026-09-04 05:54:35 UTC: 495 ms2026-09-07 11:16:08 UTC: 444 ms2026-09-07 11:31:15 UTC: 584 ms2026-09-10 07:38:56 UTC: 1,522 ms09-04 05:5409-10 07:38Check time (UTC)
HTTPS first byte (ms)
19940 2026-09-04 05:54:35 UTC: 772 ms2026-09-07 11:16:08 UTC: 707 ms2026-09-07 11:31:15 UTC: 849 ms2026-09-10 07:38:56 UTC: 1,994 ms09-04 05:5409-10 07:38Check 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 ok1,522 ms1,994 ms156.146.38.168
Tunnel ok584 ms849 ms156.146.38.168
Tunnel ok444 ms707 ms156.146.38.168
Tunnel ok495 ms772 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.