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

Connection and verification

Protocol
Shadowsocks
Address
209.46.102.22:8388
Transport / security
TCP / NONE
Last verified exit IP
209.46.102.22
Last verified handshake
220 ms
Last verified HTTPS first byte
564 ms
Download speed
6.578 Mbps
Source
0xRadikal verified downloadable configs
First recorded check
2026-09-04 14:26:27 UTC
Recorded tunnel checks
3
Successful tunnel checks
3
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)
2430 2026-09-04 14:26:27 UTC: 221 ms2026-09-07 18:22:04 UTC: 243 ms2026-09-10 00:42:37 UTC: 220 ms09-04 14:2609-10 00:42Check time (UTC)
HTTPS first byte (ms)
6300 2026-09-04 14:26:27 UTC: 555 ms2026-09-07 18:22:04 UTC: 630 ms2026-09-10 00:42:37 UTC: 564 ms09-04 14:2609-10 00:42Check time (UTC)

Check history

Latest 3 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 ok220 ms564 ms209.46.102.22
Tunnel ok243 ms630 ms209.46.102.22
Tunnel ok221 ms555 ms209.46.102.22

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.