Shadowsocks server 211.174.113.172:49642
TCP / NONE · v2go hourly full-tunnel tested configs
Tunnel verified at last checkLast result: 2026-10-09 06:25:30 UTC
Connection and verification
- Protocol
- Shadowsocks
- Address
- 211.174.113.172:49642
- Transport / security
- TCP / NONE
- Last verified exit IP
- 211.174.113.172
- Last verified handshake
- 4,651 ms
- Last verified HTTPS first byte
- 7,898 ms
- Download speed
- Not measured
- Source
- v2go hourly full-tunnel tested configs
- First recorded check
- 2026-09-28 05:58:22 UTC
- Recorded tunnel checks
- 12
- Successful tunnel checks
- 11
- Recorded tunnel success rate
- 91.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.
Check history
Latest 12 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 | 4,651 ms | 7,898 ms | 211.174.113.172 | |
| Tunnel ok | 3,769 ms | 6,904 ms | 211.174.113.172 | |
| Tunnel failed | Not measured | Not measured | Not verified | |
| Tunnel ok | 1,203 ms | 1,816 ms | 211.174.113.172 | |
| Tunnel ok | 4,207 ms | 6,974 ms | 211.174.113.172 | |
| Tunnel ok | 3,770 ms | 6,484 ms | 211.174.113.172 | |
| Tunnel ok | 2,979 ms | 6,940 ms | 211.174.113.172 | |
| Tunnel ok | 2,341 ms | 3,282 ms | 211.174.113.172 | |
| Tunnel ok | 2,159 ms | 3,812 ms | 211.174.113.172 | |
| Tunnel ok | 877 ms | 1,341 ms | 211.174.113.172 | |
| Tunnel ok | 4,589 ms | 8,802 ms | 211.174.113.172 | |
| Tunnel ok | 2,118 ms | 3,502 ms | 211.174.113.172 |
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.