Testing Hysteria2 through a Dutch exit
Use a client that explicitly supports Hysteria2 and preserve the supplied authentication, TLS and obfuscation settings. Hysteria2 uses a UDP-based transport, so a network that blocks UDP can fail before useful traffic starts. For a comparison, try a compatible Dutch VLESS configuration and record both results without assuming that a shared country implies a shared network path.
How the exit country is determined
The country beside each row comes from the public IP observed through the tunnel, using the active DB-IP Country Lite dataset. Country-level GeoIP is approximate and can differ from a website’s own location database. It does not establish a city, a physical server location or the operator’s jurisdiction. Country data by DB-IP, CC BY 4.0.
Can I import these profiles into a Hysteria version 1 client?
Hysteria2 requires version 2 protocol support. Check the client’s supported protocol list and use the matching import format. A similar protocol name does not make a version 1 configuration interchangeable with version 2.
Client configuration reference: Hysteria2 outbound settings in sing-box.