Live checked Shadowsocks servers — Page 3

Recently verified Shadowsocks endpoints

Only checks newer than 72 hours are eligible. A row requires a real protocol tunnel, successful HTTPS traffic and a public exit IP different from the checker’s direct IP. Reachable ports and source-reported status are excluded.

The server-rendered table shows the 20 newest verified endpoints. Use the next page for more server cards and check histories, or retrieve the full list from the JSON API.

Shadowsocks JSON API

Use /api/v1/servers?protocol=shadowsocks&status=online to retrieve the same fresh, downloadable and full-tunnel-verified rows without scraping this table. The response includes stable public IDs, transport metadata, the observed exit IP, checker timings and the current config download URL.

Open the Shadowsocks API guide or read the complete API v1 documentation.

About Shadowsocks

The local Shadowsocks client accepts proxy traffic from applications, encrypts it and sends it to the remote server. The server decrypts each request and connects to the destination. TCP and UDP support depends on both the client and server configuration.

What a working configuration needs

Outline access keys use the Shadowsocks protocol family, so Outline is covered here instead of being counted as a separate tunnel protocol.

Connection material is quarantined and never printed in tables or logs. A download is returned only for a fresh full-tunnel result whose exact URI is still present in an allowlisted public source permitted by the publication policy.

Unknown public infrastructure may observe or manipulate traffic. Do not use community endpoints for banking, work accounts, private source code or other sensitive activity. Read the public endpoint risk guide.

Read the complete Shadowsocks protocol, configuration and troubleshooting guide.