Anycast is used by most of the DNS root-servers and other services like Cloudflare. It provides localisation and scaling benefits to clients using the anycasted service. An anycast service uses one IP for several instances of the same service. The routing system is then responsible for directing a client to the closest instance of the service. In theory, a client should always reach the closest instance, but it turns out that this is not always the case. At the DACS group of the University of Twente, we analysed the anycast infrastructure of K-root and tried to find how many clients reached the closest instance.
Learn more about the RIPE Atlas active measurements network.
You can also find a collection of use cases, reviews and other articles written by RIPE Atlas users.
In an effort to increase the growth rate of connected RIPE Atlas probes and achieve better coverage across the globe, our Measurements Community Building team is experimenting with new outreach methods.
Despite the few RIPE Atlas probes available in Latin America, it is possible to obtain interesting measurements about changes in network architecture.
In this article we compare RIPE Atlas deployment against user population estimates provided by APNIC to see which eyeball networks are missing out on RIPE Atlas probes.
We’d like to enable gzip compression on all of RIPE Atlas' measurement API calls — but thanks to the BREACH vulnerability, doing so could mean that some enterprising individual with an obscene amount of time on their hands might be able read the contents of the responses. This means measurement results as well as metadata for measurements — including the small number of measurements not marked as “public”. We believe the drawbacks are negligible, but we’re looking for community support.
After a discussion with the community about HTTP measurements, we'll start implementing this as a publicly available measurement type.
During the RIPE 70 Meeting in Amsterdam this week (on 13 May around 10:00 UTC), we experienced a network outage at AMS-IX. Let's see how this was monitored by various tools.
In 2013 and 2014 we looked into measuring Interdomain Routing in Africa using the RIPE Atlas infrastructure. This resulted in a paper published at the PAM (Passive and Active Measurement) 2015 conference. Here we present some highlights of this research.
We looked at Internet measurements for the South East Europe (SEE) region in order to share these with attendees at the SEE 4 Meeting that took place from 21-22 April 2015 in Belgrade, Serbia. This is the long version of the lightning talk Vesna Manojlovic gave at SEE 4.
In March 2015, a diverse group of contributors got together to come up with creative ways to visualise the health of the Internet using RIPE Atlas open measurements data. It was the first RIPE Atlas hackathon. Impressive results were hacked together by programmers, designers and operators during an intensive weekend of work and fun in Amsterdam. In this article we celebrate hackathon achievements, document and promote hackathon results, create a memento for participants and report in detail for the benefit of the rest of the community.
With the MENOG 15 meeting taking place this week, we look at Internet measurements and statistics for countries in the MENOG region.
There was a power outage last week in the north of The Netherlands, a country with a very high density of RIPE Atlas probes. This density provides us with some interesting data and visualisation.
We've been working with various Internet Exchange Points (IXPs) over the last few months to see how RIPE Atlas active measurements can provide insight into how they are keeping local traffic local. This could help improve performance and efficiency for IXPs and their members. To explore this, we've created a set of Python scripts to analyse Internet traffic paths between RIPE Atlas probes in a given country and try to identify whether they traverse IXPs.
We visualised the measurements collected by our RIPE Atlas anchor. This allows us to analyse the quality of our connectivity and topology changes and to help debugging network issues. This monitoring page is publicly available.
The RIPE NCC's Chief Information Officer, Kaveh Ranjbar, gives an update on the state of our technical services and tools, and gives readers a heads up about what they can expect in 2015.
While the cyclone Pam is battering the South Pacific, we're monitoring how this affects Vanuatu.
The increasing number of middleboxes (such as firewalls, NATs, proxies, or Deep Packet Inspection) has raised concerns over the impact of such middleboxes on the network and the possibility to innovate. As a result, operators and researchers are studying the distribution and behaviour of middleboxes in large networks. In this article, we will describe a tool called Tracebox that helps in detecting middleboxes. Tracebox was developed at the Université Catholique de Louvain (UCL) and at university of Liège (ULg) in 2013 and funded by Change (INFSO-ICT-257422), mPlane (ICT-318627), and Bestcom IAP. We believe that adding tracebox-like capabilities to RIPE Atlas could give network operators a deeper insight into their systems and help debugging network problems.
Microsoft ended support for Windows XP as of April 2014. We're about to change RIPE Atlas and RIPEstat to stop support for Internet Explorer 8 running on these systems.
This article describes how RIPE Atlas probes and anchors maintain their clocks, and how accurate these clocks are. We also plan to make the NTP measurements we describe here available as an additional measurement type for RIPE Atlas users.
This article shows some prototypes of visualising network outages with RIPE Atlas using CartoDB.