Skip to main content
Tunnel verified at last checkLast result: 2026-09-09 20:03:24 UTC

Connection and verification

Protocol
Shadowsocks
Address
15.204.246.111:5498
Transport / security
TCP / NONE
Last verified exit IP
15.204.246.111
Last verified handshake
606 ms
Last verified HTTPS first byte
1,028 ms
Download speed
4.38 Mbps
Source
Barry Shadowsocks
First recorded check
2026-09-05 18:19:01 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)
25510 2026-09-05 18:19:01 UTC: 2,551 ms2026-09-09 05:27:58 UTC: 388 ms2026-09-09 20:03:24 UTC: 606 ms09-05 18:1909-09 20:03Check time (UTC)
HTTPS first byte (ms)
45040 2026-09-05 18:19:01 UTC: 4,504 ms2026-09-09 05:27:58 UTC: 865 ms2026-09-09 20:03:24 UTC: 1,028 ms09-05 18:1909-09 20:03Check 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 ok606 ms1,028 ms15.204.246.111
Tunnel ok388 ms865 ms15.204.246.111
Tunnel ok2,551 ms4,504 ms15.204.246.111

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.