As [reported in an ISOC report last year](), IPv6 adoption is now solidly in the "early majority phase" of the [technology adoption life cycle]() by many metrics (well past "innovators" and "early adopters"), with progress beyond that in some areas. Akamai continues to see solid growth in IPv6, including significant traffic peaks during large events, and we continue to find cases where IPv6 outperforms IPv4. Driven by the growth of Internet end-users outpacing the supply of IPv4 addresses needed to number their devices, and a desire to plan for a future IPv6-based Internet, many networks around the globe are shifting to provisioning their end-users with IPv6 connectivity. Currently, IPv6 deployment in 7 of the top ten global economies has reached a point where Akamai typically sees over 18% of requests to IPv6-enabled sites using IPv6, with India (56%), U.S. (46%), Germany (35%), Japan (28%), and Brazil (27%) being well beyond this. We have come a long ways [since World IPv6 Launch when we reported]() seeing only around 1% of U.S. end-users using IPv6. With around 80% of U.S. mobile end-users accessing IPv6-enabled Akamai sites over IPv6 (and 90% from some carriers including Reliance Jio in India), the adoption of IPv6 in the mobile space is well through the "late majority" phase. Over the past year IPv6 has been enabled on many of the largest online streaming events on the Internet, as delivered by Akamai, such as numerous major sporting events including the[ VIVO IPL]() and some major broadcasters of the Olympics. During these we've often seen between roughly a quarter (¼) and two-thirds (⅔) of the global event traffic delivered over IPv6, depending on the audience distribution. We often see a considerably higher average throughput to IPv6 end-users than to IPv4 end-users during dual-stacked events (although some of this may be due to sample bias). We've even seen multiple recent cases where massive IPv4-only events caused problems for CGNAT middle-boxes but IPv6 traffic continued to flow unimpeded. For dual-stacked hostnames we typically see higher average estimated throughput over IPv6 than over IPv4. Some of this may be due to IPv6-connected users being correlated with better connectivity, but over half of dual-stacked hostnames (weighted by daily bytes delivered) have IPv6 estimated throughput at least 50% faster than IPv4, and 90% of these hostnames have the IPv6 estimated throughput at least 10% faster than IPv4. Individual sites and network providers will vary (with IPv6 performing worse than IPv4 in some cases). However the overall trend aligns with past results from [LinkedIn](), [Facebook](), [Akamai](), and others that show IPv6 as delivering significantly better performance than IPv4, especially in some mobile networks. ## IPv6 Content Availability on Akamai Aggregate IPv6 traffic levels are a function of whether users have IPv6 connectivity through their network/ISP, whether content is available via IPv6 ("dual-stack IPv6+IPv4"), and whether client devices support IPv6. For the past two years, Akamai has had IPv6 enabled by default for customers integrating new properties onto our platform (although we still need to support customers opting out, such as because their backend origin or log processing infrastructure has problems handling IPv6 addresses). Over this time, we've seen significant growth in the percentage of dual-stacked customer hostnames on our platform, although there is still quite a ways to go. [![IPv6-1.png](https://blogs.akamai.com/assets_c/2018/06/IPv6-1-thumb-500xauto-7194.png)]() _Portion of hosts dual-stacked on Akamai by request volume_ Over these two years, we have seen a doubling in the number of dual-stacked hostnames across a range of categories, including for sites with over 100 million requests-per-day that include the websites of many household-name brands. Most of these categories are also now in the "early majority" adoption range. (Recent overall growth has been slower and more complicated at the top end of the spectrum, but that also has had a higher level of IPv6 adoption.) We continue to explore ways of safely accelerating the transition of customer content and sites to IPv6+IPv4 dual-stack, and customers are encouraged to dual-stack existing and new content. Many customers see IPv6 as a strategic imperative and have been working hard to dual-stack content. For example, NBC Universal as a leading broadcaster sees the needs-based and value-based benefits of IPv6 and continues to be a leader in making dual-stacking part of their standard-operating-procedure. [![IPv6-2.png](https://blogs.akamai.com/assets_c/2018/06/IPv6-2-thumb-500xauto-7197.png)]() _Distribution of "IPv6 Usage" percentages (IPv6 requests / total requests) across request-weighted hostnames, showing the wide distribution of potential "IPv6 global user adoption" numbers for different types of content._ Customers sometimes ask what percentage of requests to expect over IPv6, but there is no one single number. The "IPv6 usage" percentage can vary widely based on end-user population. As a result, global and country-level IPv6 measurements can be sensitive to the mix of content being measured and the associated end-user bases. Looking at distribution of the "IPv6 usage" percentage across a 24-hour snapshot of traffic against around 10,000 dual-stacked customer hostnames each serving over 250k requests/day (weighted by total requests per-hostname), we see that most hostnames have IPv6 usage around or below 45%, but that over three-quarters of (weighted) dual-stacked hostnames have IPv6 usage over 15%. (We've sometimes seen some large events with a heavy mobile user population in India reach over 65%, however.) Some of the modes consistent of classes of traffic: for example, the mode around 45% IPv6 usage contains lots of U.S.-centric streaming media content. Those near 0% often have end-users in countries with little-to-no IPv6. use a client application lacking IPv6 support (such as some desktop apps and consumer electronics), or are web-service calls from cloud services lacking configured IPv6. Those with very high IPv6 usage are often from mobile apps in countries with high IPv6 mobile adoption. End-User IPv6 Adoption Drivers and Ramifications Akamai continues to see growth in IPv6 adoption in many networks including mobile and broadband ISPs. The IPv6 growth we see in countries is a function of the IPv6 adoption within the networks deployed in that country. Per [some recent analysis by APNIC's Geoff Huston](), there's no one clear factor yet as to which networks are and aren't deploying IPv6 and to what degree. However, [freely available IPv4 addresses were exhausted by all but one of the RIRs prior to September 2015 (with Africa's AFRINIC projected to run out in less than a year)](). IPv4 address pricing on secondary auction markets [has also been increasing](), with many blocks selling in the range of $15-$16 per-address in 2018, and steadily increasing prices. Between the cost of acquiring IPv4 addresses and the complexity of running a dual-stack network with both IPv6 and IPv4 as equivalents, it is becoming increasingly attractive for network operators to run "IPv4-as-a-service" (IPv4aaS) over IPv6. Technologies such as NAT64/464XLAT, lw4o6, MAP-T, MAP-E, DS-lite, and even HTTP proxies and VPNs can all leverage an IPv6-only network with IPv4aaS being used to provide end-users access to IPv4-only resources. A crowd-sourced spreadsheet shows [which technologies are being]() used by various ISPs. Networks who have control over their end-user devices, such as mobile carriers and streaming set-top boxes (such as the Xfinity X1) can readily leverage IPv6-only deployment for those devices, while using IPv4aaS for any residual IPv4 traffic. One ramification of IPv4aaS and common to all of the transition technologies is that IPv4 traffic relies on additional infrastructure with varying scaling and resource availability characteristics (such as limited NAT capacity). We've observed cases where large online events or software bugs have caused problems with NAT infrastructure relied on for IPv4 but where IPv6 has continued to work just fine. This is a compelling reason to dual-stack content: even if your content isn't responsible for triggering such a problem, providing your end-users with IPv6 as an option allows them to bypass these issues and achieve higher availability and/or performance in the face. Dual-stacking large events can also help reduce the chances of exhausting NAT resources within ISPs and causing problems for others. Another ramification of IPv4aaS is that while IPv6 may break out onto the Internet locally (such as in cities scattered around a country), we have started to see cases where IPv4 traffic is all passed through more centrally located CGNATs or other gateways. As such, a CDN is able to get deploy closer to users over IPv6 than over IPv4 (without deploying behind the CGNAT), providing better performance and scale. ## Growth in Client Addresses In a single sample day in March 2018, we saw HTTP(S) requests from around 1.7 billion unique IPv6 client addresses (and around 10 billion native IPv6 client addresses in a March 2018 sample week). As IPv6 clients may change their addresses periodically (such as due to privacy addressing), this likely significantly over-estimates the number of unique IPv6 end-points. During the sample day in March 2018 we saw 576 million active /64 prefixes covering these IPv6 client addresses, with 1.43 billion of these prefixes in the March 2018 sample week. Compared to IPv4, we actually see more active /64 prefixes from HTTP(S) clients in a week than we see active IPv4 addresses in a year. This continues to evidence the freedom-in-addressing that IPv6 offers. Most of these have gone up around an order of magnitude over the past four years --- in March 2014 we saw 157 million /64 prefixes in a week from clients vs. 1.43 billion this March, with similar increases across the other metrics. Also for comparison, we see more unique active IPv6 client addresses in a week than the total number of possible IPv4 addresses. [![IPv6-3.png](https://blogs.akamai.com/assets_c/2018/06/IPv6-3-thumb-500xauto-7200.png)]() _Increase in active IPv6 client addresses and unique /64 prefixes making HTTP(S) requests to Akamai during a week, over the past four years (excluding Teredo and 6to4)._ ## End-User Adoption by Country Akamai's measurements of end-user IPv6 adoption look at a few hundred billion HTTP(S) requests over a 24-hour period (a weekday such as a Wednesday for these measurements) across a mixture of hostnames and look at the percentage of requests over IPv6 relative to total requests. Depending on the geographic (and device) mix of traffic, we often see global averages for dual-stacked hostnames between 17% and 31% IPv6 usage, with some being well outside of this range on either end. Even within a country, the IPv6 usage will vary based on the mix of mobile, broadband, and business traffic, as well as the targeted devices. As such, we'll see fluctuations in the country-level average as the mix of dual-stacked content we deliver changes over time or as we look at different sample sets of dual-stacked hostnames. However, the trends we see line up similarly to those reported by [Facebook](), [APNIC](), [Google](), and others, each of which reports by a different sample set. We continue to see upward growth over the past five years in many countries. While some countries such as the U.S., Japan, Belgium, Germany, Malaysia, and a few others had major networks start their IPv6 roll-outs five years ago with steady growth over that time, India, Taiwan, and Mexico and other countries had networks start deploying IPv6 at scale more recently. As mentioned above, the U.S., India, and Belgium all see around half of traffic to dual-stack sites delivered over IPv6 depending on the mixture of traffic. [![IPv6-4.png](https://blogs.akamai.com/assets_c/2018/06/IPv6-4-thumb-autox585-7203.png)]() _IPv6 usage/preference for select dual-stack hostnames on Akamai (measured on weekdays, which are typically lower than weekends)_ ## End-User Adoption by Network Many of the largest networks in the world (in terms of subscriber base) have been aggressively deploying IPv6 over the past few years, with a majority of requests using IPv6 to reach dual-stack sites in these networks. For example, across the top-4 U.S. mobile carriers we now see IPv6 usage rates over 80% (and this continues to steadily increase). Reliance Jio, the largest mobile carrier in India, has IPv6 usage over 90% based on our observations. Some of the largest fixed-line networks in the world (Comcast, AT&T, Deutsche Telekom, British Sky Broadcasting, Rogers, KDDI, and others) all have IPv6 usage around or well above 50% in our observations, with many others on a path to reach and cross that soon. [![IPv6-5.png](https://blogs.akamai.com/assets_c/2018/06/IPv6-5-thumb-autox762-7206.png)]() _IPv6 usage/preference for select dual-stack hostnames on Akamai (measured on weekdays, which are typically lower than weekends)_ ## Residual IPv4 In addition to looking at IPv6 adoption, we've also started to look at "residual IPv4". By looking at areas with the highest levels of IPv4 traffic on dual-stack hostnames, we can identify areas that will have the biggest impact on global, country, or network IPv6 usage metrics. These tend to fall into the category of areas where there is already high IPv6 usage (but still significant opportunity for growth) and those areas with very limited IPv6 deployment. ### Residual IPv4 by Country For example, we have seen that the following countries have high both significant IPv6 deployment but also high residual IPv4: U.S., U.K, Japan, Germany, India, France, Canada, Brazil, Australia, Mexico, Netherlands, and Sweden. On the other hand, we've seen that the following countries have very limited (less than 3%) IPv6 usage -- which means that most of their traffic is residual IPv4 traffic: * Russia * China * Italy * Spain * Indonesia * Turkey * South Korea For China in-particular, while there [have been and are plans]() to deploy IPv6 broadly, we have not yet seen much IPv6 traffic materialize against dual-stacked sites outside of China from networks other than CERNET2. As seen in other countries, IPv6 deployment has the potential to ramp up quickly, especially in countries with a smaller number of ISPs. ### Residual IPv4 by Network On the network side, more IPv6 movement will be needed in the longer tail (such as in smaller ISPs and corporate networks) to keep global IPv6 adoption moving upwards. Smaller networks (with correspondingly less aggregate residual IPv4) are less likely for any given network to have deployed IPv6 than the larger networks. As of May 2018, we have observed that the top 60 networks constitute approximately 50% of the residual IPv4 traffic, with 58% of these having IPv6 usage rates over 2%. Looking at the top 387 networks that constitute 80% of residual IPv4 traffic, this drops to 31% having IPv6 deployment over 2%. The top 90% of residual IPv4 traffic comes from around 1300 networks and only 17% of them have IPv6 deployments over 2%. On an optimistic note, there are many network partners where Akamai has been able to obtain functioning IPv6 connectivity to our servers but where the network partner has not yet rolled out IPv6 to their end-users. As of May 2018, we now have IPv6 live on Akamai servers in 114 countries, over 700 cities, and over 850 network providers. We also have seen continual growth in the number of origin ASNs we observe active IPv6 HTTP(S) clients arriving from, being 6,887 in March 2018 as compared to 3,842 in March 2014. ### Residual IPv4 by Client Devices On the device/client side, all recent major mobile and desktop operating systems and web browsers support and use IPv6, but they are not the only clients. We see very high levels of residual IPv4 traffic from some popular set-top boxes and gaming consoles that do not yet support IPv6. Additionally, some portion of custom applications (such as download clients, games, and mobile apps) do not use IPv6 and thus can also result in residual IPv4 traffic. Consumer electronics manufacturers and app authors are strongly encouraged to support IPv6 in their client software. Using a scheme such as [RFC8305 "Happy Eyeballs v2"]() (as implemented in operating systems such as recent versions of macOS and iOS) can allow clients to also improve their reliability and performance to continue functioning even if either of IPv4 or IPv6 breaks but the other continues to work. ## Conclusion While we still have a ways to go before residual users of IPv4 are truly "laggards", six years into World IPv6 Launch we are at a stage where the use of IPv6 should be considered the norm and certainly included in default planning for any new projects. For content providers, ISPs, and device manufacturers who have not yet enabled IPv6 and didn't want to be early adopters, now is as good a time as any to take the plunge. Doing so may have performance and reliability benefits in addition to preparing you for the future. For more measurements on IPv6 adoption, see: * [Akamai State of the Internet: daily measurements of IPv6 adoption by network and country]() (out of date as of May 2018, but will be fixed shortly) * My blog posts from World IPv6 Launch anniversaries in [2016](), [2015](),[ 2014](),[ 2013](), and[ 2012]() as well as a post on [IPv6 talks at the Akamai Edge conference](), and [on preparing for IPv6-only mobile networks (from 2016)]() * [World IPv6 Launch measurements]() * [Cisco's 6lab]() * [Eric Vyncke's report on IPv6-enabled Web sites per-country]() Thank you to Dave Plonka, Moritz Steiner, and others for providing some of the details for this blog post. While precautions have been taken in the preparation of this document, Akamai Technologies, Inc. assumes no responsibility for errors, omissions, or for damages resulting from the use of the information herein. The information herein is subject to change without notice. Akamai and the Akamai wave logo are registered trademarks or service marks in the United States (Reg. U.S. Pat. & Tm. Off). Non-Akamai product and corporate names are trademarks or registered trademarks of other companies; they are used only for identification purposes and to the owner's benefit, without intent to infringe. Published June 5, 2018. ![](http://feeds.feedburner.com/~r/TheAkamaiBlog/~4/PLm48mIF4yg)