Skip to main content
Inactive — did not pass verificationLast result: 2026-10-21 22:59:55 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.48:8080
Transport / security
TCP / NONE
Last verified exit IP
193.29.139.219
Last verified handshake
346 ms
Last verified HTTPS first byte
548 ms
Download speed
8.918 Mbps
Source
Matin Shadowsocks
First recorded check
2026-09-07 16:12:41 UTC
Recorded tunnel checks
38
Successful tunnel checks
32
Recorded tunnel success rate
84.2%

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)
4770 09-11 14:3310-21 22:59Check time (UTC)
HTTPS first byte (ms)
6880 09-11 14:3310-21 22:59Check time (UTC)

Check history

Latest 38 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 ok346 ms548 ms193.29.139.219
Tunnel ok187 ms362 ms193.29.139.219
Tunnel ok224 ms417 ms193.29.139.219
Tunnel ok190 ms363 ms193.29.139.219
Tunnel ok224 ms425 ms193.29.139.219
Tunnel failedNot measuredNot measuredNot verified
Tunnel failedNot measuredNot measuredNot verified
Tunnel failedNot measuredNot measuredNot verified
Tunnel failedNot measuredNot measuredNot verified
Tunnel ok244 ms459 ms193.29.139.219
Tunnel ok189 ms366 ms193.29.139.219
Tunnel ok188 ms370 ms193.29.139.219
Tunnel ok178 ms607 ms193.29.139.219
Tunnel ok220 ms412 ms193.29.139.219
Tunnel ok181 ms357 ms193.29.139.219
Tunnel ok477 ms688 ms193.29.139.219
Tunnel ok219 ms405 ms193.29.139.219
Tunnel ok186 ms365 ms193.29.139.219
Tunnel ok216 ms436 ms193.29.139.219
Tunnel ok205 ms383 ms193.29.139.219
Tunnel ok203 ms394 ms193.29.139.219
Tunnel ok187 ms363 ms193.29.139.219
Tunnel ok228 ms418 ms193.29.139.219
Tunnel ok191 ms370 ms193.29.139.219
Tunnel ok221 ms413 ms193.29.139.219
Tunnel ok200 ms380 ms193.29.139.219
Tunnel ok190 ms362 ms193.29.139.219
Tunnel ok254 ms460 ms193.29.139.219
Tunnel ok197 ms394 ms193.29.139.219
Tunnel ok199 ms381 ms193.29.139.219
Tunnel ok276 ms499 ms193.29.139.219
Tunnel ok197 ms375 ms193.29.139.219
Tunnel ok266 ms499 ms193.29.139.219
Tunnel ok261 ms457 ms193.29.139.219
Tunnel ok235 ms443 ms193.29.139.219
Tunnel ok236 ms432 ms193.29.139.219
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.