Skip to main content

Filter WireGuard servers

More filters
Reset filters Stable servers Best speed Freshly checked Found: 0 / 0

About measurements and countries

Filters apply to the full catalog. Speed is the measured download rate. Latency is the HTTPS response time through the tunnel. Unknown measurements are excluded when a limit is set.

Success rate uses saved check attempts in the last 7 days, including failures. Proxy history retains up to 100 checks per configuration. This is a sample, not continuous uptime. A rate filter requires at least 5 checks; increase the minimum checks for a larger sample.

Exit country is an approximate location of the verified exit IP. IP Geolocation by DB-IP (2026-10, CC BY 4.0). Unmapped addresses appear as Unknown.

Recently verified WireGuard endpoints

Each source catalog applies its freshness and publication checks. 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.

Search indexing paused: zero usable rows seven days. The gate requires at least 10 unique endpoints, 3 independent sources and 7 qualifying days in the last 14. The page remains available with noindex,follow while evidence accumulates.

No fresh full-tunnel checks are available yet.

A full-tunnel checker and complete publishable client configurations are not connected for this protocol yet. Server cards and check history will become available when verified configurations exist.

WireGuard JSON API

Use /api/v1/servers?protocol=wireguard&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 WireGuard API guide or read the complete API v1 documentation.

About WireGuard

WireGuard creates an encrypted IP interface and associates public keys with tunnel addresses. AllowedIPs acts as both a routing selector and a peer address policy. For a full-device tunnel, IPv4 and IPv6 default routes, DNS behavior and the peer configuration all need to be correct.

What a working configuration needs

A relay hostname and port are not a usable WireGuard profile. A publishable client key, peer key and allowed-IP configuration are required.

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 WireGuard protocol, configuration and troubleshooting guide.