Live checked Hysteria2 servers
Fresh Hysteria2 QUIC endpoints verified through a complete UDP tunnel, HTTPS request and changed public exit IP.
Fresh Hysteria2 QUIC endpoints verified through a complete UDP tunnel, HTTPS request and changed public exit IP.
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.
| Endpoint | Connection | Exit IP / country | Performance | Checked / stability | Source | Config |
|---|---|---|---|---|---|---|
UDPTLS |
109.235.49.234Netherlands |
Speed5 MbpsHandshake833 msHTTPS1022 ms |
100% successful 6/6 checks · last 7d | GetFreeProxy Hysteria2 | Download | |
UDPTLS |
130.49.161.70Netherlands |
Speed9 MbpsHandshake362 msHTTPS534 ms |
100% successful 1/1 checks · last 7d · small sample | Iran Intranet Access verified configs | Download |
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.
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.
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.