Shadowsocks server 82.38.31.175:8080
TCP / NONE · Au1rxx verified downloadable configs
Inactive — did not pass verificationLast result: 2026-10-09 06:25:34 UTC
This endpoint has no current downloadable verification, or a newer check did not succeed. Previous measurements below are historical. Choose another checked Shadowsocks server.
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
- 186 ms
- Last verified HTTPS first byte
- 360 ms
- Download speed
- 5.836 Mbps
- Source
- Au1rxx verified downloadable configs
- First recorded check
- 2026-09-10 07:37:41 UTC
- Recorded tunnel checks
- 26
- Successful tunnel checks
- 25
- Recorded tunnel success rate
- 96.2%
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 26 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 | 186 ms | 360 ms | 193.29.139.135 | |
| Tunnel ok | 209 ms | 388 ms | 193.29.139.135 | |
| Tunnel ok | 229 ms | 425 ms | 193.29.139.135 | |
| Tunnel ok | 185 ms | 504 ms | 193.29.139.135 | |
| Tunnel ok | 226 ms | 414 ms | 193.29.139.135 | |
| Tunnel ok | 172 ms | 334 ms | 193.29.139.135 | |
| Tunnel ok | 269 ms | 469 ms | 193.29.139.135 | |
| Tunnel ok | 184 ms | 357 ms | 193.29.139.135 | |
| Tunnel ok | 200 ms | 385 ms | 193.29.139.135 | |
| Tunnel ok | 216 ms | 402 ms | 193.29.139.135 | |
| Tunnel ok | 177 ms | 344 ms | 193.29.139.135 | |
| Tunnel ok | 210 ms | 398 ms | 193.29.139.135 | |
| Tunnel ok | 196 ms | 377 ms | 193.29.139.135 | |
| Tunnel ok | 253 ms | 474 ms | 193.29.139.135 | |
| Tunnel ok | 219 ms | 411 ms | 193.29.139.135 | |
| Tunnel ok | 296 ms | 527 ms | 193.29.139.135 | |
| Tunnel ok | 211 ms | 404 ms | 193.29.139.135 | |
| Tunnel ok | 238 ms | 441 ms | 193.29.139.135 | |
| Tunnel ok | 237 ms | 432 ms | 193.29.139.135 | |
| Tunnel ok | 248 ms | 446 ms | 193.29.139.135 | |
| Tunnel ok | 231 ms | 424 ms | 193.29.139.135 | |
| Tunnel ok | 216 ms | 405 ms | 193.29.139.135 | |
| Tunnel ok | 203 ms | 380 ms | 193.29.139.135 | |
| Tunnel ok | 207 ms | 391 ms | 193.29.139.135 | |
| Tunnel ok | 216 ms | 397 ms | 193.29.139.135 | |
| 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.