Skip to main content
Tunnel verified at last checkLast result: 2026-09-11 05:56:31 UTC

Connection and verification

Protocol
Shadowsocks
Address
139.180.220.175:8388
Transport / security
TCP / NONE
Last verified exit IP
139.180.220.175
Last verified handshake
785 ms
Last verified HTTPS first byte
1,469 ms
Download speed
Not measured
Source
rjsxrd secure tunnel-tested configs
First recorded check
2026-09-09 12:03:46 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)
7850 2026-09-09 21:22:41 UTC: 686 ms2026-09-11 05:56:31 UTC: 785 ms09-09 21:2209-11 05:56Check time (UTC)
HTTPS first byte (ms)
14690 2026-09-09 21:22:41 UTC: 1,358 ms2026-09-11 05:56:31 UTC: 1,469 ms09-09 21:2209-11 05:56Check 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 ok785 ms1,469 ms139.180.220.175
Tunnel ok686 ms1,358 ms139.180.220.175
Policy blockedNot measuredNot measuredNot verified

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.