- ripe-atlas - mailman.ripe.net

Availability report accuracy
by Lorenzo Colitti 03 Jan '16

03 Jan '16

Hi, mostly out of curiosity: what sort of accuracy are the numbers in the monthly availability report? For example: the report says that my probe was "connected" 99.95% of the time (down for 20 seconds) in December. What does that mean? That the SSH control connection was not up? That the probe didn't have link? That it couldn't reach any targets? Something else? Cheers, Lorenzo

4 4

Seven new RIPE Atlas anchors have joined the community
by Michela Galante 31 Dec '15

31 Dec '15

Dear RIPE Atlas users, Since the previous announcement, seven new RIPE Atlas anchors have been activated bringing the total number to 164. - nc-nou-as56055, hosted by Micro Logic Systems (MLS) in Nouméa, New Caledonia. - bg-sof-as47872, hosted by Sofia Connect in Sofia, Bulgaria. - bg-sls-as198228, hosted by Silistra Telecom Solutions in Silistra, Bulgaria. - fr-ysd-as201958, hosted by Claranet in Saint-Denis, France. - de-erl-as680, hosted by Friedrich-Alexander-Universität Erlangen-Nürnberg in Erlangen, Germany. - cr-sjo-as263779, hosted by NIC Costa Rica in San José, Costa Rica and sponsored by LACNIC. - nl-roo-as43350, hosted by NFOrce Entertainment in Roosendaal, Netherlands. The map of all anchor locations is available at: https://atlas.ripe.net/anchors/map/ You can access the anchoring measurements for all anchors at: https://atlas.ripe.net/anchors/list/ And here are the logos and links to hosting companies: https://atlas.ripe.net/get-involved/community/#!tab-anchor-sponsors We are still accepting new applications from organisations interested in hosting a RIPE Atlas anchor. We are particularly interested in deploying anchors in the Middle East, Western Asia, Latin America and Africa, in order to add more geographical diversity to the measurement data. There are more organisations that want to host a RIPE Atlas anchor but don’t have the necessary funding. To learn more about sponsoring an anchor, please contact us at mcb(a)ripe.net To apply for your own RIPE Atlas anchor: https://atlas.ripe.net/get-involved/become-an-anchor-host/ For any other questions, please contact us at atlas(a)ripe.net We’d like to thank all the anchor hosts and the organisations sponsoring anchors for their support in 2015. Thanks to you it was possible to expand the coverage and reach this amazing goal. Wishing all of you the best for 2016. Michela Galante on behalf of the RIPE Atlas Team RIPE NCC

1 0

How to deal with inaccurate geocoding of probes
by Klaus Darilion 30 Dec '15

30 Dec '15

Hi! Inspired by https://perso.telecom-paristech.fr/~drossi/index.php?n=Dataset.Anycast I wanted to detect my Anycast locations using the Atlas probes. The problem is, that my results are only as accurate as the geocoding of the Atlas probes. For example probe #19273 is reported to be somewhere in Kansas. Bit the probe is only 5ms away from my LAX server and also traceroute indicates the probe is in LAX (traceroute to 63.84.150.1). So, now I am seeking some advice how to handle such problems. Is there some tag that indicates "verified location"? Any other ideas? Thanks Klaus

2 1

Ticket response times
by Micha Bailey 30 Dec '15

30 Dec '15

Hi, what's the average time for responses to atlas(a)ripe.net tickets? I've been waiting almost 2 months to hear back on 1193254, and was wondering if that's a typical wait time or if it fell between the cracks...

3 2

Anchor probes with broken lat/lon
by Klaus Darilion 29 Dec '15

29 Dec '15

https://atlas.ripe.net/api/v1/probe/6155/ "latitude": 2228.7695, "longitude": -4412.6105, https://atlas.ripe.net/api/v1/probe/6166/ "latitude": 2840.3705, "longitude": 631.8105, regards Klaus

2 1

Exploring the Idea of RIPE Atlas Virtual Probes
by Vesna Manojlovic 29 Dec '15

29 Dec '15

Dear colleagues, Some of you have asked about Virtual Probes on this list. Although we don't plan to make virtual probes available in 2016, we do plan to investigate this idea and develop some prototypes. Please find more details on RIPE Labs: https://labs.ripe.net/Members/suzanne_taylor_muzzin/exploring-the-idea-of-r… Kind regards, Vesna Manojlovic RIPE NCC

5 7

Support for arbitrary DNS queries
by Shumon Huque 26 Dec '15

26 Dec '15

I'd like to request the ability to have RIPE Atlas probes be able to issue DNS queries for arbitrary record types, and have that capability exposed in the API. I'm particularly interested in newer DANE record types like TLSA, OPENPGPKEY, SMIMEA, etc but a general purpose mechanism would be useful. Is this feasible? Are others interested in this capability? Thanks! Shumon Huque

11 19

13 new zones added to DNSMON
by Vesna Manojlovic 22 Dec '15

22 Dec '15

2 2

DNS measurement failed
by Maciej Andziński 16 Dec '15

16 Dec '15

Hi, Since yesterday I've been encountering a problem, many of the DNS measurements end with "failed" status. It happens for every measurement that tries to query 8.8.8.8, 8.8.4.4 or when using "Use the Probe's Resolver(s)" feature. However, everything works fine when querying a-dns.pl (194.181.87.156) server. Sample measurements: 3082732 3083505 3083581 Do you observe any issues related to the lack of available probes / exceeded limits? Many greetings, Maciej Andziński, NASK

3 4

Number of packets now ignored for ICMP tests?
by Stephane Bortzmeyer 16 Dec '15

16 Dec '15

I asked just one packet: {'definitions': [{'description': 'Ping 2001:67c:217c:6::2 from AS #3215', 'af': 6, 'packets': 1, 'type': 'ping', 'is_oneoff': True, 'target': '2001:67c:217c:6::2'}], 'probes': [{'requested': 500, 'type': 'asn', 'value': '3215', 'tags': {'include': ['system-ipv6-works']}}]} But, for the nine probes that were selected, I got 27 tests, which is the default of 3 packets per probe. Strange. Measurement #3083491

2 2