Skip to main content
Inactive — did not pass verificationLast result: 2026-09-09 19:16:57 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.95.183:443
Transport / security
TCP / NONE
Last verified exit IP
149.22.95.183
Last verified handshake
471 ms
Last verified HTTPS first byte
768 ms
Download speed
3.066 Mbps
Source
Matin Shadowsocks
First recorded check
2026-09-05 03:35:13 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)
6320 2026-09-05 03:35:13 UTC: 632 ms2026-09-08 16:49:37 UTC: 495 ms2026-09-09 19:16:57 UTC: 471 ms09-05 03:3509-09 19:16Check time (UTC)
HTTPS first byte (ms)
10360 2026-09-05 03:35:13 UTC: 1,036 ms2026-09-08 16:49:37 UTC: 793 ms2026-09-09 19:16:57 UTC: 768 ms09-05 03:3509-09 19:16Check 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 ok471 ms768 ms149.22.95.183
Tunnel ok495 ms793 ms149.22.95.183
Tunnel ok632 ms1,036 ms149.22.95.183

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.