Shadowsocks server 193.29.139.198:8080
TCP / NONE · Anonymous tested configs
TCP / NONE · Anonymous tested configs
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.
Hover or focus a point for check details. Click or tap to keep them open.
Latest 8 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 | 220 ms | 406 ms | 193.29.139.198 | |
| Tunnel ok | 202 ms | 383 ms | 193.29.139.198 | |
| Tunnel ok | 201 ms | 379 ms | 193.29.139.198 | |
| Tunnel ok | 194 ms | 375 ms | 193.29.139.198 | |
| Tunnel ok | 204 ms | 391 ms | 193.29.139.198 | |
| Tunnel ok | 191 ms | 386 ms | 193.29.139.198 | |
| Tunnel ok | 196 ms | 380 ms | 193.29.139.198 | |
| Tunnel failed | Not measured | Not measured | Not verified |
No recorded checks match this filter.
If it fails, compare the latest check time, try a different endpoint or report the problem. Public source configurations can change between checks.
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.