AWS charge for using IPv4 expected to bring $1B/year and speed up IPv6 adoption

Original Article ↗ Hacker News Discussion ↗

Amazon Web Services’ new fee for public IPv4 addresses—estimated to generate up to $1B annually—is prompting cloud users to audit and reduce their IPv4 usage, but opinions differ on whether this will materially accelerate IPv6 adoption. Commenters note that many workloads can fall back to private IPv4 or NAT rather than moving to IPv6, and that real bottlenecks remain with ISPs, enterprises, and major platforms that still lack robust IPv6 support. While some see economic pressure from AWS and others as necessary to push the internet off scarce IPv4 space, others argue the operational complexity of dual-stack networks and uneven IPv6 reliability continue to slow progress.

Impact of AWS IPv4 Fees

  • Many expect AWS’s new per-IPv4 charge to push customers to audit usage and drop unnecessary public IPv4s, especially on internal EC2 instances.
  • Some argue this mostly encourages private IPv4 + NAT, not IPv6-only, so external services will remain dual-stack and end users won’t see a big shift.
  • Others note AWS owns a large chunk of IPv4 space; charging just rebalances economics rather than “killing” IPv4.
  • There’s concern that freeing unused IPv4s could ease scarcity and actually reduce pressure on ISPs to deploy IPv6.

Cloud & Service Provider Limitations

  • Several AWS services and patterns still lack full IPv6 support (e.g., some load balancers can’t be IPv6-only; some services require public IPv4 for updates or SaaS access).
  • GitHub and various PaaS/IaaS wrappers (Heroku, Vercel, others) are cited as lagging on IPv6, forcing workarounds like SSH tunnels or NAT64.
  • Azure is reportedly planning similar IPv4 charges but with fragile NAT gateway designs.
  • NAT gateway pricing is a pain point; some hoped IPv4 fees would be offset by cheaper NAT.

ISP and Enterprise Adoption Patterns

  • Multiple anecdotes: some residential ISPs rolled out IPv6 years ago; others offer it only on certain access types, or rolled it back after problems.
  • Many ISPs default to CGNAT for IPv4; static IPv4 often costs extra, while IPv6 is absent or poorly documented.
  • Google’s IPv6 stats were cited: higher IPv6 usage on weekends suggests home networks are ahead of enterprises, where change aversion is strong.

Practical Problems with IPv6

  • Users report broken or flaky ISP implementations leading them to disable IPv6 entirely.
  • Dual-stack introduces operational overhead: two sets of firewall rules, monitoring, and diagnostics.
  • Some complain about protocol complexity (SLAAC vs DHCPv6, multiple addresses per interface, transition mechanisms) and weak documentation.
  • Misaligned prefix delegation (only /64s) conflicts with best-practice advice (/56 or /48), causing subnetting headaches.

Benefits and Use Cases

  • Advocates highlight: easier home servers (no NAT, many “static” IPs), better P2P/gaming/VoIP, fewer CGNAT issues, and simpler interconnection between private networks.
  • For many “everyday users,” benefits are mostly invisible; biggest gains accrue to ISPs, mobile networks, and P2P-heavy applications.

Long-Term Outlook and Attitudes

  • Some see AWS’s move as a long-overdue nudge that will, over years, normalize IPv6.
  • Others are skeptical, suggesting IPv6 has “failed to launch” after decades and that network effects keep IPv4 entrenched.
  • A recurring view: real acceleration will come when major platforms or app stores start effectively requiring IPv6 support.