The long view
NAT is a bridge, not a destination. Every flow that moves to IPv6 is one less flow that needs translation, reducing load, cost and logging volume.
Dual stack
The most common approach: subscribers get both an IPv6 prefix and IPv4 access through CGNAT. Applications that support IPv6 use it automatically. Large content platforms already serve much of their traffic over IPv6.
IPv6-only with translation
Some networks go further and run IPv6-only internally, using NAT64 and DNS64 so subscribers can still reach IPv4-only sites. This simplifies the internal network.
464XLAT
Mobile networks often use 464XLAT, which lets IPv4-only applications on a device work over an IPv6-only network.
Measuring progress
Track the percentage of your traffic on IPv6. As it grows, CGNAT capacity needs fall.
Where Peer1IX helps
NAT Gateway supports transition designs, and peering at Peer1IX over IPv6 lets your IPv6 traffic reach content networks directly.
Check IPv6 adoption in India with our country insights tool.
