For World IPv6 Launch the RIPE NCC measured 60 selected participants from over 50 vantage points all over the world. In this article we present the DNS and HTTP measurement results from a 4-day period as a 3 minute movie. We will discuss general observations and look at some specific events.
On Monday, 13 August, we'll decommission the deprecated RIPEstat data calls.
While developing RIPE Atlas, we wish to keep the RIPE community involved and informed. We are maintaining a roadmap of the features we are working on, and with this update we are asking for feedback so that we can use it as guidance for making further plans.
As part of our Data Repository, the RIPE NCC has released a new dataset. This dataset contains DNS lookups (A+AAAA), ping/ping6, traceroute/traceroute6 and HTTP fetches (IPv4/IPv6) from 53 vantage points (TTM, CAIDA Ark and others) to 60 websites involved in World IPv6 Launch. The data covers the period from 2012-05-19T00:00 to 2012-06-18T00:00 (UTC).
In this article I look at four different IPv6 destinations in different BGP set-ups and how these are seen by RIPE Atlas probes. This reveals some differences in reachability for the different networks, likely due to BGP route filtering. We see roughly 1% out of ~500 RIPE Atlas probes that can't reach a destination in an IPv6 /48 prefix (without a covering shorter prefix) out of IPv6 PA space, likely due to filtering.
The fifth RIPEstat demo of 2012 gives an overview of the news since the previous episode at the RIPE 64 Meeting in Ljubljana, and announces changes that will happen between now and the next RIPE Meeting, RIPE 65, in Amsterdam.
Now that World IPv6 Launch is weeks behind us it's interesting to look at what long-lasting effects it had.
An alternative way of looking at the prefix size distribution in IPv4 and IPv6 blocks is now available in RIPEstat as an interactive widget. Tabular visualisation and cumulative percentage representation can be used for filtering based on minimum allocation size or for general research about the usage of address space.
We've enabled RIPE NCC members to do IPv6-traceroutes from all RIPE Atlas probes to IPv6 destinations. Until now they could get the raw analysis results (text/JSON representations of traceroute results) for analysis. In this article we present a first experimental analysis and visualisation of the traceroute results.