RIPE NCC developers and researchers present their own findings about a range of topics using RIPE Atlas data, from the effect of hurricanes on the Internet to examining IPv6 /48 filtering.
After implementing the "pingable:" and "ping-hdl:" attributes in the RIPE Database five years ago, we check how the new attributes have been adopted and how reachable the pingable addresses registered in the RIPE Database are when pinged from RIPE Atlas.
We had a sense that with a limited amount of extra load on the system, we could dramatically increase the number of router IPs seen on a given day in RIPE Atlas - and that means measuring more of the Internet.
We use RIPE Atlas to look at how large-scale disruptions in the Internet's core infrastructure affect end-to-end connectivity on the Internet.
After expanding the K-root anycast cluster with 17 hosted servers in 15 new cities over the previous few months, we look at RIPE Atlas to see what impact this had on performance on both global and regional scales.
After Dyn published an article about K-root, we take a deeper look into the effect that placing a new K-root node in Iran had on the surrounding region.
We collaborated with France-IX to collect data plane and control plan data using RIPE Atlas and the Routing Information Service (RIS).
A year after we started announcing a few prefixes longer than a /24, we revisit our investigation of how visible these prefixes are according to RIPE Atlas and the Routing Information Service (RIS).
We investigate an outage at AMS-IX using the RIPE Atlas Seismograph and DNSMON tools.
We look at 10 countries in South East Europe and see how we can use RIPE Atlas to get a sense of routing and the interconnectedness of networks in that region.
We monitor a large-scale power outage as seen by RIPE Atlas and create an animated map showing probes going down and coming back online.
We work with various Internet Exchange Points (IXPs) to see how RIPE Atlas active measurements can provide insight into how they are keeping local traffic local.
We monitor how cyclone Pam is battering the South Pacific and how this affects Vanuatu.
We provide some insight into what happened with Facebook's connectivity to the rest of the Internet when the social media site went offline.
We request a small block of address space from the reserved /10 to test the usability/routability of prefixes longer than a /24.
We look at some interesting details of the Time Warner cable outage using RIS and RIPE Atlas.
Engineers from the Wikimedia Foundation and the RIPE NCC collaborate to measure the latency of Wikimedia sites, identifying ways to decrease latency and improve performance for users around the world.
We investigate the potential hijacking of Google's 188.8.131.52 DNS resolver in Turkey and create a timeline of these events.
We use RIPE Atlas measurements to see whether we can still find cases where 184.108.40.206/16 is filtered out.
We look at some of the effects Hurricane Sandy had on the Internet data plane, as we see them in traceroutes done by RIPE Atlas.
We used the RIPE Atlas network to find out what effects Superstorm Sandy had on the Internet.
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 look at four different IPv6 destinations in different BGP set-ups and how these are seen by RIPE Atlas probes, revealing some differences in reachability for the different networks, likely due to BGP route filtering.
RIPE Atlas was used to perform IPv6 reachability testing before and during the World IPv6 Launch. We include one success story and the usage statistics.
We took a quick look at anycast traffic to DNS root name servers. There is a lot of interesting signal in this data.
The prefix 128.0/16 is filtered in Juniper devices up to and including JUNOS software version 11.1. We explored three different ways to get a rough estimate on how much filtering of 128.0/16 is going on on the Internet.
We describe how we use RIPE Atlas to determine which instance of a name server a probe uses.
At a 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.