Skip to main content
Inactive — did not pass verificationLast result: 2026-10-22 15:19:52 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
84.247.155.196:80
Transport / security
TCP / NONE
Last verified exit IP
84.247.155.196
Last verified handshake
643 ms
Last verified HTTPS first byte
1,172 ms
Download speed
2.511 Mbps
Source
Matin Shadowsocks
First recorded check
2026-09-11 14:09:23 UTC
Recorded tunnel checks
35
Successful tunnel checks
21
Recorded tunnel success rate
60.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

Hover or focus a point for check details. Click or tap to keep them open.

Tunnel handshake (ms)
10300 09-16 19:4010-20 01:35Check time (UTC)
HTTPS first byte (ms)
17650 09-16 19:4010-20 01:35Check time (UTC)

Check history

Latest 35 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 failedNot measuredNot measuredNot verified
Tunnel ok643 ms1,172 ms84.247.155.196
Tunnel ok669 ms1,257 ms84.247.155.196
Tunnel ok633 ms1,120 ms84.247.155.196
Tunnel failedNot measuredNot measuredNot verified
Tunnel failedNot measuredNot measuredNot verified
Tunnel failedNot measuredNot measuredNot verified
Tunnel failedNot measuredNot measuredNot verified
Tunnel failedNot measuredNot measuredNot verified
Tunnel ok700 ms1,518 ms84.247.155.196
TimeoutNot measuredNot measuredNot verified
Tunnel ok814 ms1,421 ms84.247.155.196
Tunnel ok679 ms1,258 ms84.247.155.196
Tunnel ok629 ms1,153 ms84.247.155.196
Tunnel ok771 ms1,337 ms84.247.155.196
Tunnel ok671 ms1,198 ms84.247.155.196
Tunnel ok639 ms1,129 ms84.247.155.196
TimeoutNot measuredNot measuredNot verified
Tunnel ok898 ms1,443 ms84.247.155.196
Tunnel ok702 ms1,272 ms84.247.155.196
Tunnel ok734 ms1,217 ms84.247.155.196
Tunnel ok1,030 ms1,765 ms84.247.155.196
Tunnel ok652 ms1,236 ms84.247.155.196
Tunnel ok629 ms1,178 ms84.247.155.196
Tunnel ok697 ms1,204 ms84.247.155.196
Tunnel ok665 ms1,170 ms84.247.155.196
Tunnel ok1,015 ms1,699 ms84.247.155.196
Tunnel ok700 ms1,197 ms84.247.155.196
Tunnel failedNot measuredNot measuredNot verified
Tunnel ok650 ms1,141 ms84.247.155.196
Tunnel failedNot measuredNot measuredNot verified
Tunnel failedNot measuredNot measuredNot verified
Tunnel failedNot measuredNot measuredNot verified
Tunnel failedNot measuredNot measuredNot verified
Tunnel failedNot measuredNot measuredNot verified

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.

This saved detail page remains available with its check history. Search indexing requires current successful full-tunnel verification, real measurements and an available configuration.