Skip to main content
Inactive — did not pass verificationLast result: 2026-09-11 19:52:38 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.102.132.184:443
Transport / security
TCP / NONE
Last verified exit IP
149.102.132.184
Last verified handshake
242 ms
Last verified HTTPS first byte
448 ms
Download speed
6.988 Mbps
Source
Barry Shadowsocks
First recorded check
2026-09-05 06:33:43 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)
3520 2026-09-05 06:33:43 UTC: 242 ms2026-09-08 23:00:38 UTC: 352 ms2026-09-09 18:00:51 UTC: 235 ms2026-09-10 20:52:22 UTC: 231 ms2026-09-11 19:52:38 UTC: 242 ms09-05 06:3309-11 19:52Check time (UTC)
HTTPS first byte (ms)
5490 2026-09-05 06:33:43 UTC: 433 ms2026-09-08 23:00:38 UTC: 549 ms2026-09-09 18:00:51 UTC: 425 ms2026-09-10 20:52:22 UTC: 427 ms2026-09-11 19:52:38 UTC: 448 ms09-05 06:3309-11 19:52Check 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 ok242 ms448 ms149.102.132.184
Tunnel ok231 ms427 ms149.102.132.184
Tunnel ok235 ms425 ms149.102.132.184
Tunnel ok352 ms549 ms149.102.132.184
Tunnel ok242 ms433 ms149.102.132.184

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.