Skip to main content
Inactive — did not pass verificationLast result: 2026-09-11 00:03:02 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
51.79.64.198:8119
Transport / security
TCP / NONE
Last verified exit IP
51.79.64.198
Last verified handshake
621 ms
Last verified HTTPS first byte
1,022 ms
Download speed
4.043 Mbps
Source
Au1rxx verified downloadable configs
First recorded check
2026-09-05 15:23:49 UTC
Recorded tunnel checks
5
Successful tunnel checks
5
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)
6730 2026-09-05 15:23:49 UTC: 673 ms2026-09-09 12:42:31 UTC: 439 ms2026-09-09 12:57:59 UTC: 423 ms2026-09-09 18:49:01 UTC: 480 ms2026-09-11 00:03:02 UTC: 621 ms09-05 15:2309-11 00:03Check time (UTC)
HTTPS first byte (ms)
11100 2026-09-05 15:23:49 UTC: 1,110 ms2026-09-09 12:42:31 UTC: 833 ms2026-09-09 12:57:59 UTC: 824 ms2026-09-09 18:49:01 UTC: 876 ms2026-09-11 00:03:02 UTC: 1,022 ms09-05 15:2309-11 00:03Check time (UTC)

Check history

Latest 5 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 ok621 ms1,022 ms51.79.64.198
Tunnel ok480 ms876 ms51.79.64.198
Tunnel ok423 ms824 ms51.79.64.198
Tunnel ok439 ms833 ms51.79.64.198
Tunnel ok673 ms1,110 ms51.79.64.198

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.