In the past few weeks, we've been busy deploying a new version of the RIPE Atlas infrastructure. These changes bring more measurements to you, and also pave the way towards "user defined measurements".
As part of our effort to make an evolution plan for the RIPE Test Traffic Measurement service, we conducted a survey among TTM hosts. Find below the results and suggested next steps.
The RIPE NCC operates various data intensive services. As part of our DNS operations we have been operating K-root since 1997. A key to the stable operation of this service is a solid understanding of the traffic it responds to and how it evolves over time. With the success and growth of the Internet, traffic to the DNS root servers has increased and K-root produces terabytes of raw packet capture (PCAP) files every month. We were looking for a scalable and fast approach to analyse this data. In this article I will explain how we use Apache Hadoop and why we open-sourced our PCAP implementation for it.
This article provides you with a number of step by step examples on how to use the recently released prototype geolocation service in the RIPE Database.
The RIPE NCC is pleased to announce a new Geolocation prototype service for storing geolocation data in the RIPE Database. This article outlines the methodology applied in this prototype.
This article providers a summary of the RIPEstat demo session held on Tuesday, 4 October 2011. The focus of this demo was the mobile version of RIPEstat. Information about the next demo can be found at the end of the article.
This is a follow-up to the recently published article "Routing 2011" which focused on IPv4. In this new article Geoff is looking at the IPv6 routing table.
This weekend the NANOG mailing list was abuzz about an F-root IPv6 route leak, that resulted in the F-root DNS server instance located in Bejing, China, being queried from outside of China. This normally doesn't happen, as this instance is advertised with the BGP attribute NO_EXPORT, which means it should not be visible outside of immediate neighbor Autonomous Systems (ASes). We looked at the DNSMON data about this event, and found that 5 out of 29 IPv6-enabled DNSMON monitors saw the Bejing F-root instance. We also found there was an earlier leak on 29-30 September.
As part of the user interface to the RIPE Atlas network, users can see the first and second hops seen by certain probes. By looking for private addresses in these hops, we can learn something about how NATs are used in the Internet – in particular, that there's quite a lot of them!
The size of the global routing table has been growing at a constant pace for many years. However, over the last few months, it is not growing as fast as it used to.