Skip to main content
Tunnel verified at last checkLast result: 2026-09-11 04:33:49 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
305 ms
Last verified HTTPS first byte
569 ms
Download speed
5.775 Mbps
Source
Firmfox Proxify mixed configs
First recorded check
2026-09-05 21:47:29 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)
4430 2026-09-05 21:47:29 UTC: 443 ms2026-09-09 08:13:45 UTC: 289 ms2026-09-09 08:15:03 UTC: 386 ms2026-09-09 20:45:43 UTC: 321 ms2026-09-11 04:33:49 UTC: 305 ms09-05 21:4709-11 04:33Check time (UTC)
HTTPS first byte (ms)
12160 2026-09-05 21:47:29 UTC: 751 ms2026-09-09 08:13:45 UTC: 544 ms2026-09-09 08:15:03 UTC: 1,216 ms2026-09-09 20:45:43 UTC: 610 ms2026-09-11 04:33:49 UTC: 569 ms09-05 21:4709-11 04:33Check 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 ok305 ms569 ms108.181.70.23
Tunnel ok321 ms610 ms108.181.70.23
Tunnel ok386 ms1,216 ms108.181.70.23
Tunnel ok289 ms544 ms108.181.70.23
Tunnel ok443 ms751 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.