Skip to main content
Tunnel verified at last checkLast result: 2026-09-10 21:04:26 UTC

Connection and verification

Protocol
Shadowsocks
Address
149.22.87.240:443
Transport / security
TCP / NONE
Last verified exit IP
149.22.87.240
Last verified handshake
734 ms
Last verified HTTPS first byte
1,249 ms
Download speed
1.332 Mbps
Source
Freedom V2Ray tested configs
First recorded check
2026-09-05 05:37:04 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)
7580 2026-09-05 05:37:04 UTC: 758 ms2026-09-08 20:02:56 UTC: 683 ms2026-09-09 18:07:36 UTC: 676 ms2026-09-10 21:04:26 UTC: 734 ms09-05 05:3709-10 21:04Check time (UTC)
HTTPS first byte (ms)
12740 2026-09-05 05:37:04 UTC: 1,274 ms2026-09-08 20:02:56 UTC: 1,193 ms2026-09-09 18:07:36 UTC: 1,184 ms2026-09-10 21:04:26 UTC: 1,249 ms09-05 05:3709-10 21:04Check 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 ok734 ms1,249 ms149.22.87.240
Tunnel ok676 ms1,184 ms149.22.87.240
Tunnel ok683 ms1,193 ms149.22.87.240
Tunnel ok758 ms1,274 ms149.22.87.240

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.