Skip to main content
Tunnel verified at last checkLast result: 2026-09-11 10:29:00 UTC

Connection and verification

Protocol
Shadowsocks
Address
173.244.56.6:443
Transport / security
TCP / NONE
Last verified exit IP
173.244.56.6
Last verified handshake
513 ms
Last verified HTTPS first byte
837 ms
Download speed
3.247 Mbps
Source
Freedom V2Ray tested configs
First recorded check
2026-09-03 22:03: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)
6480 2026-09-03 22:03:49 UTC: 518 ms2026-09-06 23:19:29 UTC: 648 ms2026-09-06 23:35:11 UTC: 541 ms2026-09-10 00:34:02 UTC: 521 ms2026-09-11 10:29:00 UTC: 513 ms09-03 22:0309-11 10:29Check time (UTC)
HTTPS first byte (ms)
9660 2026-09-03 22:03:49 UTC: 843 ms2026-09-06 23:19:29 UTC: 966 ms2026-09-06 23:35:11 UTC: 861 ms2026-09-10 00:34:02 UTC: 842 ms2026-09-11 10:29:00 UTC: 837 ms09-03 22:0309-11 10:29Check 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 ok513 ms837 ms173.244.56.6
Tunnel ok521 ms842 ms173.244.56.6
Tunnel ok541 ms861 ms173.244.56.6
Tunnel ok648 ms966 ms173.244.56.6
Tunnel ok518 ms843 ms173.244.56.6

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.