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

Connection and verification

Protocol
Shadowsocks
Address
141.164.45.187:6697
Transport / security
TCP / NONE
Last verified exit IP
141.164.45.187
Last verified handshake
11,358 ms
Last verified HTTPS first byte
12,057 ms
Download speed
2.276 Mbps
Source
Firmfox Proxify mixed configs
First recorded check
2026-09-21 23:08:01 UTC
Recorded tunnel checks
14
Successful tunnel checks
10
Recorded tunnel success rate
71.4%

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)
139950 09-21 23:0810-23 21:21Check time (UTC)
HTTPS first byte (ms)
150530 09-21 23:0810-23 21:21Check time (UTC)

Check history

Latest 14 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 ok11,358 ms12,057 ms141.164.45.187
TimeoutNot measuredNot measuredNot verified
Tunnel ok983 ms2,785 ms141.164.45.187
Tunnel ok2,279 ms3,335 ms141.164.45.187
TimeoutNot measuredNot measuredNot verified
Tunnel ok1,387 ms2,519 ms141.164.45.187
Tunnel ok721 ms1,618 ms141.164.45.187
Tunnel ok2,808 ms5,230 ms141.164.45.187
Tunnel ok13,995 ms15,053 ms141.164.45.187
Tunnel ok882 ms1,609 ms141.164.45.187
Tunnel ok1,152 ms1,877 ms141.164.45.187
TimeoutNot measuredNot measuredNot verified
TimeoutNot measuredNot measuredNot verified
Tunnel ok1,178 ms2,213 ms141.164.45.187

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.