As a result, the raw sample counts cannot simply be aggregated to calculate global IPv6 capability. Instead, APNIC Labs aggregates the measured IPv6 capability for each economy and then weights it according to that economy’s estimated Internet user population.

In practice, this means that large Internet populations, such as those in India, China, Indonesia, and other major economies, contribute proportionally more to the global result than smaller economies, even if the raw sample volumes on a given day might suggest otherwise. This weighting ensures that the final measurements reflect global Internet usage more accurately, rather than daily advertising distribution patterns.

At the level of individual economies, APNIC Labs’ measurements generally align with the totals published by Google and with data from Cloudflare, Akamai, Cisco, and others. This suggests that the underlying measurements are comparable and that the larger differences observed at the global level are likely due to differences between APNIC’s weighting model. This may be why we see the large variances between the two measurements.

In practice, APNIC’s measurements tend to be lower than Google’s. As a result, it’s useful to view the two data sets together, as they effectively bracket the likely range of actual IPv6 capability at any given point in time.

Is IPv6 adoption progressing as expected?

Some point to the long path toward a 50% adoption milestone as evidence of a systemic failure in IPv6. Nothing could be further from the truth. Deploying IPv6 has required substantial technical effort and significant capital investment. It’s therefore entirely expected that progress has varied across regions and economies, as individual ISPs and economies make their own decisions about how best to balance network growth, user expectations, and the practical realities of operating Internet infrastructure.

The global Internet is not a ‘command economy‘, it evolves through collaboration and cooperation within market-driven conditions. Many providers made substantial capital investments in IPv4 in earlier periods and have naturally sought to maximize the return on those investments. In doing so, they built sustainable and commercially viable IPv4-based networks within their existing footprints.

By contrast, for newer market entrants, it has often been more rational to adopt IPv6 as the primary protocol, as it can demonstrably reduce the total cost of ownership. This pattern is particularly evident in the mobile sector, most notably in large-scale IPv6 deployments such as Reliance Jio’s network in India.

Is the global Internet functioning in a ‘two‑protocol world’?

Yes, but it could be simpler.

Certainly, it would be easier logistically to run a global internet under a single protocol. However, that is not the environment we have ended up with. Instead, the Internet today operates across a mix of direct IPv4 connectivity, IPv4 mediated through Network Address Translation (NAT), either in home networks or at the carrier level via Carrier‑Grade NAT (CGNAT), and IPv6.

Managing address translation through NAT is not materially less complex than alternatives such as protocol translation, IPv4 encapsulation over IPv6, or other transition and proxy mechanisms. As a result, claims that ‘IPv4 is working fine’ often overlook the underlying reality: Modern IPv4 networks already rely on layers of operational complexity, and there is no inherently lower‑cost or simpler approach available within IPv4 alone.

From the outset, it was understood that the lack of direct interoperability between IPv4 and IPv6 would be a challenge that needed to be addressed. Early efforts explored the idea of protocols that could subsume IPv4 unchanged and enable direct connectivity across both worlds, but these approaches did not prove viable.

Instead, interoperability has emerged at higher layers, with transport protocols such as TCP, UDP, and QUIC operating independently of the underlying IP version. This model necessarily relies on some form of intermediary. This is visible in the way large content and caching providers, such as Cloudflare, are able to offer dual‑stack services regardless of whether the backend systems themselves support both protocols.

The absence of native dual‑stack capability at some services, for example, certain Git platforms or national television broadcasters, is often perceived as a major barrier to IPv6 progress. However, this may reflect pragmatic constraints, such as operational complexity, or, in the case of national broadcasters, legal and regulatory requirements around data access and geolocation, rather than resistance.

Let’s recognize the 50% milestone, even as the journey continues

Whatever one’s view on the decision to introduce a second addressing and protocol model beneath today’s Internet services, the reality is clear: IPv6 is now deployed on a global scale. Around half of the Internet users visible to Google already reach its services over IPv6. IPv6 is used every day, every hour, across developed and developing economies alike, on fixed and mobile networks, on small personal devices, and within vast data‑centre‑backed services. It is no longer experimental or marginal; it is part of the Internet’s day‑to‑day operation.

That achievement reflects the collective effort of those working to build, operate, and grow the Internet worldwide, and it is something worth recognizing and taking pride in.

The views expressed by the authors of this blog are their own and do not necessarily reflect the views of APNIC. Please note a Code of Conduct applies to this blog.