Why IPv4 Costs Are Rising and How to Seamlessly Transition to IPv6

Public IPv4 addresses are running out, prompting major cloud providers to start charging for their use: AWS bills $0.005 per hour per address (about $4 per month), Fly.io charges roughly $2 per month per dedicated IPv4, and Supabase plans a $4‑per‑month add‑on.

Supabase CEO Paul Copplestone warns that these fees will significantly increase infrastructure costs, especially for startups and SMEs, and urges the industry to prepare for IPv6 migration.

Three Cost‑Mitigation Options

Pass the cost to customers. Providers can add a surcharge for IPv4 usage, e.g., AWS’s $0.05 per day translates to $43.80 per year per address.

Offer workarounds such as IPv4 proxies or NAT. Mapping IPv6 traffic to IPv4 reduces direct IPv4 demand and allows shared address usage via port differentiation.

Adopt IPv6 exclusively. IPv6 provides a vastly larger address space (≈3.4×10^38 addresses) and better support for mobile devices, simpler headers, and improved security.

Challenges Facing IPv6 Adoption

Despite its advantages, IPv6 deployment faces two major hurdles:

Insufficient ISP support. Many ISPs lack updated hardware, software, and routing configurations for IPv6, making the transition costly and slow.

Lack of tooling. Development tools and platforms often do not enable IPv6 by default, requiring manual configuration.

Example DNS resolution illustrates the difference:

example.com → 93.184.216.34   // IPv4
example.com → 2607:f8b0:4006:819::200e   // IPv6

Enabling IPv6 in Common Infrastructure

To support IPv6, organizations need to adjust several components:

Add IPv6 to VPC networks.

Enable IPv6 on Airflow VMs.

Configure Docker and Docker‑Compose for IPv6.

Docker configuration steps:

"ipv6": true,
"fixed-cidr-v6": "fd00:ffff::/80",
"ip6tables": true,
"experimental": true

Restart Docker: systemctl restart docker Create and test an IPv6 network:

docker network create --ipv6 --subnet fd00:ffff::/80 ip6net
docker run --rm -it --network ip6net busybox ping6 google.com -c3

Check IPv6 iptables: ip6tables -L Update docker-compose.yaml:

# enable IPv6 to default network
networks:
  default:
    enable_ipv6: true
    ipam:
      config:
        - subnet: fd00:c16a:601e::/80
          gateway: fd00:c16a:601e::1

Verify inside a container:

docker exec -it "airflow_airflow-worker_1" bash
curl -6 https://ifconfig.co/ip

Real‑World Migration Pain Points

DevOps engineer Mathew Duggan recounts multiple issues when moving a server to IPv6:

SSH connectivity fails because his ISP and the server’s ISP lack IPv6 support, forcing a temporary IPv4 address.

GitHub access fails despite expectations that GitHub supports IPv6, requiring a proxy.

Datadog installation scripts break due to IPv6 incompatibilities, resolved only after manual intervention.

He resorted to NAT64 services (e.g., https://nat64.net/) to reach IPv4 resources from an IPv6‑only environment.

Conclusion

IPv6 offers a sustainable solution to address exhaustion, but widespread adoption is hampered by ISP readiness and tooling gaps. Organizations must proactively enable IPv6 in their infrastructure, educate teams, and adopt interim solutions like proxies or NAT64 while the ecosystem catches up.