Skip to main content
Inactive — did not pass verificationLast result: 2026-09-11 17:15:35 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
2.58.81.221:80
Transport / security
TCP / NONE
Last verified exit IP
2.58.81.221
Last verified handshake
642 ms
Last verified HTTPS first byte
979 ms
Download speed
2.334 Mbps
Source
Au1rxx verified downloadable configs
First recorded check
2026-09-05 15:23:21 UTC
Recorded tunnel checks
4
Successful tunnel checks
4
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

Tunnel handshake (ms)
6420 2026-09-05 15:23:21 UTC: 215 ms2026-09-09 16:07:40 UTC: 401 ms2026-09-10 16:44:20 UTC: 333 ms2026-09-11 17:15:35 UTC: 642 ms09-05 15:2309-11 17:15Check time (UTC)
HTTPS first byte (ms)
9790 2026-09-05 15:23:21 UTC: 419 ms2026-09-09 16:07:40 UTC: 639 ms2026-09-10 16:44:20 UTC: 628 ms2026-09-11 17:15:35 UTC: 979 ms09-05 15:2309-11 17:15Check time (UTC)

Check history

Latest 4 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.

Recorded Shadowsocks checks, newest first
Checked (UTC)ResultHandshakeHTTPS first byteExit IP
Tunnel ok642 ms979 ms2.58.81.221
Tunnel ok333 ms628 ms2.58.81.221
Tunnel ok401 ms639 ms2.58.81.221
Tunnel ok215 ms419 ms2.58.81.221

How to use this Shadowsocks configuration

  1. Download the current configuration while a fresh verification is available.
  2. Import it into a Shadowsocks-compatible client, preserving all required transport, security and authentication parameters.
  3. 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.