Skip to main content
Inactive — did not pass verificationLast result: 2026-09-10 21:08:07 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
15.204.247.244:4444
Transport / security
TCP / NONE
Last verified exit IP
15.204.247.244
Last verified handshake
1,314 ms
Last verified HTTPS first byte
1,756 ms
Download speed
3.079 Mbps
Source
0xRadikal verified downloadable configs
First recorded check
2026-09-04 23:23:31 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)
30130 2026-09-04 23:23:31 UTC: 3,013 ms2026-09-08 11:27:31 UTC: 388 ms2026-09-09 18:08:58 UTC: 467 ms2026-09-10 21:08:07 UTC: 1,314 ms09-04 23:2309-10 21:08Check time (UTC)
HTTPS first byte (ms)
42300 2026-09-04 23:23:31 UTC: 4,230 ms2026-09-08 11:27:31 UTC: 759 ms2026-09-09 18:08:58 UTC: 925 ms2026-09-10 21:08:07 UTC: 1,756 ms09-04 23:2309-10 21:08Check 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 ok1,314 ms1,756 ms15.204.247.244
Tunnel ok467 ms925 ms15.204.247.244
Tunnel ok388 ms759 ms15.204.247.244
Tunnel ok3,013 ms4,230 ms15.204.247.244

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.