Skip to main content
Tunnel verified at last checkLast result: 2026-10-09 07:23:51 UTC

Connection and verification

Protocol
Shadowsocks
Address
51.77.225.200:8388
Transport / security
TCP / NONE
Last verified exit IP
57.129.140.88
Last verified handshake
245 ms
Last verified HTTPS first byte
475 ms
Download speed
6.487 Mbps
Source
Au1rxx verified downloadable configs
First recorded check
2026-09-07 21:05:08 UTC
Recorded tunnel checks
15
Successful tunnel checks
12
Recorded tunnel success rate
80.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

Hover or focus a point for check details. Click or tap to keep them open.

Tunnel handshake (ms)
3810 09-28 13:0710-09 07:23Check time (UTC)
HTTPS first byte (ms)
7470 09-28 13:0710-09 07:23Check time (UTC)

Check history

Latest 16 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 ok245 ms475 ms57.129.140.88
Tunnel ok240 ms466 ms57.129.140.88
Tunnel ok244 ms480 ms57.129.140.88
Tunnel ok246 ms484 ms57.129.140.88
Preflight okNot measuredNot measuredNot verified
Tunnel ok247 ms574 ms57.129.140.88
Tunnel ok381 ms747 ms57.129.140.88
Tunnel ok300 ms583 ms57.129.140.88
Tunnel ok275 ms537 ms57.129.140.88
Tunnel ok261 ms512 ms57.129.140.88
Tunnel ok314 ms559 ms57.129.140.88
Tunnel ok257 ms504 ms57.129.140.88
Tunnel ok239 ms480 ms57.129.140.88
Tunnel failedNot measuredNot measuredNot verified
Tunnel failedNot measuredNot measuredNot verified
Tunnel failedNot 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.

This saved detail page remains available with its check history. Search indexing requires current successful full-tunnel verification, real measurements and an available configuration.