When the IPv6 Data Changes, so Should Your Opinion

Sky UK recently completed their rollout of IPv6. The uptake statistics are quite remarkable. If you think that people don’t have IPv6-capable devices, or that their home routers can’t handle IPv6…you really need to look at the data, and re-think your opinion.

APNIC has a long-running program collecting data on IPv6 client capability/preference by country and ASN. This graph shows the data for Great Britain:


So a year ago we had ~5% takeup, and now it’s 20-25%. And here’s the reason for that big jump from April this year - this graph shows the data for AS5607, BSkyB:


So > 80% of clients on the BSkyB network are IPv6-capable.

If someone tells you that people don’t have IPv6-capable devices, or routers: the data does not back that up. A few years ago that may have been true, but people don’t access the Internet using Windows XP desktops anymore: They use iOS and Android mobile devices. These have short replacement lifecycles, so people tend to be running newer versions. These are capable of using IPv6, and will prefer it if it is available.

The other related trend is that people have more wireless devices at home, and they have faster connections to the Internet than they used to. When people had 1 or 2 devices using a 10Mbps ADSL link, their local wireless performance didn’t matter much.

Now they have > 10 devices, and > 100Mbps links. This created demand to upgrade home routers. ISPs offer better devices for ‘free’, and people are buying their own. These newer devices support IPv6. As ISPs start enabling IPv6 at their edge, everything else is in place.

Why does it matter?

You could still look at the overall uptake (global peak ~13% of Google users) and say “meh, doesn’t matter to me.”

Or you could look at the country and user-specific stats - e.g. > 50% of mobile users in the US use IPv6. If you’re designing an application that targets those user bases, it makes sense to use IPv6 where possible, and translate to IPv4 at the edge. That way you’ll be doing less protocol translation than going the other way.

Of course, if your target user base is on-site users of Oracle ERP systems…well, who cares? Enterprise is lagging further behind in technology.