You are here: Home > Analyse > Internet Measurements > RIPE Atlas > Results > Analyses

Analyses and Use Cases

Below you can find a list of publications, articles and other documentation that were made possible by using RIPE Atlas as a measurement system.

  • An Update on De-bogonising 128.0.0.0/16

    (RIPE Labs, 2013-02-21) We continued RIPE Atlas measurements to see if we can still find cases where 128.0.0.0/16 is filtered out.

  • Hurricane Sandy and How the Internet Routes Around Damage

    (RIPE Labs, 2012-11-12)

    In this article we look at some of the effects Hurricane Sandy had on the Internet data plane, as we can see them in traceroutes done by RIPE Atlas.

  • Superstorm Sandy

    (RIPE Labs, 2012-10-30)

    After causing lots of damage in the Caribbean, superstorm Sandy is having a devastating effect on the US East Coast. We looked at the RIPE Atlas network to find out what effects this superstorm has on the Internet. Below are some preliminary results of what we saw.

  • Comparing TCP and UDP Response Times of DNS Root Servers

    (RIPE Labs, 2012-10-17)

    We did some measurements on the round-trip (RT) values of DNS queries for SOA (Start of Authority) records from our RIPE Atlas probes, over both UDP and TCP. We plotted the TCP/UDP ratios on graphs, and found that, as expected, for the majority of the measurements, it is around 2. However, we also observed other values for some servers (including K-root). Upon investigation, we found that the K-root servers were configured to allow at most 10 concurrent TCP connections. This caused several much bigger RT values than on other root servers. When we changed the configuration to allow for 100 concurrent TCP connections, K-root showed ratios similar to the other root servers.

  • A Case Study of AAAA Filtering

    (RIPE Labs, 2012-10-11)

    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.

  • Using RIPE Atlas: A DENIC Case Study

    (RIPE Labs, 2012-09-25)

    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.

  • A Case Study of IPv6 /48 Filtering

    (RIPE Labs, 2012-07-26)

    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.

  • A Use Case for IPv6 Reachability Testing with RIPE Atlas

    (RIPE Labs, 2012-07-03)

    RIPE Atlas was used to perform IPv6 reachability testing before and during the World IPv6 Launch. One success story and the usage statistics lead us to the conclusion that this feature needs to remain available even after the "launch" is over.

  • RIPE Atlas & Anycast Instance Switches

    (RIPE Labs, 2011-12-22)

    RIPE Atlas can now test packet flows from more than 1000 vantage points on the Internet. We took a quick look at anycast traffic to DNS root name servers. There is a lot of interesting signal in this data.

  • 128.0.0.0/16 As Seen by RIPE Atlas

    Atlas traceroutes to 128.0.0.1 - Last Working Hop

    The Curious Case of 128.0/16

    (RIPE Labs, 2011-12)

    The prefix 128.0/16 is filtered in Juniper devices up to and including JUNOS software version 11.1. We looked at three ways to get a rough estimate on how much filtering of 128.0/16 is going on on the Internet.

  • DNS Measurements with RIPE Atlas Data

    (RIPE Labs, 2011-12-05)

    In this article we describe how we use RIPE Atlas to determine which instance of a name server a probe uses.

We develop RIPE Atlas in cooperation with the Internet community, and we want to know what you think. Find out how to get in touch.