Skip to main content
Tunnel verified at last checkLast result: 2026-09-11 20:17:16 UTC

Connection and verification

Protocol
Shadowsocks
Address
141.98.101.181:443
Transport / security
TCP / NONE
Last verified exit IP
141.98.101.181
Last verified handshake
285 ms
Last verified HTTPS first byte
507 ms
Download speed
4.887 Mbps
Source
Firmfox Proxify mixed configs
First recorded check
2026-09-06 03:11: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)
6540 2026-09-06 03:11:51 UTC: 391 ms2026-09-09 12:48:22 UTC: 285 ms2026-09-09 18:13:59 UTC: 654 ms2026-09-10 21:17:09 UTC: 285 ms2026-09-11 20:17:16 UTC: 349 ms09-06 03:1109-11 20:17Check time (UTC)
HTTPS first byte (ms)
10560 2026-09-06 03:11:51 UTC: 606 ms2026-09-09 12:48:22 UTC: 499 ms2026-09-09 18:13:59 UTC: 1,056 ms2026-09-10 21:17:09 UTC: 507 ms2026-09-11 20:17:16 UTC: 578 ms09-06 03:1109-11 20:17Check 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 ok349 ms578 ms141.98.101.181
Tunnel ok285 ms507 ms141.98.101.181
Tunnel ok654 ms1,056 ms141.98.101.181
Tunnel ok285 ms499 ms141.98.101.181
Tunnel ok391 ms606 ms141.98.101.181

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.