Skip to main content
Inactive — did not pass verificationLast result: 2026-09-10 16:05:37 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.11:8080
Transport / security
TCP / NONE
Last verified exit IP
193.29.139.188
Last verified handshake
344 ms
Last verified HTTPS first byte
528 ms
Download speed
3.767 Mbps
Source
rjsxrd secure tunnel-tested configs
First recorded check
2026-09-08 12:16:07 UTC
Recorded tunnel checks
2
Successful tunnel checks
2
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)
3440 2026-09-09 15:32:54 UTC: 203 ms2026-09-10 16:05:37 UTC: 344 ms09-09 15:3209-10 16:05Check time (UTC)
HTTPS first byte (ms)
5280 2026-09-09 15:32:54 UTC: 381 ms2026-09-10 16:05:37 UTC: 528 ms09-09 15:3209-10 16:05Check 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 ok344 ms528 ms193.29.139.188
Tunnel ok203 ms381 ms193.29.139.188
Policy blockedNot 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.