Shadowsocks server 82.38.31.62:8080
TCP / NONE · Au1rxx verified downloadable configs
Tunnel verified at last checkLast result: 2026-10-09 04:42:53 UTC
Connection and verification
- Protocol
- Shadowsocks
- Address
- 82.38.31.62:8080
- Transport / security
- TCP / NONE
- Last verified exit IP
- 193.29.139.202
- Last verified handshake
- 187 ms
- Last verified HTTPS first byte
- 360 ms
- Download speed
- 8.868 Mbps
- Source
- Au1rxx verified downloadable configs
- First recorded check
- 2026-09-12 11:23:07 UTC
- Recorded tunnel checks
- 24
- Successful tunnel checks
- 24
- Recorded tunnel success rate
- 100.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 25 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 | 187 ms | 360 ms | 193.29.139.202 | |
| Tunnel ok | 176 ms | 347 ms | 193.29.139.202 | |
| Preflight ok | Not measured | Not measured | Not verified | |
| Tunnel ok | 185 ms | 357 ms | 193.29.139.202 | |
| Tunnel ok | 231 ms | 415 ms | 193.29.139.202 | |
| Tunnel ok | 217 ms | 411 ms | 193.29.139.202 | |
| Tunnel ok | 183 ms | 370 ms | 193.29.139.202 | |
| Tunnel ok | 201 ms | 375 ms | 193.29.139.202 | |
| Tunnel ok | 217 ms | 407 ms | 193.29.139.202 | |
| Tunnel ok | 179 ms | 349 ms | 193.29.139.202 | |
| Tunnel ok | 375 ms | 564 ms | 193.29.139.202 | |
| Tunnel ok | 195 ms | 534 ms | 193.29.139.202 | |
| Tunnel ok | 191 ms | 365 ms | 193.29.139.202 | |
| Tunnel ok | 206 ms | 389 ms | 193.29.139.202 | |
| Tunnel ok | 228 ms | 419 ms | 193.29.139.202 | |
| Tunnel ok | 227 ms | 428 ms | 193.29.139.202 | |
| Tunnel ok | 204 ms | 384 ms | 193.29.139.202 | |
| Tunnel ok | 209 ms | 385 ms | 193.29.139.202 | |
| Tunnel ok | 215 ms | 407 ms | 193.29.139.202 | |
| Tunnel ok | 205 ms | 386 ms | 193.29.139.202 | |
| Tunnel ok | 199 ms | 379 ms | 193.29.139.202 | |
| Tunnel ok | 289 ms | 489 ms | 193.29.139.202 | |
| Tunnel ok | 208 ms | 388 ms | 193.29.139.202 | |
| Tunnel ok | 251 ms | 458 ms | 193.29.139.202 | |
| Tunnel ok | 199 ms | 378 ms | 193.29.139.202 |
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.