Skip to main content
Tunnel verified at last checkLast result: 2026-09-11 17:54:12 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
599 ms
Last verified HTTPS first byte
1,126 ms
Download speed
3.026 Mbps
Source
PSG mixed Xray configs
First recorded check
2026-09-06 19:53:59 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)
7010 2026-09-06 19:53:59 UTC: 579 ms2026-09-09 17:16:09 UTC: 701 ms2026-09-10 18:53:58 UTC: 623 ms2026-09-11 17:54:12 UTC: 599 ms09-06 19:5309-11 17:54Check time (UTC)
HTTPS first byte (ms)
12260 2026-09-06 19:53:59 UTC: 1,099 ms2026-09-09 17:16:09 UTC: 1,226 ms2026-09-10 18:53:58 UTC: 1,156 ms2026-09-11 17:54:12 UTC: 1,126 ms09-06 19:5309-11 17:54Check 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 ok599 ms1,126 ms102.37.156.224
Tunnel ok623 ms1,156 ms102.37.156.224
Tunnel ok701 ms1,226 ms102.37.156.224
Tunnel ok579 ms1,099 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.