In the past few months, we've added some new features and functionality to RIPE Atlas, including making the DNSMON code available on GitHub for personal use, displaying IPv4 vs IPv6 comparisons in LatencyMON, new credit sharing options, and new limits on probes per measurement and results per day. Learn more about the latest updates - and don't forget to tell us what you think.
Here's how we developed a methodology and open source tools to make it easier to detect route prefix hijacks.
The Elliptic Curve Cryptography (ECC) is becoming increasingly popular in DNSSEC. While it is sometimes considered to be a remedy for the low DNSSEC adoption rate, there is also a lot of controversy around it. One of the main concerns is that DNSSEC-validating resolvers don't always make use of ECC. We used RIPE Atlas to measure the support for ECC in DNS resolvers.
Internet interconnection has often been described as an unregulated field. However, local public regulation is starting to emerge – be it through disclosure regulations, mandatory peering or licensing terms. Due to the networked nature of the internet, local rules may acquire a global scope.
We’ve updated our IPv4 graph to tell the whole story about our remaining address pool.
A new tool joins the family of applications whose goal it is to take full advantage of RIPE Atlas to monitor availability, consistency and reachability of networks and services: the RIPE Atlas Monitor.
This week, the RIPE NCC saw a milestone as the 10,000th Local Internet Registry (LIR) received IPv6 addresses. The first block of IPv6 addresses was allocated from IANA to the RIPE NCC in 1999, so we have been distributing IPv6 addresses for 17 years. In those years we have seen interesting policy developments, making it easier for LIRs to obtain enough IPv6 to satisfy their needs. In this article we track the policy developments that have made it progressively easier for LIRs to get the IPv6 they need.
The RIPE Atlas Interface Hackathon is an opportunity to work together with RIPE Atlas developers and other enthusiastic coders and hackers. The hackathon will take place from 21-22 May in Copenhagen ahead of the RIPE 72 Meeting. Find out how you can take part!
We tend to make a number of assumptions about the Internet, and sometimes these assumptions don’t always stand up to critical analysis. We were perhaps ‘trained’ by the claims of the telephone service to believe that these communications networks supported a model of universal connectivity. Any telephone handset could establish a call with any other telephone handset was the underlying model of a ubiquitous telephone service, and we’ve carried that assumption into our perception of the Internet. On the Internet anyone can communicate with anyone else – right?
Following my research on DNS reachability and performance, I found interesting results for specific domain names.
The RIPE NCC membership has raised concerns regarding members setting up additional Local Internet Registry (LIR) accounts. The RIPE NCC Executive Board is now asking the RIPE NCC membership to discuss this. The article below provides some background information, data and statistics for the discussion.
This is the second part in a series of articles looking at the use of DNS servers in Iran. For the second part I will continue measuring performance and reachability for two more sets of DNS resolvers: TIC and Verisign.
While most Internet users are not aware of the importance of DNS resolution in their overall web browsing experience, they often complain about shortage of bandwidth when experiencing sluggish Internet connectivity. It is no surprise that most of the service providers also ignore this fact by redirecting their customer DNS traffic to public DNS servers.
RIPE Atlas has been in operation for more than five years now, and its network of probes and users has grown tremendously in that time. We’ve also added anchors, sponsors and ambassadors to the system, developed a huge array of new tools, visualisations and features, and RIPE Atlas data is now being used by network operators, engineers and researchers around the world. As a result, we thought it was time to revamp the RIPE Atlas website, which hadn’t changed much over the past five years despite all the changes to RIPE Atlas itself. Get an overview of some of the biggest changes and new features - then check out the new site, which launches today!
In this report we provide some more details about the incidents of 30 November and 1 December 2015, as seen from the K-root environment. We also share some of the lessons we took away from this event.
I was at FOSDEM 2016 last weekend, and wrote up a few of my observations around DNS there. Enjoy!
RIPE Atlas had another successful year in 2015, thanks in large part to all our users, hosts, sponsors, ambassadors and other community members. Here we take a look back at some of the achievements we reached together, the new features we implemented, key facts and figures - and offer a sneak peek of what you can expect in 2016.
One of the more difficult design exercises in packet-switched network architectures is that of the design of packet fragmentation. In this article, I’d like to examine IP packet fragmentation in detail and look at the design choices made by IP version 4, and then compare that with the design choices made by IP version 6.
RIPE Atlas collects a lot of measurements. But how much of the Internet are we actually measuring? 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.
Wouldn’t it be nice if turning on IPv6 really was ‘press one button and the rest is magic’ easy?