RIPE Atlas Public Roadmap

RIPE Atlas users will be able to use an API to retrieve the list of RIPE Atlas anchors and their associated measurements.

Every 24 hours, collect all IP addresses used in measurements, results, netnames, geolocations, and announcing AS, and publish this data in bulk and through the API, indexed by IP.

Comparing probe deployment density with GDP, number of networks, population density, etc.

Improve visualisation of traceroute measurements

Optimising multiple measurements towards multiple targets by allowing users to create one measurement.

Allow users to create their own groups of measurements for viewing, downloading, and using in status checks.

While installing probes software on the virtual machines is technically possible, more guidance is needed from the community about choice of technology, limitations and possible consequences on RIPE Atlas systems. Read more on RIPE Labs.

There are per user limits that can prevent people from adding new measurements against the same target. In this case, offer a list of the current (public) measurements in a table or some other format.

Allow search by target, multiple views on the same target used in different measurements, etc.

Enable copying of existing measurements using the same set of probes and settings.

Timely and accurate reporting of probe status and distribution over time to ensure transparency and accountability to the community.

Users should be able to say "measure X and provide me a (written) report". This could be a one-off measurement or an ongoing one (in which case the report is most likely periodically made and sent, or even archived online for the user).

Allow Atlas Messages to be linked to an email template and send out that email if the user has opted-in to receive emails or severity of the message is high enough.

Handle probes dropping out of existing user-defined measurements (for example, by replacing them with new probes that meet the same criteria).

Enable monitoring of user's SSL certificate by building a feature that lets users predefine an expected SSL certificate, and match real world results against this.

Investigate automatic alarms in DNSMON based on RIPE Atlas status checks.

Implement visualisation of the root name servers anycast measurements for user-defined measurements towards anycasted targets.

Part of the RIPE Atlas community uses IRC as their preferred communication channel. We are considering how to integrate this with our existing communication practices.

When a measurement is created by specifying the IDs of the probes that should be used, for probes that are not selected, log and make available to the user why they were not selected. Add these as warnings to the user, if possible.

This feature has been asked by a number of probe hosts.

When results come in multiple days after a measurement has been stopped, don't bill for those results.

We can have a whitelist of networks that we exclude from target quota management.

Users receive notifications about events related to their probe: firmware update, new tag, errors. Accessible through My Atlas menu/messages.

NTP measurements are now available. Network Time Protocol (NTP) is a network protocol for clock synchronisation between computer systems. RIPE Atlas probes send NTP requests to one of the NTP servers, and the reply is received as a result together with the time the measurement is done. Based on this, the quality of synchronisation can be measured.

Learn more.

Allow sharing a probe with a custom-made group of users

Users need to be able to tag some IPs, prefixes, ASNs as "don't measure".

Every 24 hours, a snapshot of all probe metadata is published.

Several categories of system tags are added to the probes: connection type, connection speed, IP protocol DNS resolution, etc

Large groups of probes are now visually aggregated into donuts, and users can see probe statistics per specific country (e.g. number of active probes, compared to total number). Find out more.

Enable resilience of current services and scaling for future services.

Based on the DNS WG guidance, new DNSMON zones were added in 2015. Read more.

Goals of the new menu structure are to: enable users to access public measurements even when not logged in, simplify navigation and introduce dashboard pages for major categories of topics. Read more about it on RIPE Labs.

Get data for a built-in measurement for a specific time.

Enable exchanging TCP or UDP traffic on various ports.

Enable measurements from any device that has RIPE Atlas measurement software installed. The reasons we haven’t enabled this is detailed in the FAQ entry "Why did you choose a hardware solution instead of software?”

Research community has a need for the bulk downloads of historical built-in measurements.

Enable detection of middle boxes by specifying additional traceroute parameters.

This is a passive measurement and, as such, is not part of the scope of RIPE Atlas.

This is an exotic capability of limited use to the wider community.

This has been partially implemented by allowing users to copy parameters of a measurement. We will not implement the capability of starting a stopped measurement with the same measurement ID.

While it is technically possible to perform spoofed source measurements, there is a need for more input from the community about limiting the negative consequences of such measurements.

This is an exotic capability of limited use to the wider community.

Large amount of measurement results data are offered in compressed format in order to decrease download time and bandwidth. Learn more.

Enable sharing for the earning and use of credits with colleagues from the same LIR.

Inspired by hackathon results, internet maps performance and usability have improved. Check all hackathon results here.

Enable automatic measurements of targets contained in the "pingable" attribute in route and route6 objects in the RIPE Database

Make real-time measurement data and live streaming of data visualisations available to RIPE Atlas users. Learn more.

Users can create their own mesh measurement between custom-selected probes or per region.

Find out more.

New publicly available measurement type. Learn more.

Adding new RIPE NCC identity into RIPE Atlas graphics.

Our one-hour, interactive webinars offer RIPE NCC members the chance to learn about RIPE Atlas, watch live demonstrations and have their questions answered by developers. Learn more.

Second hackathon in 2015 has as a focus making and improving the tools, in cooperation between developers and network operators. Read more about it on RIPE Labs.

Open-sourcing the command-line client toolset with the community. You can get the code to run, and/or to contribute to, on GitHub. Read more on RIPE Labs.

Wikipedia now has an article about RIPE Atlas. Anyone in the community can edit Wikipedia and contribute to the article.