I noticed the 50% figure on Google's IPv6 stats page https://www.google.com/intl/en/ipv6/statistics.html on 4/16/2026, flagged on Hacker News https://news.ycombinator.com/item?id=47777894. A milestone worth pausing on, even if the headline buries the lead: it took roughly 20 years from IPv6's formal definition (RFC 2460, 1998) to get halfway there.
The culprit is obvious in retrospect — NAT gave IPv4 a decade-long second life and removed any burning platform. Why pay migration cost when carrier-grade NAT works fine?
From a firmware perspective, the story is actually a bright spot. RFC 5970 https://www.rfc-editor.org/rfc/rfc5970.txt standardized network boot over IPv6 (DHCPv6/PXE) in 2010, and the firmware stack moved quickly. I was part of the team that implemented dual-stack IPv4/IPv6 network boot support in EDK2 https://github.com/tianocore/edk2 — the open-source UEFI reference firmware — had it certified at the UNH Interoperability Lab https://www.iol.unh.edu/, and codified in the UEFI specification. That code has been fully deployed since the RFC landed and ships today in the host firmware of most PCs, servers, and devices like the NVIDIA Jetson. The iPXE project https://ipxe.org/ is the other prominent host-side implementation and likewise supports RFC 5970. The IPv6 TFTP/PXE boot foundation was then leveraged for HTTP boot, which is the modern evolution now widely used for network-based firmware provisioning. I journaled bit of this in places like https://github.com/vincentjzimmer/Documents/blob/master/UEFI-Recovery-Options-002-1.pdf, https://www.intel.com/content/dam/www/public/us/en/documents/research/2011-vol15-iss-1-intel-technology-journal.pdf, and https://uefi.org/sites/default/files/resources/A_Tale_of_Two_Standards_0.pdf.
So firmware did its job — standards written through the IETF and UEFI Forum, code certified, silicon shipping, HTTP boot built on top. The 50% adoption story is really about everything above the firmware layer: ISP rollout, enterprise network operations, and the long tail of IPv4 infrastructure that NAT kept alive just long enough to delay the transition by a decade.
That's the part that still surprises me. When the firmware stack is ahead of the network, you know diffusion is the bottleneck, not implementation.
