This website has been available over IPv6 — the next generation Internet protocol — since May and I immediately started logging how much of the site traffic is over IPv6.
This site is available over both IPv4 and IPv6 in what is called a dual‐stack configuration. Even though a visitor may have IPv6 available to them, networking conditions and their devices may still have them connect over IPv4 instead of IPv6. The graph below doesn’t show IPv6 availability, merely the percentage of server requests that took place over IPv6 versus IPv4.
This above graph only shows the first four months worth of traffic. Right now, it looks like an average of 5,16 % of all requests to Slight Future are using IPv6. It will be interesting to keep an eye on this in the years to come as the now undeniable IPv4 address exhaustion will only lead to more and more problems. I’ll maintain a live version of the graph that automatically updates every month for anyone interested.
This website’s audience is likely of a more technical nature than you’ll find on many other websites. This may skew the graph towards IPv6, but I still look on it as one interesting measure of the total global IPv6 deployment. Apple devices is set to favor IPv6 connections starting with the their release of iOS 9 and OS X 10.11 due this month. Give it a month or three, and IPv6 traffic share could look quite different.
Are you interested in seeing the IPv6 traffic breakdown for your own website? Assuming you’re logging IP addresses — most web servers do that by default — you can use my little log counter script to find how many IPv4 and IPv6 addresses you have in your logs. It’s based on counting the number of lines containing either an IPv4 or IPv6 address so it should work with any kind of log that contains IP addresses. Filter out your own IP addresses and any local addresses from the logs before running the script. I also filter out traffic from aggressive bots (more than 500 requests from the same bot per 24 hours).