T-Mobile Deploys Largest IPv6-Only Mobile Network in the US
T-Mobile operates the largest IPv6-only mobile network in the US, using a technology called 464XLAT to maintain compatibility with IPv4-only services. This post covers the specifics of their deployment, what it means for IPv4 demand, and when renting IPv4 still makes sense.
T-Mobile’s IPv6-Only Deployment by the Numbers
T-Mobile’s IPv6 strategy is backed by concrete data:
- 10 million IPv6-only clients on the network as of 2018
- 8 million unique IPv6 subscribers within the first 8 months of deployment
- Over 50% of traffic from IPv6-enabled devices is end-to-end IPv6—no translation needed
- 27% of all traffic on IPv6-enabled phones used native IPv6 in early deployments
T-Mobile launched 464XLAT as the default for Android 4.3+ and iOS 10.3+ devices, starting with 8 Android phone models in 2013.
How 464XLAT Works
464XLAT (RFC 6877) solves a problem that pure NAT64 couldn’t: applications like Skype and WhatsApp that embed IPv4 addresses in their protocols failed on IPv6-only networks.
The solution has two parts:
- NAT64 + DNS64 on the network translates IPv6 requests to IPv4 destinations
- CLAT (Customer-side translator) on the device provides a local IPv4 address so legacy apps work unmodified
The device runs IPv6-only to the network; the CLAT handles IPv4-only apps locally. This eliminates the need for per-subscriber IPv4 addresses on the carrier network.
Why IPv4 Still Matters
T-Mobile’s IPv6-only deployment reduces CGNAT requirements and lowers costs. But IPv4 doesn’t disappear:
- Peering points often require IPv4 connectivity
- Enterprise services and VPNs may need IPv4
- IPv4-only content still exists, though the CLAT handles it for subscribers
- Backend infrastructure may use IPv4 for legacy systems
What This Means for IPv4 Demand
Carrier IPv6 deployment is uneven across the industry. T-Mobile led the way, but other operators have followed at different speeds:
- Verizon Wireless was at 65% IPv6 deployment as of 2015, ahead of T-Mobile at the time
- AT&T was at 38% IPv6 deployment in the same period
- Many regional and international carriers still rely heavily on IPv4 or CGNAT
Even where IPv6-only deployment exists, IPv4 remains necessary for peering, enterprise services, and legacy systems.
Lessons for Other Operators
T-Mobile’s deployment offers a blueprint:
- Use 464XLAT, not pure NAT64. The CLAT component is essential for application compatibility.
- Target new device activations. Roll out IPv6-only for new devices while legacy devices continue on dual-stack or IPv4.
- Measure the split. Track how much traffic goes end-to-end IPv6 vs. through translation.
- Reduce CGNAT dependency. Less IPv4 per subscriber means lower CGNAT infrastructure costs.
When to Rent or Lease IPv4
If your organization is affected by carrier IPv6 changes:
- Rent IPv4 for short-term projects, testing, or migration. Our how to rent IPv4 guide covers flexible options.
- Lease IPv4 for medium-term capacity where you need more predictability.
- Buy IPv4 if you need long-term control.
Carrier IPv6 deployment doesn’t eliminate IPv4 demand—it changes where the demand sits. Infrastructure, peering, and enterprise services still need IPv4, even when subscriber traffic shifts to IPv6.