RIPE Atlas has a large enough footprint all over the world to observe various kinds of network behaviour. Recently we've been notified about a case where the IPv6 source address ::/128 appeared in some of our traceroutes. We set out to discover why this happens.
Likes on articles
About the author
I am the leader of the Research and Development team at the RIPE NCC leading a dedicated team of thinkers to support the RIPE community by providing network research, data analysis and prototype tool development and services including RIPE Atlas and RIPEstat.
Links & Social
One of the tasks of the R&D team here at the RIPE NCC is to come up with, evaluate, and execute new ideas for research topics and tools that can be of good use to the community. In this article, we're starting an experiment to expose some of these ideas to the community, in order to find interested…
RIPE Atlas is 10 years old! To help mark the occasion, alongside the virtual events we have planned over the next two weeks, we'll be posting a series of stories surrounding the development of RIPE Atlas. Check here for daily instalments!
In this article we will give some insights into the overall architecture of the RIPE Atlas network and how we manage secure communication with our probe flock.
It's possible to look at RIPE Atlas probes from the perspective of IoT - a key element of the service is the physical devices deployed all over the world. Read on to find some interesting insights from this perspective.
As RIPE Atlas is expanding, it is approaching the magical milestone of 10,000 probes. However, as our public graphs also illustrate, the expansion has slowed down recently.
This article is intended to make RIPE Atlas users aware of ethical issues that could arise when using RIPE Atlas. We do not intend to propose any new formal processes or procedures to address the relevant ethical issues, but we do want to encourage members of the RIPE Atlas community to consider th…
Twelve years ago the RIPE NCC set out to build the largest Internet measurement network ever made. Today, RIPE Atlas provides users with an unprecedented understanding of the state of the Internet in real time. In this episode, I catch up with Robert Kisteleki to talk about how RIPE Atlas developed…
When it comes to RIPE Atlas, bigger is better. Each new probe adds another vantage point, bringing the measurement platform closer to its goal of providing an unprecedented view of the state of the Internet. But expansion into new geographical locations and networks wouldn't be possible without the…
Software probes provide yet another way to help grow the RIPE Atlas network. As many new hosts opt for this alternative, getting RIPE Atlas into new places means helping people install and run the relevant software packages. Language support will be key to this, and we have a plan to provide it, bu…
This year's Internet Measurement Conference (IMC) was held in London from 1 - 3 November. In this article we highlight some of the presented work that we think is interesting and that the RIPE community might find useful.
Please find below the third part of our technical services update. This time we're focusing on our research activities and a number of tools we are developing.
In 2013 and 2015 we provided high-level reports on the status of our plans for our technical services and tools. It is time for an update. In this first article we will focus on RIPE Atlas.
We're thinking about implementing WiFi measurements in RIPE Atlas, and we want to know what you think. There are several different ways we could do this - find out more below and then take our poll to make your voice heard!
Dyn Research published an article on K-root recently. Here we would like to augment the picture with data from RIPE Atlas in order to provide a more complete picture of the effect of the K-root node in Iran.
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 …
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 p…