Shadowsocks server 82.38.31.47:8080
TCP / NONE · 0xRadikal verified downloadable configs
Tunnel verified at last checkLast result: 2026-10-09 03:50:05 UTC
Connection and verification
- Protocol
- Shadowsocks
- Address
- 82.38.31.47:8080
- Transport / security
- TCP / NONE
- Last verified exit IP
- 193.29.139.219
- Last verified handshake
- 547 ms
- Last verified HTTPS first byte
- 731 ms
- Download speed
- 4.129 Mbps
- Source
- 0xRadikal verified downloadable configs
- First recorded check
- 2026-09-07 18:31:47 UTC
- Recorded tunnel checks
- 30
- Successful tunnel checks
- 27
- Recorded tunnel success rate
- 90.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
Hover or focus a point for check details. Click or tap to keep them open.
Check history
Latest 30 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.
| Checked (UTC) | Result | Handshake | HTTPS first byte | Exit IP |
|---|---|---|---|---|
| Tunnel ok | 547 ms | 731 ms | 193.29.139.219 | |
| Tunnel ok | 199 ms | 377 ms | 193.29.139.219 | |
| Tunnel failed | Not measured | Not measured | Not verified | |
| Tunnel ok | 179 ms | 505 ms | 193.29.139.219 | |
| Tunnel ok | 184 ms | 355 ms | 193.29.139.219 | |
| Tunnel ok | 194 ms | 369 ms | 193.29.139.219 | |
| Tunnel ok | 216 ms | 398 ms | 193.29.139.219 | |
| Tunnel ok | 248 ms | 437 ms | 193.29.139.219 | |
| Tunnel ok | 245 ms | 421 ms | 193.29.139.219 | |
| Tunnel ok | 211 ms | 388 ms | 193.29.139.219 | |
| Tunnel ok | 225 ms | 406 ms | 193.29.139.219 | |
| Tunnel ok | 223 ms | 413 ms | 193.29.139.219 | |
| Tunnel ok | 173 ms | 336 ms | 193.29.139.219 | |
| Tunnel ok | 171 ms | 335 ms | 193.29.139.219 | |
| Tunnel ok | 196 ms | 370 ms | 193.29.139.219 | |
| Tunnel ok | 203 ms | 385 ms | 193.29.139.219 | |
| Tunnel ok | 195 ms | 373 ms | 193.29.139.219 | |
| Tunnel ok | 230 ms | 420 ms | 193.29.139.219 | |
| Tunnel ok | 230 ms | 415 ms | 193.29.139.219 | |
| Tunnel ok | 196 ms | 378 ms | 193.29.139.219 | |
| Tunnel ok | 2,553 ms | 3,171 ms | 193.29.139.219 | |
| Tunnel ok | 200 ms | 382 ms | 193.29.139.219 | |
| Tunnel ok | 207 ms | 391 ms | 193.29.139.219 | |
| Tunnel ok | 228 ms | 685 ms | 193.29.139.219 | |
| Tunnel ok | 443 ms | 648 ms | 193.29.139.219 | |
| Tunnel ok | 296 ms | 517 ms | 193.29.139.219 | |
| Tunnel ok | 236 ms | 444 ms | 193.29.139.219 | |
| Tunnel ok | 232 ms | 427 ms | 193.29.139.219 | |
| Tunnel failed | Not measured | Not measured | Not verified | |
| Tunnel failed | Not measured | Not measured | Not verified |
No recorded checks match this filter.
How to use this Shadowsocks configuration
- Download the current configuration while a fresh verification is available.
- Import it into a Shadowsocks-compatible client, preserving all required transport, security and authentication parameters.
- 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.