Skip to main content
Tunnel verified at last checkLast result: 2026-09-10 02:45:03 UTC

Connection and verification

Protocol
Shadowsocks
Address
82.38.31.186:8080
Transport / security
TCP / NONE
Last verified exit IP
193.29.139.152
Last verified handshake
211 ms
Last verified HTTPS first byte
396 ms
Download speed
7.081 Mbps
Source
Barry Shadowsocks
First recorded check
2026-09-04 08:32:32 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)
3350 2026-09-04 08:32:32 UTC: 210 ms2026-09-07 12:55:36 UTC: 335 ms2026-09-10 02:45:03 UTC: 211 ms09-04 08:3209-10 02:45Check time (UTC)
HTTPS first byte (ms)
5870 2026-09-04 08:32:32 UTC: 490 ms2026-09-07 12:55:36 UTC: 587 ms2026-09-10 02:45:03 UTC: 396 ms09-04 08:3209-10 02:45Check 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 ok211 ms396 ms193.29.139.152
Tunnel ok335 ms587 ms193.29.139.152
Tunnel ok210 ms490 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.