During the recent RIPE 65 meeting, some attendees experienced problems with the wireless network. Together with these attendees we investigated the problem. Find a detailed report below.
We observed an increase in the number of new LIRs in the RIPE NCC service region. Many of these new LIRs show 1-star IPv6 RIPEness.
At the recent RIPE Meeting, the question was raised whether Internet users would see significant filtering of AAAA DNS queries or replies. We used RIPE Atlas measurements to provide an answer to this question.
The weekend after the recent RIPE 65 Meeting in Amsterdam, we experienced a network outage that affected a number of services. Please find below a detailed report and analysis.
While developing RIPE Atlas, we are maintaining and publishing a roadmap to keep the RIPE community involved and informed of the features we are working on. This update was presented last week at the RIPE 65 meting. We are curious to get your feedback.
IPv6 RIPEness helped in creating awareness and got people into action with regards to their first steps towards deploying IPv6 in the RIPE NCC service region. Up until now IPv6 RIPEness didn't measure actual IPv6 deployment. In this article we propose a measure (a "5th star"), which attempts to measure actual IPv6 deployment at the edge.
In response to a huge amount of demand, the RIPE NCC has conducted another survey on the level of IPv6 support for various vendor's Customer Premises Equipment (CPE). The questions in the 2012 focused around the most common access technologies. The results have been published using a simple colour coded matrix, listing which features are present, on the roadmap or not available. We've also developed a new interactive user interface so you're now able to filter the results and compare different models. This article will highlight some of the 2012 findings as well as some comparison to previous editions of the survey.
When we experienced an occasional operational issue with the data returned by one of our name servers, we wanted to verify DNS responses from a number of widely distributed measurement points (vantage points). RIPE Atlas was just the right service to provide us with the necessary raw data.
It is possible to measure how well we are doing with DNSSEC? How many of the DNS resolvers will now perform DNSSEC validation of a domain name? How many of the Internet's user population are using these DNSSEC-validating resolvers? In this article we will explore a way to answer these questions, and provide some measures that describe which countries are well advanced in their use of DNSSEC deployment, and which are falling behind.
The upcoming RIPE meeting in Amsterdam will give plenty of opportunity for "community building" - interaction between the developers of various tools like RIPE Atlas and RIPEstat, and the users of these services. If you want to talk about TTM, DNSMON, K-root, RIPE Atlas Anchors, IPv6 Measurements... we are looking forward to meeting you there!