Skip to main content
Inactive — did not pass verificationLast result: 2026-09-09 23:09:30 UTC

This endpoint has no current downloadable verification, or a newer check did not succeed. Previous measurements below are historical. Choose another checked Shadowsocks server.

Connection and verification

Protocol
Shadowsocks
Address
149.22.87.241:443
Transport / security
TCP / NONE
Last verified exit IP
149.22.87.241
Last verified handshake
750 ms
Last verified HTTPS first byte
1,263 ms
Download speed
1.81 Mbps
Source
Firmfox Proxify mixed configs
First recorded check
2026-09-05 18:07:08 UTC
Recorded tunnel checks
3
Successful tunnel checks
3
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)
7500 2026-09-05 18:07:08 UTC: 687 ms2026-09-09 05:12:52 UTC: 671 ms2026-09-09 23:09:30 UTC: 750 ms09-05 18:0709-09 23:09Check time (UTC)
HTTPS first byte (ms)
12630 2026-09-05 18:07:08 UTC: 1,203 ms2026-09-09 05:12:52 UTC: 1,182 ms2026-09-09 23:09:30 UTC: 1,263 ms09-05 18:0709-09 23:09Check time (UTC)

Check history

Latest 3 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 ok750 ms1,263 ms149.22.87.241
Tunnel ok671 ms1,182 ms149.22.87.241
Tunnel ok687 ms1,203 ms149.22.87.241

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.