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

Connection and verification

Protocol
Shadowsocks
Address
51.255.13.232:8388
Transport / security
TCP / NONE
Last verified exit IP
91.134.92.132
Last verified handshake
348 ms
Last verified HTTPS first byte
653 ms
Download speed
4.437 Mbps
Source
rjsxrd secure tunnel-tested configs
First recorded check
2026-09-08 11:32:57 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)
4020 2026-09-09 14:49:14 UTC: 402 ms2026-09-10 15:09:41 UTC: 290 ms2026-09-11 16:24:06 UTC: 348 ms09-09 14:4909-11 16:24Check time (UTC)
HTTPS first byte (ms)
12880 2026-09-09 14:49:14 UTC: 1,288 ms2026-09-10 15:09:41 UTC: 546 ms2026-09-11 16:24:06 UTC: 653 ms09-09 14:4909-11 16: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 ok348 ms653 ms91.134.92.132
Tunnel ok290 ms546 ms91.134.92.132
Tunnel ok402 ms1,288 ms91.134.92.132
Policy blockedNot measuredNot measuredNot verified

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.