RIPE Atlas back-end applications run on more than 40 servers. Each day these machines can produce thousands of application logs of any kind of severity level. In order to be able to track down serious errors, warnings or even unusual behaviour, we decided some time ago to try Elasticsearch as a logging sink. In this article we will look at the design of such a system and describe how we can easily make sense from an ocean of logs.
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.
I attended a conference on Broadband Services and Infrastructure Mapping, which I think had some interesting content for RIPE Labs readers.
The IXP country jedi tool described in earlier RIPE Labs articles, can also be used to analyse the situation in a specific city. This time we look at Berlin.
The RIPE NCC has developed an additional interface for the RIPE community mailing lists – something that we hope will encourage more interaction and discussion among the RIPE community.
In February 2011 the RIPE NCC implemented the "pingable:" and "ping-hdl:" attributes in the RIPE Database. These attributes were added to the Routing Policy Specification Language by RFC 5943 to allow networks to advertise IP addresses that are reachable and can be used as a target for diagnostic tests. Five years later we check how the new attributes have been adopted and how reachable the pingable addresses registered in the RIPE Database are when pinged from RIPE Atlas.
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.
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.
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.
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!
Following my research on DNS reachability and performance, I found interesting results for specific domain names.
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!
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.
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.
A little while ago, we asked what you thought about the idea of conducting WiFi measurements in RIPE Atlas. After some consideration and community feedback, we now want to propose a way to implement this feature in RIPE Atlas and clarify exactly how these measurements will benefit the RIPE Atlas community.
The concept of virtual probes is one that RIPE Atlas users have asked about for quite some time. Although we don't plan to make virtual probes available in 2016, we do plan to investigate this idea and develop some prototypes.
More and more governments, authorities and courts are requesting censorship of Internet content. It is often done via a lying DNS resolver. Can we use RIPE Atlas probes to see it, and how?
RIPE Atlas users have been asking us for some time to support a command-line interface (CLI), and we're pleased to announce that it's now available.
A few weeks ago we gave you a heads up about a new visualisation tool in RIPE Atlas called DomainMON, and we're pleased to announce that this is now available for all RIPE Atlas users with available credits.