Skip to main content
Tunnel verified at last checkLast result: 2026-09-09 17:54:45 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
679 ms
Last verified HTTPS first byte
1,344 ms
Download speed
2.401 Mbps
Source
Firmfox Proxify mixed configs
First recorded check
2026-09-05 00:47:47 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)
38620 2026-09-05 00:47:47 UTC: 755 ms2026-09-08 12:45:10 UTC: 3,862 ms2026-09-08 12:45:45 UTC: 667 ms2026-09-09 17:54:45 UTC: 679 ms09-05 00:4709-09 17:54Check time (UTC)
HTTPS first byte (ms)
45600 2026-09-05 00:47:47 UTC: 1,409 ms2026-09-08 12:45:10 UTC: 4,560 ms2026-09-08 12:45:45 UTC: 1,303 ms2026-09-09 17:54:45 UTC: 1,344 ms09-05 00:4709-09 17:54Check 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 ok679 ms1,344 ms45.32.16.53
Tunnel ok667 ms1,303 ms45.32.16.53
Tunnel ok3,862 ms4,560 ms45.32.16.53
Tunnel ok755 ms1,409 ms45.32.16.53

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.