With RIPE NCC Access, our single sign-on service - you log in once and can access many RIPE NCC services. Now, with the new RIPE Database release, you can update your data in the RIPE Database using this single sign-on service. This is part of the RIPE NCC's work to make the RIPE Database easier to use.
We wanted to find out what network security experts think about network anomalies. We created a short web survey in order to map opinions of network professionals. In this article we describe the results.
We've made it much easier to get an overview of the history and measurements for all the public probes in the RIPE Atlas network. We've also added some new functionality, such as being able to add tags to probes and mark them as "favourites". Get all the details below and then explore the new pages for yourself - and don't forget to tell us what you think.
When a senior engineer at FreeAgent, an accounting software provider, got a tweet about their servers running slowly, he turned to RIPE Atlas to help solve the problem.
More and more network operators are interested in using RIPE Atlas as a monitoring tool. We listened to your requests and are pleased to introduce Status Checks, a new feature that lets you harness the power of the RIPE Atlas network to help monitor the health of your own services.
The Seismograph is an interactive RIPE Atlas tool that allows users to analyse and visualise ping measurements. Here we explain the tool's different features and how you can make the most of them.
The recently accepted policy proposal 2012-08, "Publication of Sponsoring LIR for Independent Resources", requires the RIPE NCC to publish an identifying link between each independent Internet number resource in the RIPE Database and the sponsoring organisation (where such a link exists). This article outlines how we propose to implement this, and asks for your feedback.
Increasing the reach of RIPE Atlas anchors is one of the highest priority goals of RIPE Atlas Team. In this article we will inform you about the current status, new features and, as always, we want to get your feedback about our plans.
Before we decide to implement a stricter operational practices, we needed to find out how many routes with invalid origins are actually being used and how much traffic is exchanged using those routes. Please find the results below.
After the recent amplification attacks involving NTP servers, John Kristoff, a researcher with Team Cymru, kindly agreed to publish an analysis of the history and timeline leading up to the attacks. Please find his contribution below.
The techniques used by the L-root DNS server are documented in RFC 7108 "A Summary of Various Mechanisms Deployed at L-Root for the Identification of Anycast Nodes". These techniques can be used by the RIPE Atlas probes to find the instance of L-root they are talking to.
RIPEstat users saw a lot of changes throughout 2013, from support for new query types, such as countries and hostnames, to a completely revamped website. Below we summarise some of the most exciting advancements from the year, and give you a sneak peek of the things we think you might find useful in 2014. As always, please let us know what you think!
It has been a busy last quarter of 2013 for RIPE Atlas. Here you have an overview of the latest features and new functionality.
Each RIPE Atlas probe has at least one DNS resolver, indicated by a DHCP reply on the local network of the probe. Irrespective of the IP address of the resolver, this server may have IPv4 and IPv6 connectivity or only IPv4 connectivity. What is the percentage among RIPE Atlas probes?
The RIPE NCC wishes to thank all members of the RIPE Atlas community for their participation and support. This includes RIPE Atlas probe hosts, anchor hosts, sponsoring organisations, ambassadors, users and all RIPE NCC members who support this activity. Below we describe the major achievements and changes implemented in 2013.
At RIPE 67 we presented our ideas on infrastructure geolocation. We received positive feedback for developing this idea. This article shows the current thinking on how to develop router geolocation further. Any feedback will be appreciated.
RIPE Atlas is now three years old, and is moving from a prototype to production service. Based on our experience so far, observing typical usage and listening to user feedback, we suggest opening up the publication of measurement data further. In this article we aim to clarify the current situation regarding privacy, and ask for community input about our suggested plan to move forward.
At the RIPE 67 meeting in Athens, Greece, the RIPE IPv6 Working Group ran a little experiment to test the feasibility of an IPv6-only network and to identify challenges in user experience. While the results were highly encouraging, they indicated that there is still work to be done before IPv4 can be switched off once and for all.
We would like your help for a planned project to create subtitles for our e-learning videos in multiple languages.
View maps based on RIPE Atlas traceroute measurements. Compare the maps to the ISP's description of their topology. See the potential of RIPE Atlas for mapping the packet layer topology. Learn about experimental tools you can use yourself to explore. Make suggestions for further work.