Skip to main content
Tunnel verified at last checkLast result: 2026-09-11 06:49:06 UTC

Connection and verification

Protocol
Shadowsocks
Address
15.204.246.132:7307
Transport / security
TCP / NONE
Last verified exit IP
15.204.246.132
Last verified handshake
1,724 ms
Last verified HTTPS first byte
3,167 ms
Download speed
1.067 Mbps
Source
0xRadikal verified downloadable configs
First recorded check
2026-09-04 21:38:56 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)
48520 2026-09-04 21:38:56 UTC: 4,852 ms2026-09-08 08:27:31 UTC: 674 ms2026-09-08 09:06:25 UTC: 400 ms2026-09-09 22:08:32 UTC: 583 ms2026-09-11 06:49:06 UTC: 1,724 ms09-04 21:3809-11 06:49Check time (UTC)
HTTPS first byte (ms)
53140 2026-09-04 21:38:56 UTC: 5,314 ms2026-09-08 08:27:31 UTC: 1,065 ms2026-09-08 09:06:25 UTC: 792 ms2026-09-09 22:08:32 UTC: 1,060 ms2026-09-11 06:49:06 UTC: 3,167 ms09-04 21:3809-11 06:49Check 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 ok1,724 ms3,167 ms15.204.246.132
Tunnel ok583 ms1,060 ms15.204.246.132
Tunnel ok400 ms792 ms15.204.246.132
Tunnel ok674 ms1,065 ms15.204.246.132
Tunnel ok4,852 ms5,314 ms15.204.246.132

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.