Skip to main content
Tunnel verified at last checkLast result: 2026-09-11 08:08:36 UTC

Connection and verification

Protocol
Shadowsocks
Address
156.146.38.170:443
Transport / security
TCP / NONE
Last verified exit IP
156.146.38.170
Last verified handshake
670 ms
Last verified HTTPS first byte
937 ms
Download speed
1.711 Mbps
Source
0xRadikal verified downloadable configs
First recorded check
2026-09-04 13:50:45 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)
6700 2026-09-04 13:50:45 UTC: 524 ms2026-09-07 17:46:14 UTC: 541 ms2026-09-09 23:18:41 UTC: 423 ms2026-09-11 08:08:36 UTC: 670 ms09-04 13:5009-11 08:08Check time (UTC)
HTTPS first byte (ms)
10290 2026-09-04 13:50:45 UTC: 1,029 ms2026-09-07 17:46:14 UTC: 836 ms2026-09-09 23:18:41 UTC: 699 ms2026-09-11 08:08:36 UTC: 937 ms09-04 13:5009-11 08:08Check 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 ok670 ms937 ms156.146.38.170
Tunnel ok423 ms699 ms156.146.38.170
Tunnel ok541 ms836 ms156.146.38.170
Tunnel ok524 ms1,029 ms156.146.38.170

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.