Skip to main content
Tunnel verified at last checkLast result: 2026-09-11 13:38:52 UTC

Connection and verification

Protocol
Shadowsocks
Address
15.204.247.206:4444
Transport / security
TCP / NONE
Last verified exit IP
15.204.247.206
Last verified handshake
487 ms
Last verified HTTPS first byte
871 ms
Download speed
1.864 Mbps
Source
v2go hourly full-tunnel tested configs
First recorded check
2026-09-09 10:54:14 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)
4870 2026-09-10 02:32:06 UTC: 402 ms2026-09-11 13:38:52 UTC: 487 ms09-10 02:3209-11 13:38Check time (UTC)
HTTPS first byte (ms)
8710 2026-09-10 02:32:06 UTC: 787 ms2026-09-11 13:38:52 UTC: 871 ms09-10 02:3209-11 13:38Check 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 ok487 ms871 ms15.204.247.206
Tunnel ok402 ms787 ms15.204.247.206
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.