Skip to main content
Tunnel verified at last checkLast result: 2026-10-23 07:48:02 UTC

Connection and verification

Protocol
Shadowsocks
Address
82.38.31.175:8080
Transport / security
TCP / NONE
Last verified exit IP
193.29.139.135
Last verified handshake
225 ms
Last verified HTTPS first byte
453 ms
Download speed
3.178 Mbps
Source
0xRadikal verified downloadable configs
First recorded check
2026-09-07 18:21:12 UTC
Recorded tunnel checks
41
Successful tunnel checks
29
Recorded tunnel success rate
70.7%

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)
5470 09-11 10:4710-23 07:48Check time (UTC)
HTTPS first byte (ms)
7300 09-11 10:4710-23 07:48Check 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 ok225 ms453 ms193.29.139.135
Tunnel ok220 ms432 ms193.29.139.135
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 failedNot measuredNot measuredNot verified
Policy blockedNot measuredNot measuredNot verified
Tunnel ok300 ms496 ms193.29.139.135
Tunnel failedNot measuredNot measuredNot verified
Tunnel ok206 ms388 ms193.29.139.135
Tunnel ok183 ms354 ms193.29.139.135
Tunnel ok237 ms439 ms193.29.139.135
Tunnel ok205 ms385 ms193.29.139.135
Tunnel failedNot measuredNot measuredNot verified
Tunnel ok193 ms375 ms193.29.139.135
Tunnel ok192 ms375 ms193.29.139.135
Tunnel ok206 ms390 ms193.29.139.135
Tunnel ok188 ms363 ms193.29.139.135
Tunnel ok189 ms372 ms193.29.139.135
Tunnel ok190 ms378 ms193.29.139.135
Tunnel ok174 ms343 ms193.29.139.135
Tunnel ok180 ms349 ms193.29.139.135
Tunnel ok198 ms376 ms193.29.139.135
Tunnel ok192 ms366 ms193.29.139.135
Tunnel ok272 ms473 ms193.29.139.135
Tunnel ok191 ms364 ms193.29.139.135
Tunnel ok197 ms371 ms193.29.139.135
Tunnel ok199 ms380 ms193.29.139.135
Tunnel ok242 ms459 ms193.29.139.135
Tunnel ok200 ms378 ms193.29.139.135
Tunnel ok206 ms390 ms193.29.139.135
Tunnel ok547 ms730 ms193.29.139.135
Tunnel ok203 ms400 ms193.29.139.135
Tunnel ok224 ms415 ms193.29.139.135
Tunnel ok285 ms480 ms193.29.139.135
Tunnel ok200 ms388 ms193.29.139.135
Tunnel failedNot measuredNot measuredNot verified
Tunnel failedNot 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.