Skip to main content
Tunnel verified at last checkLast result: 2026-10-23 20:24:08 UTC

Connection and verification

Protocol
Shadowsocks
Address
82.38.31.193:8080
Transport / security
TCP / NONE
Last verified exit IP
193.29.139.198
Last verified handshake
686 ms
Last verified HTTPS first byte
949 ms
Download speed
8.184 Mbps
Source
0xRadikal verified downloadable configs
First recorded check
2026-09-04 14:37:04 UTC
Recorded tunnel checks
42
Successful tunnel checks
30
Recorded tunnel success rate
71.4%

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)
12080 09-04 14:3710-23 20:24Check time (UTC)
HTTPS first byte (ms)
13870 09-04 14:3710-23 20:24Check 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 ok686 ms949 ms193.29.139.198
Tunnel failedNot measuredNot measuredNot verified
Tunnel failedNot measuredNot measuredNot verified
Tunnel failedNot measuredNot measuredNot verified
Tunnel failedNot measuredNot measuredNot verified
Tunnel ok206 ms388 ms193.29.139.198
Tunnel ok213 ms385 ms193.29.139.198
Tunnel ok180 ms495 ms193.29.139.198
Tunnel ok178 ms346 ms193.29.139.198
Tunnel ok202 ms539 ms193.29.139.198
Tunnel ok182 ms348 ms193.29.139.198
Tunnel ok217 ms399 ms193.29.139.198
Tunnel ok198 ms374 ms193.29.139.198
Tunnel ok216 ms411 ms193.29.139.198
Tunnel ok185 ms359 ms193.29.139.198
Tunnel ok202 ms384 ms193.29.139.198
Tunnel ok184 ms358 ms193.29.139.198
Policy blockedNot measuredNot measuredNot verified
Tunnel ok292 ms480 ms193.29.139.198
Tunnel ok183 ms360 ms193.29.139.198
Tunnel ok197 ms374 ms193.29.139.198
Tunnel ok1,208 ms1,387 ms193.29.139.198
Tunnel ok403 ms594 ms193.29.139.198
Tunnel ok186 ms367 ms193.29.139.198
Tunnel ok957 ms1,185 ms193.29.139.198
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 failedNot measuredNot measuredNot verified
Tunnel failedNot measuredNot measuredNot verified
Tunnel ok246 ms449 ms193.29.139.198
Tunnel failedNot measuredNot measuredNot verified
Tunnel ok233 ms431 ms193.29.139.198
Tunnel ok202 ms384 ms193.29.139.198
Tunnel ok266 ms485 ms193.29.139.198
Tunnel ok355 ms564 ms193.29.139.198
Tunnel ok250 ms470 ms193.29.139.198
Tunnel ok256 ms470 ms193.29.139.198
Tunnel ok205 ms381 ms193.29.139.198
Tunnel ok240 ms597 ms193.29.139.198
Tunnel ok219 ms412 ms193.29.139.198

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.