Skip to main content
Tunnel verified at last checkLast result: 2026-09-10 00:29:31 UTC

Connection and verification

Protocol
Shadowsocks
Address
102.133.165.160:16233
Transport / security
TCP / NONE
Last verified exit IP
4.222.217.240
Last verified handshake
623 ms
Last verified HTTPS first byte
1,160 ms
Download speed
1.816 Mbps
Source
Barry Shadowsocks
First recorded check
2026-09-03 21:29:44 UTC
Recorded tunnel checks
3
Successful tunnel checks
3
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)
6230 2026-09-03 21:29:44 UTC: 582 ms2026-09-06 22:59:44 UTC: 554 ms2026-09-10 00:29:31 UTC: 623 ms09-03 21:2909-10 00:29Check time (UTC)
HTTPS first byte (ms)
15470 2026-09-03 21:29:44 UTC: 1,106 ms2026-09-06 22:59:44 UTC: 1,547 ms2026-09-10 00:29:31 UTC: 1,160 ms09-03 21:2909-10 00:29Check time (UTC)

Check history

Latest 3 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 ok623 ms1,160 ms4.222.217.240
Tunnel ok554 ms1,547 ms4.222.217.240
Tunnel ok582 ms1,106 ms4.222.217.240

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.