Skip to main content
Tunnel verified at last checkLast result: 2026-10-23 20:15:23 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
235 ms
Last verified HTTPS first byte
434 ms
Download speed
8.681 Mbps
Source
0xRadikal verified downloadable configs
First recorded check
2026-09-04 14:02:40 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)
48450 09-04 14:0210-23 20:15Check time (UTC)
HTTPS first byte (ms)
52230 09-04 14:0210-23 20:15Check time (UTC)

Check history

Latest 43 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 ok235 ms434 ms193.29.139.152
Tunnel ok198 ms392 ms193.29.139.152
Tunnel ok544 ms733 ms193.29.139.152
Tunnel ok206 ms384 ms193.29.139.152
Tunnel ok275 ms482 ms193.29.139.152
Tunnel ok220 ms401 ms193.29.139.152
Tunnel ok198 ms367 ms193.29.139.152
Tunnel ok208 ms389 ms193.29.139.152
Tunnel ok181 ms351 ms193.29.139.152
Tunnel ok208 ms404 ms193.29.139.152
Policy blockedNot measuredNot measuredNot verified
Tunnel ok406 ms703 ms193.29.139.152
Tunnel ok222 ms411 ms193.29.139.152
Tunnel ok188 ms371 ms193.29.139.152
Tunnel ok192 ms373 ms193.29.139.152
Tunnel ok519 ms710 ms193.29.139.152
Tunnel ok215 ms404 ms193.29.139.152
Tunnel ok220 ms410 ms193.29.139.152
Tunnel ok190 ms369 ms193.29.139.152
Tunnel ok4,845 ms5,223 ms193.29.139.152
Tunnel ok213 ms396 ms193.29.139.152
Tunnel ok221 ms411 ms193.29.139.152
Tunnel ok247 ms461 ms193.29.139.152
Tunnel ok2,037 ms2,246 ms193.29.139.152
Tunnel ok208 ms403 ms193.29.139.152
Tunnel ok1,249 ms1,445 ms193.29.139.152
Tunnel ok473 ms657 ms193.29.139.152
Tunnel ok221 ms439 ms193.29.139.152
Tunnel ok210 ms391 ms193.29.139.152
Tunnel ok217 ms403 ms193.29.139.152
Tunnel ok327 ms570 ms193.29.139.152
Tunnel ok942 ms1,154 ms193.29.139.152
Tunnel ok1,070 ms1,271 ms193.29.139.152
Tunnel failedNot measuredNot measuredNot verified
Policy blockedNot measuredNot measuredNot verified
Policy blockedNot measuredNot measuredNot verified
Tunnel failedNot measuredNot measuredNot verified
Tunnel failedNot measuredNot measuredNot verified
Tunnel failedNot measuredNot measuredNot verified
Tunnel failedNot measuredNot measuredNot verified
Tunnel ok226 ms538 ms193.29.139.152
Tunnel ok342 ms559 ms193.29.139.152
Tunnel ok247 ms450 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.