- ripe-atlas - mailman.ripe.net

network coverage and probe API
by Bajpai, Vaibhav 23 Apr '14

23 Apr '14

Hello, The network coverage page [1] shows around 10K+ registered probes. However, if I call the probe API [2], the total_count field shows 8K probes. Probe objects also have is_public field, so I assume the API counts both public and private probes. There is also a status field, so I assume the API counts connected, disconnected and abandoned probes as well. What am I missing? [1] https://atlas.ripe.net/results/maps/network-coverage [2] https://atlas.ripe.net/api/v1/probe Best, Vaibhav ----------------------------------------------------- Vaibhav Bajpai Research I, Room 86 Computer Networks and Distributed Systems (CNDS) Lab School of Engineering and Sciences Jacobs University Bremen, Germany www.vaibhavbajpai.com

5 7

one-off traceroute and interval parameter
by Bajpai, Vaibhav 16 Apr '14

16 Apr '14

Hello, Traceroute UDMs include an interval parameter. If I provision a one-off traceroute UDM via the GUI wizard, the interval field should get disabled no? Once the measurement is completed, the general information tab for the UDM now shows the interval for a one-off measurement as 900s. PS: We understand the interval parameter may have made no difference to the actual measurement. This is more of a bug report for visual side of things. Best, Vaibhav ----------------------------------------------------- Vaibhav Bajpai Research I, Room 86 Computer Networks and Distributed Systems (CNDS) Lab School of Engineering and Sciences Jacobs University Bremen, Germany www.vaibhavbajpai.com

1 0

v2 in anchorv2
by Bajpai, Vaibhav 15 Apr '14

15 Apr '14

Hello, We have a RIPE atlas anchor question. Can you please tell us the reason for using v2 in anchorv2? We went to [2], but that doesn’t exist. We also searched but couldn’t find documentation on this. [1] http://anchorv2.ripe.net [2] http://anchorv1.ripe.net PS: We understand what RIPE atlas anchors do :-) Best, Vaibhav ----------------------------------------------------- Vaibhav Bajpai Research I, Room 86 Computer Networks and Distributed Systems (CNDS) Lab School of Engineering and Sciences Jacobs University Bremen, Germany www.vaibhavbajpai.com

2 1

Related to Rip Atlas Credit System
by Roya Ensafi 14 Apr '14

14 Apr '14

Hi all, Considering RIPE Atlas credit system, ping and tracerout unit cost calculations are tricky. It closely depends on number of packets in train and size of the packets. Based on [1], predicted cost of a traceroute measurement with sent packet size of 2040 and 3 as number of packets (detail arguments are bellow) should be 10*3*(int(2040/1500)+1) = 90 (refer to [1]). However, predicted cost calculated by RIPE server is 120. After looking at available JavaScript, we couldn't find the predicted cost calculation. It sounds like calculation happens on server side and then the the value is returned. Is it possible to check the server code i.e. is the cost function calculation on server side publicly available? Thanks, Roya Enasfi [1]: https://atlas.ripe.net/docs/credits Details for a traceroute measurement : (Per result: 120.0 credits, Estimated total cost: 120 credits) Arguments: (Interval: 900 seconds, Resolve on probe: No, First hop: 1, #packets: 3, Don't fragment: True, Max hops: 32, Tcp: True,Paris: 16, Timeout resp.(ms): 4000, Port: 80, Size: 2040)

2 1

APNIC (AU) has joined RIPE Atlas anchors
by Michela Galante 14 Apr '14

14 Apr '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-bne-as4608 and it is hosted by APNIC in Brisbane, Australia. This is the second anchor hosted by an RIR on behalf of the RIPE NCC. 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

"Invalid group id" for Restful API?
by Philipp Winter 11 Apr '14

11 Apr '14

I'm trying to create a measurement using Atlas' Restful API [1]. Before that, I created an API key for measurement creation. Using my API key, when executing the simple example shown in [1], the server tells me: > {"error": {"code": 104, "message": "group: Invalid group id"}} I get the same error code with different JSON-formatted queries. Any ideas what's going on here? [1] https://atlas.ripe.net/docs/measurement-creation-api/ Cheers, Philipp

4 4

Using ripe data results on publications?
by Daniel Gomez 08 Apr '14

08 Apr '14

Good Morning everyone, What is the policy about using ripe atlas results on articles and publications? We know atlas is a great infrastructure to perform measurements, but we can find on them , i.e. traceroute, private IPs from atlas hosts networks. I know there is a lot of people on this list concerned about making public some information. Are atlas results open to share and so the probes information? Greetings, Daniel Gomez

2 1

Probe IPs are public?
by Roman Mamedov 08 Apr '14

08 Apr '14

Hello, I was under impression RIPE tries to somewhat anonymize probe information that's displayed publicly, e.g. only showing the probe IP address information down to the subnet or AS level on the maps, providing the option to use "Obfuscated DNS entry", etc. But on the public stats pages e.g. here: https://stat.ripe.net/widget/atlas-probes#w.resource=DE (+ "switch to table view") I am able to see both IPv4 and IPv6 addresses of many or most probes without even having to log-in; is that intended? Also what is the point of choosing to use the Obfuscated DNS option if the probe IPs are available in the clear anyway. -- With respect, Roman

4 3

Net Neutrality measurements
by Georg Chytil 31 Mar '14

31 Mar '14

Dear collegues, I sympathize with the cause for net measurements, and the RIPE Atlas project in particular. I´d like to draw your attention to the use of net measurement infrastructure as a means of documenting net neutrality, and a consulation of BEREC in this context: http://berec.europa.eu/eng/news_consultations/ongoing_public_consultations/… I´d appreciate if RIPE got involved in this field before less desireable and competent parties do ;-) Maybe comment on net neutrality on https://atlas.ripe.net/about/future-plans/ ? Kind Regards #g

3 2

Use case for RIPE Atlas: DNS service disruption in Turkey
by Vesna Manojlovic 31 Mar '14

31 Mar '14

Dear all, one of our most active users, Stephane Bortzmeyer, performed RIPE Atlas (and other) measurements to collect the data for his analysis, published in a blog post yesterday: "Hijacking of public DNS servers in Turkey, through routing" http://www.bortzmeyer.org/dns-routing-hijack-turkey.html Thank you for this interesting use-case! This is a call for the rest of the community to let us know if you have done some measurements or analysis to solve your problem, or to better understand a network-event - please share it with us. We are also interested in re-publishing your stories on RIPE Labs. You can find the previous articles here: https://labs.ripe.net/atlas Regards, Vesna

1 1

LACNIC (UY) has joined RIPE Atlas anchors
by Michela Galante 28 Mar '14

28 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 uy-mvd-as28000 and it is hosted by LACNIC in Montevideo, Uruguay. Congratulations to LACNIC! This is the first anchor in Latin America and the first one hosted by an RIR on behalf of the RIPE NCC. 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

MWEB (ZA) has joined RIPE Atlas anchors
by Michela Galante 26 Mar '14

26 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 za-jnb-as10474 and it is hosted by MWEB in Johannesburg, South Africa. Congratulations to MWEB! We have now a total of 50 active RIPE Atlas anchors! 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

ATI (TN) has joined RIPE Atlas anchors
by Michela Galante 25 Mar '14

25 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 tn-tun-as5438 and it is hosted by ATI in Tunis, Tunisia. Our congratulations to ATI! This is the first anchor in Africa. 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

Ennit Server (DE) has joined RIPE Atlas anchors
by Lia Hestina 24 Mar '14

24 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 de-kel-as13101 and it is hosted by Ennit Server in Kiel, Germany. 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

400 Bad Request
by Wilfried Woeber 22 Mar '14

22 Mar '14

Hi folks, I had a look at the list of my ambassador probes and noticed that one of them is currently listed as being off-line (ID 12734) The probe ID is rendered as a link, with this URL: https://atlas.ripe.net/ambassadors/probes/%7B%%20url%20'probe-detail'%20pk=record.prb_id%20%7D%7D which comes back with " Bad Request Your browser sent a request that this server could not understand. " Just fyi, no harm done :-) Cheers, Wilfried

2 2

HEAnet (IE) has joined RIPE Atlas anchors
by Michela Galante 20 Mar '14

20 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-dub-as1213 and it is hosted by HEAnet in Dublin, 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

8.8.8.8 hijack and ripe atlas
by Jared Mauch 20 Mar '14

20 Mar '14

It appears there are some public measurements like #1002630, and i'm curious if someone is able to look at the latency and TTL numbers of the transport side and observe the localized hijacking of 8.8.8.8. The dataset is somewhat huge and i'm not a json master so trying to discern if there is evidence in there is something i'm looking at. - Jared

3 6

Netnod (SE) has joined RIPE Atlas anchors
by Michela Galante 19 Mar '14

19 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 se-sto-as8674 and it is hosted by Netnod in Stockholm, Sweden on behalf of RIPE NCC since they are one of our RIS Remote Route Collector locations. 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

life-cycle of a probe?
by Wilfried Woeber 19 Mar '14

19 Mar '14

Hi folks, is there a way to find out when a particular probe (under my control[1]) was seen by a/the collector(s) for the first time? The best I have come up with is to look at the raw data download, but I'm not sure that the data has been preserved for raw download in the "early days". Thanks, Wilfried [1] just in case, I am interested in ID 466 and 414

2 2

CSUC (ES) has joined RIPE Atlas anchors
by Michela Galante 17 Mar '14

17 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 es-bcn-as13041 and it is hosted by Consorci de Serveis Universitaris de Catalunya (CSUC) in Barcelona, Spain. Congratulations to CSUC! This is the first anchor in Spain. 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

Feature Request - Atlas Latest
by John Bond 17 Mar '14

17 Mar '14

Hello Atlas, I would like to request an additional API call which just returns the latest results for a specific measurement. For use cases I would point you to the "RIPE Atlas - Map Visualisations²[1]. I have also seen places in the dnsmon beta where you only show the latest results. this would also be very useful for trouble shooting, if I see an issue its inconvenient to download xMB of json data just to see the whats going on now. An additional feature would be to ask for a result for X seconds in the past, the call would return a result closest to that time. This is for investigating historic events, if I have an issue that lasts one hour I would normally only need one result to perform the initial investigation. This would also be useful to have a history/timeline function to the maps[1]. The following code at the end of this mail does something similar to what I would like using the current API. By setting GO_BACK_IN_TIME=0 you should get the most recent measurement. However this is not perfect, depending on what value one sets the INTERVAL do you may get multiple results or now may get none and as far as I can tell this dose not relate to the measurement Interval. The other issue with queuing the results like this is that you get a lot of superfluous data. I.e. For the dns measurement in the script below you get result[answers][RDATA] and result-rdata which both seem to have the same data. Furthermore when in a script im not to interested in the probe and measurement details. If I am, I will request that information from the appropriate probe or measurement api call. For the DNS measurement a structure like the following would suite my needs { probe_id: { abuf: str, timestamp: int, result: { additional: str, question: str, authority: str, opcode: str, answer: str, flags: str, rcode: str, id: int }, response_time: float } } Thanks John #/bin/sh GO_BACK_IN_TIME=86400 INTERVAL=240 NOW=$(date +%s) MSG_ID=1423370 URL="https://atlas.ripe.net/api/v1/measurement/${MSG_ID}/result/?stop=$((NO W - GO_BACK_IN_TIME))&start=$((NOW - GO_BACK_IN_TIME - FREQUENCY))&format=json" echo ${URL} wget -q "${URL}" -O - [1]https://atlas.ripe.net/results/maps/

2 2

Building a "My Measurement" list via the API
by Martin Topholm 17 Mar '14

17 Mar '14

I recently started using the Atlas API interface for easier measurement access. I can't seem to find a way to list "My merasurements". It is quite possible I've overlooked something in the docs, but it seems to me I only can differentiate on is_public=0. Thus all my measurements need to be private in order build a "My Measurements" list. Is there another way? -- Kind regards, Martin Topholm

2 1

Research papers for IMC or other measurements conferences
by Vesna Manojlovic 15 Mar '14

15 Mar '14

Dear colleagues, a couple of researchers using RIPE Atlas brought this conference to my attention, and I noticed that the CFP deadline is approaching fast. I would be curious to hear if anyone else is planning to submit a paper based on RIPE Atlas data to IMC, or any other conference. Please let me know if you need some extra help from us: more credits, higher limits for usage of probes per measurements, or additional text for your paper. We would be grateful for your mention of the RIPE NCC and RIPE Atlas in your paper, and would like to invite you to share your results, after the conference, with RIPE community, either by presenting at RIPE meetings or publishing on RIPE Labs. Regards, Vesna IMC Details: http://conferences2.sigcomm.org/imc/2014/ The 2014 Internet Measurement Conference (IMC) is a three-day event focusing on Internet measurement and analysis. The conference is sponsored jointly by ACM SIGCOMM and ACM SIGMETRICS. IMC 2014 is the 14th in a series of highly successful Internet Measurement Workshops and Conferences. The ACM IMC 2014 conference will be held in Vancouver, BC, Canada on November 5-7, 2014. Call for papers deadline: 30 April http://conferences2.sigcomm.org/imc/2014/cfp.html

2 1

Seismograph for public ongoing measurement
by Sebastian Castro 14 Mar '14

14 Mar '14

Hi! The seismograph is available for UDMs as announced here https://labs.ripe.net/Members/becha/seismograph-and-other-new-ripe-atlas-fe… Is there a way to generate the seismograph for a public ongoing measurement, for example, MSM id 1423322 (f-root)? 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

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