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

Connection and verification

Protocol
Shadowsocks
Address
82.38.31.187:8080
Transport / security
TCP / NONE
Last verified exit IP
193.29.139.152
Last verified handshake
235 ms
Last verified HTTPS first byte
436 ms
Download speed
5.796 Mbps
Source
0xRadikal verified downloadable configs
First recorded check
2026-09-07 18:03:05 UTC
Recorded tunnel checks
40
Successful tunnel checks
33
Recorded tunnel success rate
82.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)
145380 09-07 18:0310-23 20:16Check time (UTC)
HTTPS first byte (ms)
147290 09-07 18:0310-23 20:16Check time (UTC)

Check history

Latest 42 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 ms436 ms193.29.139.152
Tunnel ok188 ms358 ms193.29.139.152
Tunnel ok565 ms903 ms193.29.139.152
Tunnel ok175 ms341 ms193.29.139.152
Tunnel ok220 ms412 ms193.29.139.152
Tunnel ok222 ms562 ms193.29.139.152
Tunnel ok316 ms509 ms193.29.139.152
Tunnel ok193 ms366 ms193.29.139.152
Tunnel ok211 ms394 ms193.29.139.152
Tunnel ok216 ms407 ms193.29.139.152
Policy blockedNot measuredNot measuredNot verified
Tunnel ok253 ms462 ms193.29.139.152
Tunnel ok188 ms366 ms193.29.139.152
Tunnel ok187 ms365 ms193.29.139.152
Tunnel ok197 ms378 ms193.29.139.152
Tunnel ok197 ms374 ms193.29.139.152
Tunnel ok416 ms594 ms193.29.139.152
Tunnel ok212 ms517 ms193.29.139.152
Tunnel ok194 ms379 ms193.29.139.152
Tunnel ok1,516 ms2,409 ms193.29.139.152
Tunnel ok181 ms426 ms193.29.139.152
Tunnel ok570 ms781 ms193.29.139.152
Tunnel ok193 ms375 ms193.29.139.152
Tunnel ok14,538 ms14,729 ms193.29.139.152
Tunnel ok2,327 ms2,677 ms193.29.139.152
Policy blockedNot measuredNot measuredNot verified
Tunnel ok435 ms844 ms193.29.139.152
Tunnel ok629 ms970 ms193.29.139.152
Tunnel ok194 ms374 ms193.29.139.152
Tunnel ok230 ms426 ms193.29.139.152
Tunnel ok219 ms406 ms193.29.139.152
Tunnel ok200 ms377 ms193.29.139.152
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 ok2,021 ms2,197 ms193.29.139.152
Tunnel ok5,329 ms5,730 ms193.29.139.152
Tunnel ok229 ms421 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.