Meta's IPv6-Only Data Centers: Impact on IPv4 Supply and Demand
Meta has transitioned its data center infrastructure from dual-stack to IPv6-only at scale. This post covers the specifics of their approach, what it means for the IPv4 market, and when selling makes sense for holders.
Meta’s IPv6-Only Infrastructure by the Numbers
Meta’s engineering team has shared concrete data on their IPv6 transition:
- 99% of internal traffic is IPv6. All services and applications inside Meta’s data centers communicate over IPv6.
- Half of their clusters are IPv6-only. New data center clusters launch without routable IPv4 addresses for servers.
- Load balancers handle IPv4 at the edge. Meta’s software load balancers (Layer 4 and Layer 7) accept IPv4 requests from external users and proxy them to IPv6-only backend servers.
The engineering work involved custom solutions: tunneling IPv4 packets inside IPv6 to reach backend servers, and using link-local IPv4 addresses for direct server return. Meta open-sourced parts of this work (gnlpy, a Python netlink library) to enable IPVS forwarding across IP versions.
Why IPv4 Still Matters
Meta’s internal infrastructure may be IPv6-only, but external reality differs. According to Meta’s data, only about 15% of Facebook users globally have IPv6 support. The other 85% connect via IPv4.
This gap explains why big tech can run IPv6-only internally while IPv4 demand persists externally. Meta’s approach does not eliminate IPv4—it relocates it to the edge and reduces how much routable IPv4 they need per server.
What This Means for IPv4 Markets
Reduced demand from hyperscalers. Meta’s model shows that large networks can run with far less routable IPv4 per server. As other hyperscalers (Google, Amazon, Microsoft) adopt similar architectures, their direct IPv4 demand for new capacity decreases.
Supply opportunities. Organizations that follow Meta’s path may free up IPv4 blocks they previously held for internal use. That creates supply for the secondary market.
Edge IPv4 remains critical. Even with IPv6-only data centers, edge infrastructure (load balancers, CDN nodes, DNS resolvers) still needs IPv4 to serve the majority of internet users who lack IPv6. So IPv4 demand shifts from “everywhere” to “edge.”
Selling still makes sense. If you hold IPv4 that you no longer need—because of internal IPv6 migration or other reasons—selling can monetize it. Our how to sell IPv4 guide walks through the process, RIR transfer, and what to expect.
Lessons from Meta’s Approach
Meta’s transition offers a blueprint for large organizations:
- Dual-stack first. They started by adding IPv6 to existing IPv4 infrastructure.
- New clusters IPv6-only. New builds launched without IPv4, forcing application and service updates.
- Bridge at the edge. Load balancers handle the IPv4-to-IPv6 translation, keeping the data center clean.
- Open-source the tooling. Meta published the software that makes mixed-version tunneling work.
This phased approach avoids a hard cutover. Legacy systems migrate gradually while new infrastructure starts IPv6-native.
What to Do Next
If Meta’s transition has you reconsidering your IPv4 holdings:
- Audit your usage. How much IPv4 do you actively announce? How much sits unused or lightly used?
- Assess IPv6 readiness. Can your applications run dual-stack or IPv6-only with edge translation?
- Consider selling surplus. If you have blocks you no longer need, selling via an RIR transfer monetizes them before the market shifts further.
Our how to sell IPv4 guide covers valuation, finding buyers, and the RIR transfer process.