Skip to main content
Tunnel verified at last checkLast result: 2026-09-11 01:39: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
288 ms
Last verified HTTPS first byte
538 ms
Download speed
3.761 Mbps
Source
Au1rxx verified downloadable configs
First recorded check
2026-09-05 17:43:05 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)
4880 2026-09-05 17:43:05 UTC: 298 ms2026-09-09 07:26:15 UTC: 488 ms2026-09-09 15:23:43 UTC: 361 ms2026-09-11 01:39:05 UTC: 288 ms09-05 17:4309-11 01:39Check time (UTC)
HTTPS first byte (ms)
8460 2026-09-05 17:43:05 UTC: 846 ms2026-09-09 07:26:15 UTC: 771 ms2026-09-09 15:23:43 UTC: 630 ms2026-09-11 01:39:05 UTC: 538 ms09-05 17:4309-11 01:39Check 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 ok288 ms538 ms108.181.70.23
Tunnel ok361 ms630 ms108.181.70.23
Tunnel ok488 ms771 ms108.181.70.23
Tunnel ok298 ms846 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.