Skip to main content
Tunnel verified at last checkLast result: 2026-10-23 21:34:13 UTC

Connection and verification

Protocol
Shadowsocks
Address
82.110.60.9:19999
Transport / security
TCP / NONE
Last verified exit IP
51.241.209.4
Last verified handshake
244 ms
Last verified HTTPS first byte
465 ms
Download speed
7.998 Mbps
Source
Barry Shadowsocks
First recorded check
2026-09-12 16:22:58 UTC
Recorded tunnel checks
13
Successful tunnel checks
13
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

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

Tunnel handshake (ms)
3010 09-12 16:2210-23 21:34Check time (UTC)
HTTPS first byte (ms)
5200 09-12 16:2210-23 21:34Check time (UTC)

Check history

Latest 13 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 ok244 ms465 ms51.241.209.4
Tunnel ok204 ms407 ms51.241.209.4
Tunnel ok221 ms420 ms51.241.209.4
Tunnel ok216 ms419 ms51.241.209.4
Tunnel ok224 ms425 ms51.241.209.4
Tunnel ok234 ms454 ms51.241.209.4
Tunnel ok242 ms456 ms51.241.209.4
Tunnel ok247 ms464 ms51.241.209.4
Tunnel ok254 ms467 ms51.241.209.4
Tunnel ok222 ms429 ms51.241.209.4
Tunnel ok234 ms441 ms51.241.209.4
Tunnel ok301 ms520 ms51.241.209.4
Tunnel ok270 ms495 ms51.241.209.4

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.