Shadowsocks server 51.38.71.51:2083
TCP / NONE · v2go hourly full-tunnel tested configs
Tunnel verified at last checkLast result: 2026-10-09 03:20:45 UTC
Connection and verification
- Protocol
- Shadowsocks
- Address
- 51.38.71.51:2083
- Transport / security
- TCP / NONE
- Last verified exit IP
- 51.38.71.51
- Last verified handshake
- 267 ms
- Last verified HTTPS first byte
- 484 ms
- Download speed
- 5.438 Mbps
- Source
- v2go hourly full-tunnel tested configs
- First recorded check
- 2026-09-11 10:38:06 UTC
- Recorded tunnel checks
- 28
- Successful tunnel checks
- 28
- 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 28 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 | 267 ms | 484 ms | 51.38.71.51 | |
| Tunnel ok | 271 ms | 468 ms | 51.38.71.51 | |
| Tunnel ok | 261 ms | 462 ms | 51.38.71.51 | |
| Tunnel ok | 589 ms | 802 ms | 51.38.71.51 | |
| Tunnel ok | 805 ms | 1,109 ms | 51.38.71.51 | |
| Tunnel ok | 299 ms | 529 ms | 51.38.71.51 | |
| Tunnel ok | 5,159 ms | 6,336 ms | 51.38.71.51 | |
| Tunnel ok | 267 ms | 481 ms | 51.38.71.51 | |
| Tunnel ok | 483 ms | 744 ms | 51.38.71.51 | |
| Tunnel ok | 852 ms | 1,159 ms | 51.38.71.51 | |
| Tunnel ok | 1,100 ms | 1,544 ms | 51.38.71.51 | |
| Tunnel ok | 1,834 ms | 2,541 ms | 51.38.71.51 | |
| Tunnel ok | 252 ms | 453 ms | 51.38.71.51 | |
| Tunnel ok | 657 ms | 874 ms | 51.38.71.51 | |
| Tunnel ok | 234 ms | 429 ms | 51.38.71.51 | |
| Tunnel ok | 259 ms | 450 ms | 51.38.71.51 | |
| Tunnel ok | 245 ms | 447 ms | 51.38.71.51 | |
| Tunnel ok | 266 ms | 463 ms | 51.38.71.51 | |
| Tunnel ok | 248 ms | 435 ms | 51.38.71.51 | |
| Tunnel ok | 268 ms | 456 ms | 51.38.71.51 | |
| Tunnel ok | 234 ms | 425 ms | 51.38.71.51 | |
| Tunnel ok | 273 ms | 476 ms | 51.38.71.51 | |
| Tunnel ok | 239 ms | 432 ms | 51.38.71.51 | |
| Tunnel ok | 263 ms | 457 ms | 51.38.71.51 | |
| Tunnel ok | 252 ms | 452 ms | 51.38.71.51 | |
| Tunnel ok | 533 ms | 817 ms | 51.38.71.51 | |
| Tunnel ok | 354 ms | 640 ms | 51.38.71.51 | |
| Tunnel ok | 1,058 ms | 1,376 ms | 51.38.71.51 |
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.
This saved detail page remains available with its check history. Search indexing requires current successful full-tunnel verification, real measurements and an available configuration.