Skip to main content
Tunnel verified at last checkLast result: 2026-09-12 00:43:39 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
545 ms
Last verified HTTPS first byte
1,049 ms
Download speed
3.156 Mbps
Source
0xRadikal verified downloadable configs
First recorded check
2026-09-04 13:15:51 UTC
Recorded tunnel checks
5
Successful tunnel checks
5
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)
5820 2026-09-04 13:15:51 UTC: 556 ms2026-09-07 17:28:57 UTC: 582 ms2026-09-09 19:31:49 UTC: 554 ms2026-09-11 01:43:30 UTC: 565 ms2026-09-12 00:43:39 UTC: 545 ms09-04 13:1509-12 00:43Check time (UTC)
HTTPS first byte (ms)
10940 2026-09-04 13:15:51 UTC: 1,083 ms2026-09-07 17:28:57 UTC: 1,094 ms2026-09-09 19:31:49 UTC: 1,066 ms2026-09-11 01:43:30 UTC: 1,077 ms2026-09-12 00:43:39 UTC: 1,049 ms09-04 13:1509-12 00:43Check time (UTC)

Check history

Latest 5 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 ok545 ms1,049 ms102.37.156.224
Tunnel ok565 ms1,077 ms102.37.156.224
Tunnel ok554 ms1,066 ms102.37.156.224
Tunnel ok582 ms1,094 ms102.37.156.224
Tunnel ok556 ms1,083 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.