Skip to main content
Tunnel verified at last checkLast result: 2026-09-10 17:06:25 UTC

Connection and verification

Protocol
Shadowsocks
Address
45.32.16.53:8388
Transport / security
TCP / NONE
Last verified exit IP
45.32.16.53
Last verified handshake
676 ms
Last verified HTTPS first byte
1,334 ms
Download speed
2.604 Mbps
Source
Alexant frequently refreshed configs
First recorded check
2026-09-08 14:16:21 UTC
Recorded tunnel checks
2
Successful tunnel checks
2
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)
6860 2026-09-09 16:19:18 UTC: 686 ms2026-09-10 17:06:25 UTC: 676 ms09-09 16:1909-10 17:06Check time (UTC)
HTTPS first byte (ms)
13540 2026-09-09 16:19:18 UTC: 1,354 ms2026-09-10 17:06:25 UTC: 1,334 ms09-09 16:1909-10 17:06Check time (UTC)

Check history

Latest 3 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 ok676 ms1,334 ms45.32.16.53
Tunnel ok686 ms1,354 ms45.32.16.53
Policy blockedNot measuredNot measuredNot verified

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.