Skip to main content
Inactive — did not pass verificationLast result: 2026-10-24 23:33:20 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
82.38.31.187:8080
Transport / security
TCP / NONE
Last verified exit IP
193.29.139.152
Last verified handshake
191 ms
Last verified HTTPS first byte
363 ms
Download speed
7.442 Mbps
Source
Matin Shadowsocks
First recorded check
2026-09-04 01:30:54 UTC
Recorded tunnel checks
40
Successful tunnel checks
35
Recorded tunnel success rate
87.5%

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)
74660 09-04 01:3010-24 23:33Check time (UTC)
HTTPS first byte (ms)
76410 09-04 01:3010-24 23:33Check time (UTC)

Check history

Latest 40 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 ok191 ms363 ms193.29.139.152
Tunnel ok221 ms557 ms193.29.139.152
Tunnel ok217 ms408 ms193.29.139.152
Tunnel ok212 ms400 ms193.29.139.152
Tunnel ok3,897 ms4,089 ms193.29.139.152
Tunnel ok196 ms371 ms193.29.139.152
Tunnel ok231 ms445 ms193.29.139.152
Tunnel ok1,919 ms2,216 ms193.29.139.152
Tunnel ok237 ms466 ms193.29.139.152
Tunnel ok183 ms820 ms193.29.139.152
Tunnel ok859 ms1,112 ms193.29.139.152
Tunnel ok222 ms503 ms193.29.139.152
Tunnel ok185 ms369 ms193.29.139.152
Tunnel ok203 ms384 ms193.29.139.152
Tunnel ok242 ms438 ms193.29.139.152
Tunnel ok183 ms351 ms193.29.139.152
Tunnel ok198 ms374 ms193.29.139.152
Tunnel ok2,479 ms2,775 ms193.29.139.152
Tunnel ok4,120 ms4,928 ms193.29.139.152
Tunnel ok7,466 ms7,641 ms193.29.139.152
Tunnel ok216 ms557 ms193.29.139.152
Tunnel ok4,891 ms5,193 ms193.29.139.152
Tunnel ok221 ms417 ms193.29.139.152
Tunnel ok5,334 ms5,522 ms193.29.139.152
Tunnel ok246 ms432 ms193.29.139.152
Tunnel ok244 ms449 ms193.29.139.152
Tunnel ok217 ms410 ms193.29.139.152
Tunnel ok196 ms405 ms193.29.139.152
Tunnel ok383 ms826 ms193.29.139.152
Tunnel ok231 ms430 ms193.29.139.152
Tunnel ok319 ms543 ms193.29.139.152
Tunnel ok6,239 ms6,435 ms193.29.139.152
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 ok210 ms393 ms193.29.139.152
Tunnel ok199 ms526 ms193.29.139.152
Tunnel ok235 ms429 ms193.29.139.152

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.