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.
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.
The adoption of the RPKI system is growing rapidly. To make sure the system scales, we’ve developed a new protocol that should drastically improve fetch times for RPKI repositories. This article explains how.
Despite the few RIPE Atlas probes available in Latin America, it is possible to obtain interesting measurements about changes in network architecture.
Most of the time, mostly everywhere, most of the Internet appears to work just fine. Indeed, it seems to work just fine enough to the point that that when it goes wrong in a significant way then it seems to be fodder for headlines in the industry press.
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.
At RIPE 70, Tim Bruijnzeels presented some statistics on the type of authentication people use to update the RIPE Database. There was one data point that particularly stood out for me: 76% of all updates via email are done using an MD5 password. I was stunned, because this way you are required to send your password in clear text over the Internet...
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.
For EuroDIG 2015, held in Sofia, Bulgaria on 3 and 4 June 2015, the RIPE NCC was pleased to be able to support the participation of Corinne Cath, who presented her work on human rights in the development of technical protocols at the recent RIPE 70 Cooperation Working Group session. Below is her impression of the conference.