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…