Skip to main content
Inactive — did not pass verificationLast result: 2026-09-10 10:08:27 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
139.84.166.47:8388
Transport / security
TCP / NONE
Last verified exit IP
139.84.166.47
Last verified handshake
3,017 ms
Last verified HTTPS first byte
3,816 ms
Download speed
2.255 Mbps
Source
0xRadikal verified downloadable configs
First recorded check
2026-09-07 06:39:43 UTC
Recorded tunnel checks
2
Successful tunnel checks
2
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)
30170 2026-09-07 06:39:43 UTC: 491 ms2026-09-10 10:08:27 UTC: 3,017 ms09-07 06:3909-10 10:08Check time (UTC)
HTTPS first byte (ms)
38160 2026-09-07 06:39:43 UTC: 996 ms2026-09-10 10:08:27 UTC: 3,816 ms09-07 06:3909-10 10:08Check time (UTC)

Check history

Latest 2 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 ok3,017 ms3,816 ms139.84.166.47
Tunnel ok491 ms996 ms139.84.166.47

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.