<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>– Networking</title><link>https://changelog.exoscale.com/tags/networking/</link><description>Recent content in Networking on</description><generator>Hugo -- gohugo.io</generator><language>en</language><lastBuildDate>Thu, 24 Sep 2026 12:00:00 +0000</lastBuildDate><atom:link href="https://changelog.exoscale.com/tags/networking/rss.xml" rel="self" type="application/rss+xml"/><item><title>Network Load Balancer now supports IPv6</title><link>https://changelog.exoscale.com/network-load-balancer-ipv6/</link><pubDate>Thu, 24 Sep 2026 12:00:00 +0000</pubDate><guid>https://changelog.exoscale.com/network-load-balancer-ipv6/</guid><description>
&lt;p&gt;Network Load Balancers now support IPv6. You can create an IPv6 Network Load Balancer in the &lt;a href="https://portal.exoscale.com/login?next=%2Fcompute%2Fload-balancers%2Fadd%3F"target="_blank" rel="noopener"&gt;Exoscale Portal&lt;/a&gt; or with the Exoscale CLI.&lt;/p&gt;
&lt;p&gt;&lt;img src="https://changelog.exoscale.com/network-load-balancer-ipv6/network-load-balancer-ipv6-image-01.png" alt="Selecting IPv6 as the address family when creating a Network Load Balancer in the Exoscale Portal" loading="lazy" /&gt;&lt;/p&gt;
&lt;p&gt;An IPv6 Network Load Balancer gets a public IPv6 address and distributes TCP and UDP traffic across the instances in your Instance Pools, just like an IPv4 Network Load Balancer.&lt;/p&gt;
&lt;h2&gt;Why use it&lt;span class="hx:absolute hx:-mt-20" id="why-use-it"&gt;&lt;/span&gt;
&lt;a href="#why-use-it" class="subheading-anchor" aria-label="Permalink for this section"&gt;&lt;/a&gt;&lt;/h2&gt;&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Lower cost:&lt;/strong&gt; Elastic IPv6 addresses are free, so you only pay the load balancer fee. An IPv6 Network Load Balancer costs &lt;strong&gt;EUR/CHF/USD 0.02083 per hour&lt;/strong&gt;, about 40% less than the IPv4 version. Check the &lt;a href="https://www.exoscale.com/pricing/"target="_blank" rel="noopener"&gt;pricing page&lt;/a&gt; for details.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Reach IPv6 users directly:&lt;/strong&gt; Serve users on IPv6-only and IPv6-first networks, natively and without translation layers.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Go fully IPv6:&lt;/strong&gt; Your instances already get a free public IPv6 address. Now the load balancer in front of them can be IPv6 too.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Nothing to give up:&lt;/strong&gt; Same health checks, load balancing strategies and 200 service limit as an IPv4 Network Load Balancer.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2&gt;Before you start&lt;span class="hx:absolute hx:-mt-20" id="before-you-start"&gt;&lt;/span&gt;
&lt;a href="#before-you-start" class="subheading-anchor" aria-label="Permalink for this section"&gt;&lt;/a&gt;&lt;/h2&gt;&lt;p&gt;The target Instance Pool must have IPv6 enabled (dual-stack). Instance Pools are IPv4 only by default, so set public IP assignment to dual-stack. Instances without an IPv6 address won&amp;rsquo;t receive traffic.&lt;/p&gt;
&lt;p&gt;&lt;a href="https://community.exoscale.com/product/networking/nlb/"target="_blank" rel="noopener"&gt;Learn more about Network Load Balancers →&lt;/a&gt;&lt;/p&gt;</description></item></channel></rss>