Skip to main content
Inactive — did not pass verificationLast result: 2026-09-11 10:57:56 UTC

This endpoint has no current downloadable verification, or a newer check did not succeed. Previous measurements below are historical. Choose another checked Shadowsocks server.

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
236 ms
Last verified HTTPS first byte
451 ms
Download speed
5.857 Mbps
Source
Firmfox Proxify mixed configs
First recorded check
2026-09-03 20:21:20 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)
2360 2026-09-03 20:21:20 UTC: 228 ms2026-09-06 21:34:02 UTC: 233 ms2026-09-10 00:55:31 UTC: 215 ms2026-09-11 10:57:56 UTC: 236 ms09-03 20:2109-11 10:57Check time (UTC)
HTTPS first byte (ms)
10840 2026-09-03 20:21:20 UTC: 1,084 ms2026-09-06 21:34:02 UTC: 454 ms2026-09-10 00:55:31 UTC: 425 ms2026-09-11 10:57:56 UTC: 451 ms09-03 20:2109-11 10:57Check 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 ok236 ms451 ms91.134.92.132
Tunnel ok215 ms425 ms91.134.92.132
Tunnel ok233 ms454 ms91.134.92.132
Tunnel ok228 ms1,084 ms91.134.92.132

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.