We started using RIPE Atlas to monitor and improve the services to our customers. We liked it so much that we're now a sponsor!
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.
We announced earlier that the RIPE Atlas APIs will change around the end of the year. In this article we give some advice on how to make this transition.
How we compare connectivity of cloud services using RIPE Atlas latency and DNS measurements
In July, I was fortunate enough to attend the third Indonesia Network Operators Group conference, IDNOG 3, which was held in Jakarta.
We take another, more detailed look at probe lifetimes and the dynamics of probes connecting and disconnecting from the RIPE Atlas infrastructure to try to understand how to keep the network growing in the long term.
The RIPE NCC is hosting a hackathon focused on developing tools for Internet Exchange Points. Come participate!
Until now, native IPv4 and IPv6 has been one of the conditions of hosting a RIPE Atlas anchor. However, we realise that IPv6 simply isn't available in some would-be anchor hosts' ASNs. As a result, we've decided to support IPv4-only anchors.
traIXroute is a tool that detects whether and where a traceroute path crosses an Internet Exchange Point (IXP). It uses data from multiple sources and advanced criteria to verify IXP crossings to deal with problems due to replies from third-party interfaces or inaccuracies in the available data about IP addresses assigned to IXPs. These problems can mislead simple heuristics, based solely on the IP address prefixes allocated to IXPs, for the inference of IXP crossings.
We continue to look at failure rates for RIPE Atlas version 3 probes and the possible causes.
With the attempted coup in Turkey, reports went out about social media being throttled and/or blocked. We analysed data about this that we collected with RIPE Atlas and the Open Observatory of Network Interference (OONI).
Following my recent research on DNS hijacking and the cases I have personally observed, I wondered whether this is a common practice among the operators. With the help of RIPE Atlas, I started to think of a solution to figure out whether such practice is widespread in other areas of the world.
Some of the third version of RIPE Atlas probes have recently had an issue with their USB sticks. We're investigating what may be causing this issue and have a possible solution, outlined below. (At the same time, we're also looking into a new hardware solution for the future.) If you've had trouble with your probe, please follow these simple steps. RIPE Atlas users everywhere will thank you for getting your probe back online - and we will, too!
Browse through a collection of presentations, tutorials and videos about RIPE Atlas, from both RIPE NCC staff as well as members of the Internet community who use RIPE Atlas.
Hear from RIPE Atlas users about their experiences with RIPE Atlas and how they use RIPE Atlas data to troubleshoot and gain valuable information about their own networks.
Academic researchers use RIPE Atlas data to investigate a number of topics, from Path MTU black hole detection to packet delay.
RIPE NCC developers and researchers present their own findings about a range of topics using RIPE Atlas data, from the effect of hurricanes on the Internet to examining IPv6 /48 filtering.
There are about 600 DNS root server instances deployed around the world. But does everyone have an equal level of access to a root server in their region? Are they fairly distributed? Do all major (and country level) network operators recognise the value in deploying (or peering with) a root server in their network?
The third RIPE Atlas hackathon took place in Copenhagen the weekend before RIPE 72. In this article, we share the details about the hackathon and a preview of the fourth hackathon.
IP anycast has been widely used to replicate services in multiple locations as a way to deliver better performance and resilience. It has been largely employed by CDNs and DNS operators, such as on the root server system. However, there is little evaluation of anycast under stress.
For a while now, the number of active RIPE Atlas probes has hovered around the 9,400 mark. This means that new probes are being connected at a fast enough rate to replace failing probes, but not enough to grow the network. At the same time, the version 3 probes have problems with their USB sticks. This led us to wonder whether these two issues are related.