Skip to main content
Tunnel verified at last checkLast result: 2026-09-12 11:50:05 UTC

Connection and verification

Protocol
Shadowsocks
Address
140.174.184.5:8388
Transport / security
TCP / NONE
Last verified exit IP
108.181.70.23
Last verified handshake
303 ms
Last verified HTTPS first byte
574 ms
Download speed
4.09 Mbps
Source
Barry Shadowsocks
First recorded check
2026-09-04 05:18:07 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)
14310 2026-09-04 05:18:07 UTC: 282 ms2026-09-07 09:30:42 UTC: 254 ms2026-09-10 02:07:25 UTC: 273 ms2026-09-11 12:49:57 UTC: 1,431 ms2026-09-12 11:50:05 UTC: 303 ms09-04 05:1809-12 11:50Check time (UTC)
HTTPS first byte (ms)
20520 2026-09-04 05:18:07 UTC: 541 ms2026-09-07 09:30:42 UTC: 670 ms2026-09-10 02:07:25 UTC: 743 ms2026-09-11 12:49:57 UTC: 2,052 ms2026-09-12 11:50:05 UTC: 574 ms09-04 05:1809-12 11:50Check 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 ok303 ms574 ms108.181.70.23
Tunnel ok1,431 ms2,052 ms108.181.70.23
Tunnel ok273 ms743 ms108.181.70.23
Tunnel ok254 ms670 ms108.181.70.23
Tunnel ok282 ms541 ms108.181.70.23

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.