Skip to main content

Free Hysteria2 configs with a Netherlands exit IP

This selection contains Hysteria2 configurations whose observed exit IP maps to the Netherlands. It provides a country-specific starting point for testing Hysteria2, with the actual checker results alongside each download. A successful result applies to the checker’s network; your local network still needs to support the connection.

2 matching checked endpoints Snapshot Compare servers How to connect More filters

Checked Hysteria2 in the Netherlands servers

Rows come from the current published tunnel checks and are ordered by their last check time. Compare the exit IP, connection settings and saved history before choosing a configuration. A snapshot update does not mean every row was checked at that moment.

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

Speed and HTTPS response time are measurements from the checker’s network. Weekly success is the share of saved successful attempts in the last seven days, with the sample count shown; it is not continuous uptime. Missing measurements stay unknown.

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.

How to connect with a Hysteria2 configuration

  1. Choose a row with a recent check and open its details to review the saved results.
  2. Download the complete configuration and import it into a client that supports Hysteria2 and the row’s transport and security settings.
  3. Enable the client’s intended proxy or tunnel mode. Confirm that the application you are testing is included in its routing rules.
  4. Check your public IP and run a leak test. Compare the observed exit with the selected row, then measure performance from your own network.

If a download is no longer available, return to the current selection and choose another recent row. Public endpoints change between checks. A successful tunnel test does not verify the operator’s privacy practices; read the public endpoint risk guide.

Explore other countries and protocols

All Hysteria2 servers · Compare all protocols