Why IPv4 Is Getting Expensive and How to Overcome IPv6 Migration Challenges

IPv4 (Internet Protocol version 4) is the most widely used network‑layer protocol, defined in RFC 791 in 1981 with a 32‑bit address space that provides only about 4.3 billion unique addresses.

Because the address pool is limited, IANA announced IPv4 exhaustion in 2011, and many providers now charge for public IPv4 usage: AWS bills $0.005 per hour per address, Fly.io about $2 per month per address, and Supabase $4 per month.

Supabase CEO Paul Copplestone warns that IPv6 adoption is imminent, but the transition is difficult due to protocol incompatibility and operational challenges.

Global IPv4 depletion makes IPv6 migration a focus

RIPE NCC reported that the last IPv4 address block was exhausted on 25 Nov 2019, with 4.2 billion IPv4 addresses already allocated worldwide. Scarcity drives up costs, prompting large providers to charge for IPv4 to encourage IPv6 adoption.

Three strategic options

Shift IPv4 costs to customers (e.g., AWS, Fly.io pricing policies).

Provide IPv4 proxy or NAT solutions to map IPv6 traffic to IPv4 resources.

Offer IPv6‑only services, encouraging full migration.

IPv6 challenges

Long‑term, IPv6‑only is the most economical solution: it offers a vastly larger address space (~3.4×10^38 addresses), better mobile support, simpler headers, and higher security.

However, two major obstacles remain:

Insufficient ISP support for IPv6.

Lack of tooling and configuration support.

ISP support deficiency

Many ISPs have not updated their infrastructure to handle IPv6 DNS resolution and routing, leading to failures such as inability to SSH into AWS instances, broken database connections, and failed Vercel deployments. example.com → 93.184.216.34 When IPv6 is used, the same domain resolves to an IPv6 address:

example.com → 2607:f8b0:4006:819::200e

Tooling gaps

Developers must modify many components to support IPv6, including VPC networks, Airflow VMs, Docker, and Docker Compose. Example Docker daemon configuration:

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

After updating the daemon, restart Docker: systemctl restart docker Create a temporary IPv6 network and test connectivity:

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

Check IPv6 iptables rules: ip6tables -L Enable IPv6 in Docker Compose:

networks:
  default:
    enable_ipv6: true
    ipam:
      config:
        - subnet: fd00:c16a:601e::/80
          gateway: fd00:c16a:601e::1

Real‑world migration pain points

DevOps engineer Mathew Duggan describes numerous issues when moving a blog to IPv6: inability to obtain an IPv6 address, SSH failures, GitHub not supporting IPv6, Datadog installation breaking, and the need for NAT64 services.

He had to add the --edge-ip-version 6 flag to Cloudflared to keep tunnels working, and resorted to IPv4 proxies for many tools.

Conclusion

While IPv6 migration is essential as IPv4 addresses become scarce and costly, many infrastructures, ISPs, and development tools are not yet ready, making the transition a significant operational challenge that requires careful planning, tooling updates, and sometimes interim solutions like NAT64 or IPv4 proxies.