- ripe-atlas - mailman.ripe.net

Encouraging RIPE Atlas users to choose for public probes and measurements
by Vesna Manojlovic 13 Mar '14

13 Mar '14

Dear colleagues, One of the main goals of RIPE Atlas is to share information about Internet performance, which we collect via the active measurements performed by the thousands of probes in the RIPE Atlas network. In order to better achieve that goal, last year we suggested making even more of the collected data public. You can read the full details of this proposal on RIPE Labs: https://labs.ripe.net/Members/becha/proposing-making-ripe-atlas-data-more-p… We asked for feedback about this proposal from the RIPE Atlas community and, based on that feedback, we have decided not to go ahead with the proposal or make any major changes to the system. We would therefore like to revise our original proposal and suggest the following, revised plan: 1. We will strongly encourage RIPE Atlas users to keep their RIPE Atlas probes public and to perform public measurements as much as possible by: - Making new probes public by default (opt-out available) whenever someone applies for a new probe - Checking the public option by default when using the web interface to create user-defined measurements - Rewarding those who make their probes and measurements public by giving them more credits than those who don’t - Requiring all research enabled by special credits to produce public measurement results - Stressing the public nature of RIPE Atlas as a measurements platform in the RIPE NCC's publications and outreach 2. We will continue to allow users to *not* mark their probes public and to schedule user-defined measurements that are not public. 3. We will improve the documentation in order to clarify exactly what information is available for probes and user-defined measurements that are marked public versus those not marked public. Because this revised plan does not involve making any significant changes to our procedures or interfaces, the implementation would take place during our regular deployment cycle. We are basing this revised plan on the reactions of the 13 RIPE Atlas users who provided feedback after we proposed our original plan (you can find more details about the feedback we received below). We would like to hear from more of you, even if you just confirm that you agree with this revised proposal. Regards, Vesna Manojlovic Senior Community Builder for Measurements Tools RIPE NCC Summary of the feedback (the original comments can also be found on the RIPE Atlas mailing list archives): Eleven people replied on the mailing list and two replied on RIPE Labs, with some people supporting more than one option. - Three people supported making the data more public - Six people supported keeping things the same (i.e. against removing the "not public" option) - One person suggested making the data less public - Three people suggested delaying the publication of the public results (a new suggestion) - One person was completely neutral Specific comments included: - Making the data public by default is okay, but leave the option to not make it public - If a delay in making the data public is introduced, one-off measurements should be excluded - A delay in making the data public will introduce more complexity to the system - A proposal to receive extra/fewer credits for making probes and measurements public/not public, respectively

8 8

New on RIPE Labs: Improved RIPE Atlas Probe Pages
by Mirjam Kuehne 13 Mar '14

13 Mar '14

Dear colleagues, We've made it easier to get an overview of the history and measurements for all the public probes in the RIPE Atlas network. Read about that and other new functionality on RIPE Labs: https://labs.ripe.net/Members/suzanne_taylor_muzzin/ripe-atlas-improved-pro… Kind regards, Mirjam Kuehne RIPE NCC

5 4

Blacknight Internet Solutions Ltd (IE) has joined RIPE Atlas anchors
by Michela Galante 12 Mar '14

12 Mar '14

Dear RIPE Atlas users, We're happy to announce that another RIPE Atlas anchor has joined the network and is now available as a target for probe hosts conducting their own user-defined measurements. The new anchor is called ie-caw-as39122 and it is hosted by Blacknight Internet Solutions Ltd in Carlow, Ireland. Anchoring measurements (ping, ping6, traceroute and traceroute6) are scheduled towards this anchor from all the other anchors as well as several hundred probes, providing a continual overview of regional reachability. Results of these measurements are available as raw data in JSON format, and visualised on the map and "seismograph" with many configurable features. You can access the anchoring measurements for all anchors at: https://atlas.ripe.net/anchors/list/ Learn more about RIPE Atlas anchors at: https://atlas.ripe.net/about/anchors/ Thank you for participating in RIPE Atlas! Kind regards, Measurements Community Building Team RIPE NCC mcb(a)ripe.net

1 0

Is "Prepend probe's ID" checkbox working?
by Willem Toorop 12 Mar '14

12 Mar '14

Hi, In the web-interface DNS UDM, there is checkbox "Prepend probe's ID". Is this working already? Where does it prepend the ID? I expected it to prepend to the query name (i.e. Argument), but I couldn't see it working. Regards, -- Willem

2 2

Searching for public measurements
by Sebastian Castro 12 Mar '14

12 Mar '14

Hi: I want to search for specific public measurements for hosts that are most likely be monitored at this point. Is there are way to do this using the web interface, or I should try to fetch all public measurement ids and do the grinding myself? Considering there are more than 560,000 public measurements, getting all the ids doesn't sound like a good idea. Cheers, -- Sebastian Castro Technical Research Manager .nz Registry Services (New Zealand Domain Name Registry Limited) desk: +64 4 495 2337 mobile: +64 21 400535

2 1

Probe management
by Marco Davids (SIDN) 11 Mar '14

11 Mar '14

Hi, In the 'general information' tab of our probe I noticed a section 'management sharing', with our regID as a group that apparently has 'shared administration' rights. My question: is it possible to add some of my colleagues to that group, so that they have access to the probe as well? Seems like a better thing to do than handing out my LIR-credentials... Cheers, -- Marco

3 2

Mail.ru Group (RU) has joined RIPE Atlas anchors
by Michela Galante 10 Mar '14

10 Mar '14

Dear RIPE Atlas users, We're happy to announce that another RIPE Atlas anchor has joined the network and is now available as a target for probe hosts conducting their own user-defined measurements. The new anchor is called ru-mow-as47764 and it is hosted by Mail.ru Group in Moscow, Russia. Congratulations to Mail.ru Group! This is the first anchor in Russia. Anchoring measurements (ping, ping6, traceroute and traceroute6) are scheduled towards this anchor from all the other anchors as well as several hundred probes, providing a continual overview of regional reachability. Results of these measurements are available as raw data in JSON format, and visualised on the map and "seismograph" with many configurable features. You can access the anchoring measurements for all anchors at: https://atlas.ripe.net/anchors/list/ Learn more about RIPE Atlas anchors at: https://atlas.ripe.net/about/anchors/ Thank you for participating in RIPE Atlas! Kind regards, Measurements Community Building Team RIPE NCC mcb(a)ripe.net

1 0

AusRegistry (AU) has joined RIPE Atlas anchors
by Michela Galante 05 Mar '14

05 Mar '14

Dear RIPE Atlas users, We're happy to announce that another RIPE Atlas anchor has joined the network and is now available as a target for probe hosts conducting their own user-defined measurements. The new anchor is called au-mel-as38796 and it is hosted by AusRegistry in Melbourne, Australia. Congratulations to AusRegistry! This is the first anchor in Oceania and the second in the Asia and Pacific area. Anchoring measurements (ping, ping6, traceroute and traceroute6) are scheduled towards this anchor from all the other anchors as well as several hundred probes, providing a continual overview of regional reachability. Results of these measurements are available as raw data in JSON format, and visualised on the map and "seismograph" with many configurable features. You can access the anchoring measurements for all anchors at: https://atlas.ripe.net/anchors/list/ Learn more about RIPE Atlas anchors at: https://atlas.ripe.net/about/anchors/ Thank you for participating in RIPE Atlas! Kind regards, Measurements Community Building Team RIPE NCC mcb(a)ripe.net

2 1

New on RIPE Labs: The Seismograph User Guide
by Suzanne Taylor Muzzin 05 Mar '14

05 Mar '14

Dear colleagues, Please find a new article on RIPE Labs that explains how you can get the most out of the Seismograph, an interactive RIPE Atlas tool that provides an overview of different RTT and packet loss trends measured by multiple probes. The Seismograph User Guide https://labs.ripe.net/Members/massimo_candela/seismograph-user-guide Kind regards, Suzanne Taylor Muzzin Measurements Community Building RIPE NCC

2 1

Some Atlas Anchor Graphs
by Daniel Karrenberg 27 Feb '14

27 Feb '14

During some research I happened to visualise some random anchor calibration measurements and thought I'd share the graphs. The basis are IPv4 traceroutes from all (4500+) RIPE Atlas probes to the anchor encoded in the file name. The graphs show adjacencies that appear in more than 3% of all paths. IP addresses are aggregated by the network name as registered in the RIR registries. The darker an edge appears, tho more paths contain this adjacency; the colouring is scaled logarithmically. Enjoy Daniel

1 0