- ripe-atlas - mailman.ripe.net

"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