Private Connectivity subnet access changes

Author: NicoletaComan

content/en/docs/control-center/security/private-connectivity/configure-private-connectivity.md

@@ -478,7 +478,12 @@ The Mendix internal systems operate on the following subnets:
 * 172.20.0.0/16
 
 As such, when you expose a subnet or a single IP address, it must not conflict with our private IP ranges.     
-If you absolutely must use the subnets on which Mendix operates, please configure [Network address translation (NAT)](https://en.wikipedia.org/wiki/Network_address_translation) on your infrastructure.
+If you absolutely must use the subnets on which Mendix operates, configure [4via6 subnet routers](https://tailscale.com/docs/features/subnet-routers/4via6-subnets) on your infrastructure. Follow these steps to do that:
+
+1. Generate the IPv6 subnet route – Run `tailscale debug via 100 <Your IPv4 range>` in your terminal.
+2. Advertise the IPv6 subnet route – Run `tailscale set --advertise-routes=<Newly generated IPv6 range>` in your terminal.    
+
+You can then continue with the steps in the [Enabling and Disabling Resources](/control-center/configure-private-connectivity/#private-connectivity-resources-enable-disable) section.
 
 ### Restricted IP Ranges
 

content/en/docs/releasenotes/control-center/2026.md

@@ -7,6 +7,15 @@ weight: 1
 numberless_headings: true
 ---
 
+## April 2026
+
+### April 23, 2026
+
+#### Improvements
+
+* We have moved away from [Network address translation (NAT)](https://en.wikipedia.org/wiki/Network_address_translation) for Private Connectivity subnet access, and are now requiring [4via6 subnet routers](https://tailscale.com/docs/features/subnet-routers/4via6-subnets) instead.    
+    For details, refer to [Configuring and Using Private Connectivity](/control-center/configure-private-connectivity/).
+
 ## February 2026
 
 ### February 1, 2026