- ripe-atlas - mailman.ripe.net

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

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

Network configuration / Multiple VLANs
by Guillaume Sachot 27 Feb '14

27 Feb '14

Hi, I have just received my Atlas probe, and I have an issue for the IPv6 part. Its definitive IPv4 public address does not share the same VLAN with the IPv6 subnet. Would it be possible to add an optional VLAN field in the network configuration? Thank you, Regards. -- Guillaume SACHOT Oceanet Technology Administrateur système et réseau Support : +332 28 07 14 88

6 13

Thoughts on allowing newer DNS RR queries?
by Mark Delany 21 Feb '14

21 Feb '14

Outside of Atlas I've been doing a few tests to see how well CPE supports newer RR types. By newer I mean newer than AAAA. I'd like to do the same with the Atlas probes. Has there been discussion about being able to issue RR queries of newer types? On the query side, the Atlas device only needs to know enough to encode the type-value which could be supplied as a numeric if necessary. On the response side, a simple hex dump of the response would be good enough. I guess it's sort of a one-off test for most probes because once we know a probe and its intervening caches does or does not support a number of newer types, that situation is unlikely to require re-testing very often. So an alternative might be to make it a bootstrap sequence that the probe goes thru? Out of curiousity, how does the probe do the current DNS queries? Is it via dig or similar or is it coded into a program of some sort? Mark.

5 5

Easier access to bandwidth data of RIPE Atlas anchors
by Vesna Manojlovic 20 Feb '14

20 Feb '14

Dear RIPE Atlas community, we have added a small feature to the listing of RIPE Atlas anchors: https://atlas.ripe.net/anchors/list/ If you click on the hostname of the anchor (e.g. nl-ams-as3333), the link will take you to the graph of bandwidth, served by RIPEstat: https://stat.ripe.net/m/widget/atlas-probe-traffic#w.probe_id=6001&w.measur… This is the same graph that appears on the RIPE Atlas "probe page" of every anchor, but we decided to add a direct link to the bandwidth graph rather then to the whole probe page, since we are working on the improved version of it. The graph is zoomable, so you can see the whole year of data for older anchors; and it has other features described in this RIPE Labs article: https://labs.ripe.net/Members/becha/seismograph-and-other-new-ripe-atlas-fe… Hosts of RIPE Atlas anchors can access the same feature via their admin interface. Other features on this "list" page of RIPE Atlas anchors are: - sortable columns: you can sort by hostname, company name, city or country; in ascending and descending order - "clickable" links to anchoring measurement per anchor, per type We hope that this will give you more insight into the operations of RIPE Atlas anchors to date. We are still accepting applications from new hosts: https://atlas.ripe.net/get-involved/become-an-anchor-host/ Regards, Vesna

3 2