Skip to main content

Filter Hysteria2 servers

More filters (1 active)

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 Hysteria2 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.

EndpointConnectionExit IP / countryPerformanceChecked / stabilitySourceConfig
UDPTLS
130.49.161.70Netherlands
Speed10 MbpsHandshake351 msHTTPS535 ms
100% successful 1/1 checks · last 7d · small sample Firmfox Proxify mixed configs Download
UDPTLS
109.235.49.234Netherlands
Speed10 MbpsHandshake589 msHTTPS767 ms
100% successful 5/5 checks · last 7d GetFreeProxy Hysteria2 Download

Hysteria2 JSON API

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

About Hysteria2

A Hysteria2 client establishes a QUIC connection protected by TLS and carries proxied TCP or UDP traffic inside it. QUIC runs over UDP and handles streams, loss and congestion differently from a TCP-based proxy. Optional obfuscation and bandwidth settings are deployment-specific.

What a working configuration needs

Hysteria2 requires UDP reachability and valid TLS parameters; a TCP port probe cannot verify it.

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