Skip to main content
Tunnel verified at last checkLast result: 2026-09-11 19:47:45 UTC

Connection and verification

Protocol
Shadowsocks
Address
108.181.121.226:8388
Transport / security
TCP / NONE
Last verified exit IP
108.181.70.65
Last verified handshake
318 ms
Last verified HTTPS first byte
593 ms
Download speed
5.102 Mbps
Source
Barry Shadowsocks
First recorded check
2026-09-04 16:29: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)
3670 2026-09-04 16:29:51 UTC: 367 ms2026-09-08 01:42:14 UTC: 291 ms2026-09-09 17:55:27 UTC: 304 ms2026-09-10 20:47:33 UTC: 284 ms2026-09-11 19:47:45 UTC: 318 ms09-04 16:2909-11 19:47Check time (UTC)
HTTPS first byte (ms)
7180 2026-09-04 16:29:51 UTC: 718 ms2026-09-08 01:42:14 UTC: 547 ms2026-09-09 17:55:27 UTC: 571 ms2026-09-10 20:47:33 UTC: 688 ms2026-09-11 19:47:45 UTC: 593 ms09-04 16:2909-11 19:47Check 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 ok318 ms593 ms108.181.70.65
Tunnel ok284 ms688 ms108.181.70.65
Tunnel ok304 ms571 ms108.181.70.65
Tunnel ok291 ms547 ms108.181.70.65
Tunnel ok367 ms718 ms108.181.70.65

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.