Skip to main content
Tunnel verified at last checkLast result: 2026-09-11 10:24:28 UTC

Connection and verification

Protocol
Shadowsocks
Address
102.37.156.224:443
Transport / security
TCP / NONE
Last verified exit IP
102.37.156.224
Last verified handshake
596 ms
Last verified HTTPS first byte
1,585 ms
Download speed
1.485 Mbps
Source
Barry Shadowsocks
First recorded check
2026-09-03 21:32:21 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)
6490 2026-09-03 21:32:21 UTC: 562 ms2026-09-06 23:02:01 UTC: 649 ms2026-09-10 00:30:11 UTC: 574 ms2026-09-11 10:24:28 UTC: 596 ms09-03 21:3209-11 10:24Check time (UTC)
HTTPS first byte (ms)
15850 2026-09-03 21:32:21 UTC: 1,082 ms2026-09-06 23:02:01 UTC: 1,262 ms2026-09-10 00:30:11 UTC: 1,085 ms2026-09-11 10:24:28 UTC: 1,585 ms09-03 21:3209-11 10:24Check 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 ok596 ms1,585 ms102.37.156.224
Tunnel ok574 ms1,085 ms102.37.156.224
Tunnel ok649 ms1,262 ms102.37.156.224
Tunnel ok562 ms1,082 ms102.37.156.224

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.