- ripe-atlas - mailman.ripe.net

Fwd: Your RIPE Atlas Probe (ID: 22769) is not connected to our network
by Jonathan Brewer 06 Jul '15

06 Jul '15

Hi There, My probe 22769 appears to be malfunctioning, and I'm not sure what to do in terms of diagnostics. >From the router nearest it on the network: https://www.dropbox.com/s/ghe4e3tz69u1kvc/Screenshot%202015-07-07%2011.30.1… Looks to me as if it's rebooting frequently, but I have no way to check without an in-person visit. Do you have any suggestions as to how to troubleshoot? I have access to the network it's on. Thanks, Jon ---------- Forwarded message ---------- From: RIPE Atlas <no-reply(a)ripe.net> Date: 6 July 2015 at 07:40 Subject: Your RIPE Atlas Probe (ID: 22769) is not connected to our network To: jon.brewer(a)gmail.com Dear RIPE Atlas probe host, Thank you for participating in RIPE Atlas! We have noticed that your probe (#22769 with description MDC) is not connected to our infrastructure and has been disconnected since 2015-06-28 22:42 UTC. Could you please check whether everything is set up correctly on your side? If it is, and your probe is still reported as disconnected when you log in at https://atlas.ripe.net, please reply to this email so that we can follow up. You can review the instructions for setting up your probe at https://atlas.ripe.net/getting-started If you have any questions, please contact us at atlas(a)ripe.net Best regards, RIPE Atlas Team ********** You are receiving this message because you applied for or were given a RIPE Atlas probe. We will only send messages when your probe becomes disconnected for an extended period of time.

1 0

API to get information about a probe?
by Stephane Bortzmeyer 06 Jul '15

06 Jul '15

I cannot find an API to retrieve information about a probe. I would like to get the information I can see on, for instance, <https://atlas.ripe.net/probes/10644/> but from a REST + JSON API. Does it exist? Do you think it would be a nice addition? (My current use case is that I find some probes failing to ping a target and I would like to quickly check if they share something, such as ASn or some tags.)

2 3

Wrong IP prefix values accepted?
by Stephane Bortzmeyer 05 Jul '15

05 Jul '15

It seems there is no protection against wrong prefixes? See measurement #1897909, which started with JSON: {'definitions': [{'query_class': 'IN', 'description': 'DNS resolution of jihadmin.com from prefix foobar', 'af': 4, 'query_argument': 'jihadmin.com', 'query_type': 'A', 'type': 'dns', 'is_oneoff': True, 'recursion_desired': True, 'use_probe_resolver': True}], 'probes': [{'requested': 3, 'type': 'prefix', 'value': 'foobar'}]}

2 5

Fwd: [mat-wg] New on RIPE Labs: Improving RIPE Atlas Coverage. What Networks are Missing?
by Robert Kisteleki 02 Jul '15

02 Jul '15

Dear all, The following article might be of interest to you. Regards, Robert -------- Forwarded Message -------- Subject: [mat-wg] New on RIPE Labs: Improving RIPE Atlas Coverage. What Networks are Missing? Date: Thu, 02 Jul 2015 12:18:55 +0200 From: Mirjam Kuehne <mir(a)ripe.net> To: mat-wg(a)ripe.net Dear colleagues, In this article we compare RIPE Atlas deployment against user population estimates provided by APNIC to see what eyeball networks are missing out on RIPE Atlas probes: https://labs.ripe.net/Members/emileaben/improving-ripe-atlas-coverage-what-… Kind regards, Mirjam Kuehne RIPE NCC

1 0

Probe and measurement archives vs. the APIs
by Robert Kisteleki 02 Jul '15

02 Jul '15

Dear All, We've observed recently that some users are using scripts to "crawl" through all the metadata provided by the probe and measurement APIs. This means that some people out there download basically the entire probe and/or measurement meta data set the system provides. As you can imagine, this is highly inefficient and keeps our servers busy. We believe that there could be better solutions. We have been providing the downloadable archive for probe metadata for some time now, and recently we've added the measurement metadata too. You can now reach these at http://ftp.ripe.net/ripe/atlas/ This way one can even get complete sets of metadata as far back as January 2015 for measurement specifications and March 2014 for probe data. Given the existence of these archives, we will apply a sane limit on how much metadata can be reached via the APIs. In practice this means that the API will not allow fetching results beyond, say, 10.000 (i.e. 500 pages of 20) entries. This is after the application of filters, so for example with no filters at all you could still access metadata of the 10k newest measurements, while if you filter for DNS measurements only, you could get the 10k newest of those, and so on. We believe this keeps the metadata API useful for the majority of the users, while the existence of the archive serves the remaining cases. Our plan is to make this change around the end of July. Regards, Robert Kisteleki

1 0

RIPE Atlas traceroute visualisation - use cases
by Massimo Candela 01 Jul '15

01 Jul '15

Hello, We are creating a tool to visualise traceroute results coming from the RIPE Atlas measurement network. The tool will of course be available to everyone. To help make this tool as useful as possible, I’m gathering use cases of day-to-day operations and research activities that use traceroute measurements. I hope you can spend a few minutes to answer this email and tell me how you use traceroute measurements or what you would like to have in such a tool. For each use case you have in mind, please describe it briefly. Keep in mind our system can collect measurements from multiple sources to a single target repeatedly (e.g. every 60 seconds). Don’t focus only on traceroute data, but also on correlations among traceroutes and BGP, RTT, geolocations, DNS, and registry information (feel free to expand the list to other datasets). Thanks for your time. Your help is invaluable. Ciao, Massimo RIPE NCC

2 1

DHIRAAGU (Maldives) has joined RIPE Atlas anchors
by Michela Galante 30 Jun '15

30 Jun '15

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 mv-mle-as7642 and it is hosted by DHIRAAGU in Male, Maldives, and sponsored by APNIC. 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, RIPE Atlas Team atlas(a)ripe.net

1 0

Re: [atlas] vm image for ripe atlas probe ?
by Colin Johnston 30 Jun '15

30 Jun '15

low vm disk use is priority low vm memory is priority colin Sent from my iPhone > On 30 Jun 2015, at 11:15, RIPE Atlas <atlas(a)ripe.net> wrote: > >> On 2015-06-22 15:03, Colin Johnston wrote: >> any news on vm image for ripe atlas probe ? >> would be great to use as could monitor vm farms much better ? >> >> Colin. > > Dear all, > > We understand that some people asked for this feature. At the moment we're > evaluating it, and plan to come back to the community with a plan of action > before the end of August. It's possible that we'll post a couple of > clarification questions in the meantime. > > Regards, > Robert

1 0

vm image for ripe atlas probe ?
by Colin Johnston 30 Jun '15

30 Jun '15

any news on vm image for ripe atlas probe ? would be great to use as could monitor vm farms much better ? Colin.

5 4

Active probes
by Ben O'Hara 25 Jun '15

25 Jun '15

Hi, We currently pull https://atlas.ripe.net/contrib/active_probes.json as part of some analysis of atlas data, this seems to have gone missing since yesterday and now returns a 404. Is this known? Should it work? Will it come back? Cheers Ben BEN O'HARA Senior Network and Systems Engineer P +61 9866 3710 [Bombora Technologies Logo]<http://www.bomboratech.com.au/> www.bomboratech.com.au<http://www.bomboratech.com.au/> Follow us on Twitter<https://twitter.com/BomboraTech> The Bombora Technologies group of companies includes AusRegistry, ARI Registry Services, AusRegistry International and ZOAK Solutions. The information contained in this communication is intended for the named recipients only. It is subject to copyright and may contain legally privileged and confidential information and if you are not an intended recipient you must not use, copy, distribute or take any action in reliance on it. If you have received this communication in error, please delete all copies from your system and notify us immediately.

2 2

Probe update
by Laurent Dumont 23 Jun '15

23 Jun '15

Hi gents, Small update on the probe status. I've tried a 2A usb power adapter and no dice. The Power and WPS led come on and a ethernet link seems to be active between the probe and the switch. Unfortunately, there is no DHCP discover or any kind of network activity from the probe. Anything else I can try to troubleshoot this? Is there a LED guide somewhere? -- Laurent Dumont coldnorthadmin.com

2 1

Probe question - Issue
by Laurent Dumont 23 Jun '15

23 Jun '15

Hi gents, After some delay, I'm trying to setup the probe I received. Unfortunately, it seems that something is not quite working. Once it's plugged in and powered, there is no activity. There is no DHCP request for the probe so I can't see anything on the network side. Could something be wrong with the usb key? Is there a way I could reflash the usb key with the OS files? Thanks Laurent Dumont -- Laurent Dumont coldnorthadmin.com

3 4

Netzwerge Hamburg eK, Hamburg, Germany has joined RIPE Atlas anchors
by Eamonn Lane 23 Jun '15

23 Jun '15

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-ham-as201709 and is hosted by Netzwerge Hamburg eK, Hamburg, 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, RIPE Atlas Team RIPE NCC atlas(a)ripe.net

1 0

FHE3 Gmbh, Frankfurt Am Main, Germany has joined RIPE Atlas anchors
by Eamonn Lane 23 Jun '15

23 Jun '15

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-fra-as49024 and is hosted by FHE3 Gmbh, Frankfurt Am Main, 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, RIPE Atlas Team RIPE NCC atlas(a)ripe.net

1 0

Enabling Data Compression in RIPE Atlas
by Vesna Manojlovic 19 Jun '15

19 Jun '15

Dear colleagues, We’d like to enable gzip compression on all of RIPE Atlas' measurement API calls — but thanks to the BREACH vulnerability, doing so could mean that some enterprising individual with an obscene amount of time on their hands might be able read the contents of the responses. This means measurement results as well as metadata for measurements — including the small number of measurements not marked as “public”. We believe the drawbacks are negligible, but we’re looking for community support. Find out more in this RIPE Labs article: https://labs.ripe.net/Members/daniel_quinn_39/enabling-data-compression-in-… Regards, Vesna Manojlovic

1 0

atlas anchor DANE records
by Bjørn Mork 17 Jun '15

17 Jun '15

Hello, I just noticed "We also generate a DANE record for each anchor" in the docs and became instantly curious. There aren't that many DANE records out there in the wild :) The records seem to be pointing to a self signed certificate (as documented), but with 'usage' = 1 instead of 3 as expected. At least the two records I looked at had this - I assume they are all created the same way. Is this intentional? It makes 'normal' verification fail: bjorn@canardo:~$ tlsa --debug --verify nl-ams-as3333.anchors.atlas.ripe.net Received the following record for name _443._tcp.nl-ams-as3333.anchors.atlas.ripe.net.: Usage: 1 (End-Entity Constraint + chain to CA) Selector: 0 (Certificate) Matching Type: 1 (SHA-256) Certificate for Association: 88422d55424ca8f6f74e165016851cb195fc0919f82f8762574a4d71868964e9 This record is valid (well-formed). Attempting to verify the record with the TLS service... Got the following IP: 193.0.19.107 FAIL (Usage 1): Certificate offered by the server matches the one mentioned in the TLSA record but the following error was raised during PKIX validation: X509_V_ERR_DEPTH_ZERO_SELF_SIGNED_CERT The matched certificate has Subject: /C=nl/ST=ams/L=ams/O=as3333/CN=nl-ams-as3333.anchors.atlas.ripe.net Got the following IP: 2001:67c:2e8:11::c100:136b FAIL (Usage 1): Certificate offered by the server matches the one mentioned in the TLSA record but the following error was raised during PKIX validation: X509_V_ERR_DEPTH_ZERO_SELF_SIGNED_CERT The matched certificate has Subject: /C=nl/ST=ams/L=ams/O=as3333/CN=nl-ams-as3333.anchors.atlas.ripe.net bjorn@canardo:~$ tlsa --debug --verify se-sto-as8674.anchors.atlas.ripe.net Received the following record for name _443._tcp.se-sto-as8674.anchors.atlas.ripe.net.: Usage: 1 (End-Entity Constraint + chain to CA) Selector: 0 (Certificate) Matching Type: 1 (SHA-256) Certificate for Association: 2d92e341d2181011c520ad92229155e1350fc4f7b9e628198be1f9589ec7a53f This record is valid (well-formed). Attempting to verify the record with the TLS service... Got the following IP: 185.42.136.158 FAIL (Usage 1): Certificate offered by the server matches the one mentioned in the TLSA record but the following error was raised during PKIX validation: X509_V_ERR_DEPTH_ZERO_SELF_SIGNED_CERT The matched certificate has Subject: /O=AS8674/L=STO/C=SE/CN=se-sto-as8674.anchors.atlas.ripe.net Got the following IP: 2a01:3f0:0:60::5 FAIL (Usage 1): Certificate offered by the server matches the one mentioned in the TLSA record but the following error was raised during PKIX validation: X509_V_ERR_DEPTH_ZERO_SELF_SIGNED_CERT The matched certificate has Subject: /O=AS8674/L=STO/C=SE/CN=se-sto-as8674.anchors.atlas.ripe.net What is the intended use of these records? And why doesn't https://atlas.ripe.net/ have a DANE record as well? :) Bjørn

1 0

HTTP Measurements with RIPE Atlas
by Vesna Manojlovic 17 Jun '15

17 Jun '15

Dear colleagues, After a discussion with the community about HTTP measurements, RIPE NCC will start implementing this as a publicly available measurement type. Please find some more information on RIPE Labs: https://labs.ripe.net/Members/kistel/http-measurements-with-ripe-atlas Kind regards, Vesna Manojlovic RIPE NCC

3 2

Atlas Anchors and LogJam
by Ben O'Hara 15 Jun '15

15 Jun '15

Hi, We host an Atlas Anchor, but our network monitoring still shows it being vulnerable to Logjam. Can you please let us know when this will be upgraded to fix the vulnerability? Cheers BEN O'HARA Senior Network and Systems Engineer P +61 9866 3710 [Bombora Technologies Logo]<http://www.bomboratech.com.au/> www.bomboratech.com.au<http://www.bomboratech.com.au/> Follow us on Twitter<https://twitter.com/BomboraTech> The Bombora Technologies group of companies includes AusRegistry, ARI Registry Services, AusRegistry International and ZOAK Solutions. The information contained in this communication is intended for the named recipients only. It is subject to copyright and may contain legally privileged and confidential information and if you are not an intended recipient you must not use, copy, distribute or take any action in reliance on it. If you have received this communication in error, please delete all copies from your system and notify us immediately.

2 1

Notifications for unreachable probes
by Peter Eckel 10 Jun '15

10 Jun '15

Hi, I have set up a notification if my probe 10293 is down for more than 15 minutes. Since my main mail address is located on a server likely to be unavailable if the probe is down, the notification was set to a different mail address not in the same network. Unfortunately it seems that the notification address is ignored, and the notification is sent to the reporting address instead. Does anyone else see that problem as well? Regards, Peter.

2 1

ADP, Saint-Denis, France has joined RIPE Atlas anchors
by Eamonn Lane 08 Jun '15

08 Jun '15

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 fr-ysd-as201958 and is hosted by : ADP, Saint-Denis, in France. 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, RIPE Atlas Team RIPE NCC atlas(a)ripe.net

1 0

Conova Communications GmbH, Salzburg, Austria has joined RIPE Atlas anchors
by Eamonn Lane 08 Jun '15

08 Jun '15

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 at-szg-as5404 and is hosted by : Conova Communications GmbH in Salzburg, Austria . 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, RIPE Atlas Team RIPE NCC atlas(a)ripe.net

1 0

ASTI (Philippines) has joined RIPE Atlas anchors
by Michela Galante 04 Jun '15

04 Jun '15

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 ph-qzt-as9821 and it is hosted by ASTI in Quezon City, Philippines, and sponsored by APNIC. 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, RIPE Atlas Team atlas(a)ripe.net

1 0

COMSATS Internet Services (Pakistan) has joined RIPE Atlas anchors
by Michela Galante 04 Jun '15

04 Jun '15

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 pk-isb-as7590 and it is hosted by COMSATS Internet Services in Islamabad, Pakistan, and sponsored by APNIC. 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, RIPE Atlas Team atlas(a)ripe.net

2 1

Matrix DATA (NL) has joined RIPE Atlas Anchors
by Alastair Strachan 28 May '15

28 May '15

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 nl-hrd-as34612 and it is hosted by Matrix DATA in Harderwijk (NL) 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/ <https://atlas.ripe.net/anchors/list/> Learn more about RIPE Atlas anchors at: https://atlas.ripe.net/about/anchors/ <https://atlas.ripe.net/about/anchors/> Thank you for participating in RIPE Atlas! Kind Regards, RIPE Atlas Team

1 0

ICANN (US) has joined RIPE Atlas Anchors
by Alastair Strachan 28 May '15

28 May '15

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 us-rtv-as16876 and it is hosted by ICANN in Reston (US) 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/ <https://atlas.ripe.net/anchors/list/> Learn more about RIPE Atlas anchors at: https://atlas.ripe.net/about/anchors/ <https://atlas.ripe.net/about/anchors/> Thank you for participating in RIPE Atlas! Kind Regards, RIPE Atlas Team

1 0

Atlas and TLSA RR's?
by Rose, Scott W. 26 May '15

26 May '15

Hello, We have a TLSA test tool called DANELaw (https://www.had-pilot.com/dane/danelaw.html). The tool basically check for a TLSA RR for a given domain name and makes sure it matches the presented TLS certificate. Over the last few days we noticed a large volume of tests for TLSA RR's ending in "anchor.atlas.ripe.net". This isn't a big deal (except for our crude logging system), just wondering if this is a self-check, or some test. Also, our tool isn't really a production service, so if it goes down - will it effect anything? Scott =================================== Scott Rose NIST scott.rose(a)nist.gov +1 301-975-8439 Google Voice: +1 571-249-3671 http://www.dnsops.gov/ https://www.had-pilot.com/ ===================================

2 1

Marist College (US) has joined RIPE Atlas Anchors
by Alastair Strachan 22 May '15

22 May '15

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 us-pou-as6124 and it is hosted by Marist College in Poughkeepsie, US. 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/ <https://atlas.ripe.net/anchors/list/> Learn more about RIPE Atlas anchors at: https://atlas.ripe.net/about/anchors/ <https://atlas.ripe.net/about/anchors/> Thank you for participating in RIPE Atlas! Kind Regards, RIPE Atlas Team

1 0

Big latency change
by Daniel Baeza (Red y Sistemas TVT) 21 May '15

21 May '15

Hi folks, How can I check what happened at 13:00 (Dont know if the time in my probe is UTC or UTC+2) of today in the a.root-servers.net? My latency with the a-root changed from 117 to 45ms and Im curious of what happened. I've took a look in the RIPEstat routing for the IP Address of the root server, and at the same time the BGP had changes, but there are too many AS involved I cant follow it. Thanks in advance! -- Daniel Baeza

4 4

ALTUSHOST B.V. in Dronten (NL) has joined RIPE Atlas Anchors
by Alastair Strachan 21 May '15

21 May '15

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 nl-dro-as51430 and it is hosted by ALTUSHOST B.V. in Dronten (NL). 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/ <https://atlas.ripe.net/anchors/list/> Learn more about RIPE Atlas anchors at: https://atlas.ripe.net/about/anchors/ <https://atlas.ripe.net/about/anchors/> Thank you for participating in RIPE Atlas! Kind Regards, RIPE Atlas Team

1 0

ICANN in El Segundo (US) has joined RIPE Atlas Anchors
by Alastair Strachan 21 May '15

21 May '15

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 us-els-as40528 and it is hosted by ICANN in El Sugundo. 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/ <https://atlas.ripe.net/anchors/list/> Learn more about RIPE Atlas anchors at: https://atlas.ripe.net/about/anchors/ <https://atlas.ripe.net/about/anchors/> Thank you for participating in RIPE Atlas! Kind Regards, RIPE Atlas Team

1 0

University Carlos III of Madrid, Leganes, Spain has joined RIPE Atlas anchors
by Eamonn Lane 15 May '15

15 May '15

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-leg-as766 and is hosted by University Carlos III of Madrid, Leganes, 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, RIPE Atlas Team RIPE NCC atlas(a)ripe.net

1 0

Invalid JSON because of DNS TXT records
by Stephane Bortzmeyer 15 May '15

15 May '15

The DNS, as we know, is a jungle. People put anything in their TXT records, even control characters. Atlas faithfully returns this content in the JSON files (see measurement #2004707). Then they are no longer legal JSON (RFC 7159, section 7) and crash the JSON libraries. Who should fix it? My first guess is that Atlas should not produce illegal JSON files and therefore should escape such texts.

2 1

New on RIPE Labs: AMS-IX Outage during RIPE70 as Seen with RIPE Atlas
by Vesna Manojlovic 14 May '15

14 May '15

FYI -------- Forwarded Message -------- Subject: [mat-wg] New on RIPE Labs: AMS-IX Outage during RIPE 70 as Seen with RIPE Atlas Date: Thu, 14 May 2015 17:20:21 +0200 From: Mirjam Kuehne <mir(a)ripe.net> To: mat-wg(a)ripe.net Dear colleagues, Please find this new article on RIPE Labs including some visualisations of yesterday's AMS-IX network outage: https://labs.ripe.net/Members/kistel/the-ams-ix-outage-as-seen-with-ripe-at… Kind regards, Mirjam Kuehne RIPE NCCC

1 0

M-net Telekommunikations GmbH in Munich has joined RIPE Atlas Anchors
by Alastair Strachan 14 May '15

14 May '15

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-muc-as8767 and it is hosted by M-net Telekommunikations GmbH in Munich 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/ <https://atlas.ripe.net/anchors/list/> Learn more about RIPE Atlas anchors at: https://atlas.ripe.net/about/anchors/ <https://atlas.ripe.net/about/anchors/> Thank you for participating in RIPE Atlas! Kind Regards, RIPE Atlas Team

1 0

Wikia in San Jose, USA has joined RIPE Atlas Anchors
by Alastair Strachan 06 May '15

06 May '15

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 us-sjc-as22300 and it is hosted by Wikia in San Jose (USA) 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/ <https://atlas.ripe.net/anchors/list/> Learn more about RIPE Atlas anchors at: https://atlas.ripe.net/about/anchors/ <https://atlas.ripe.net/about/anchors/> Thank you for participating in RIPE Atlas! Kind Regards, RIPE Atlas Team

1 0

Geographic Selection of Probe
by Graham Beneke 28 Apr '15

28 Apr '15

Hi All Due to the huge number of probes in Europe there is always a heavy bias when selecting "whole world" for UDMs. In the past I could get around this by requesting numbers of probes from each region/continent. I can't figure out how to do this on the new interface. Using the wizard there does not seem to be a way to request a random subset of probes within the area selected. When using the manual probe selection I can't find what area codes I can use besides "WW" Am I missing something? -- Graham Beneke graham(a)apolix.co.za

2 1

New on RIPE Labs: Measuring Countries and IXPs in the SEE Region
by Vesna Manojlovic 24 Apr '15

24 Apr '15

Dear all, In this post we look at 10 countries in South East Europe and see how we can use RIPE Atlas to get a sense of routing and the interconnectedness of networks in these countries: https://labs.ripe.net/Members/emileaben/measuring-countries-and-ixps-in-the… Two prototype tools used here can benefit from your feedback & involvement: IXP-Jedi & OpenIPMap. Please take some time to play with the interactive grid (IXP-Jedi), e.g. for Romania: http://sg-pub.ripe.net/emile/ixp-country-jedi/RO-2015-04/ixpcountry/ Code: https://github.com/emileaben/ixp-country-jedi/ Or join the OpenIPMap to crowdsource geolocation of IP infrastructure: https://github.com/RIPE-Atlas-Community/openipmap Kind regards, Vesna

1 0

IPv6 auto-tagging failure?
by Bjørn Mork 21 Apr '15

21 Apr '15

Hello, I'm wondering a bit about the IPv6 auto-tagging. I recently reveived a v3 probe and connected it to a dual-stack enabled network. The probe was initially tagged as 2015-04-16 20:23 UTC Probe auto-tagged Your probe #22894 was automatically tagged as "system: IPv6 Capable" but then (on the next batch run?, after a couple of quick firmware upgrades (3.3.8 => 4650 => 4680): 2015-04-17 08:23 UTC Probe auto-untagged Your probe #22894 was automatically untagged as "system: IPv6 Capable" and there it has been since. This wouldn't worry me too much if it otherwise worked, but I noticed that the probe isn't listed with an "ASN v6" either. So I assume the missing tag prevents it from being used for v6 probing? AFAICS, the probe does take the announced prefix, and is actually *using* the provided IPv6 connectivity. The "Connection History" shows that it consistently uses its SLAAC address to connect to the controller. So why isn't it tagged as IPv6 capable/works etc? In desperation I tried different netwrok settings, static address, adding v6 DNS, and fiddling with the managed/other flags along with matching DHCPv6 config. Made no difference of course. If I understood correctly, the probe firmware won't currently do any DHCPv6, and v6 DNS is optional as long as there is a working v4 resolver available. Bjørn

3 2

RIPE Atlas accounting system renewal
by Robert Kisteleki 20 Apr '15

20 Apr '15

Dear Users, Today we're renewing our internal accounting system in RIPE Atlas. This change is almost exclusively internal, it hardly shows up on the public pages. If you see discrepancies regarding your credits tomorrow, then please let us know at atlas(a)ripe.net (ie. NOT this mailing list) so we can check. We'll privately contact the few users where we expect a more visible change. Regards, Robert & Johan & the rest of the team

1 0

Error when adding a measurement
by Edd Barrett 17 Apr '15

17 Apr '15

Hey, A friend offered me a v3 probe, and I am currently playing around with it, exploring what I can do. I think there may be a bug in the measurements setup process. When I try to add a measurement, I get a message: "AccBalance matching query does not exist." This is not a very user friendly message. Perhaps this is suggesting that I don't have enough credit? This leads me to another potential problem. On the landing page, after I login, there is a credit summary consisting of two icons and a kind of pie chart. If I mouseover "current balance" it says 0. If I click it, the resulting page says I have 50,000 credits (the welcome bonus). I suspect that I can't setup the measurement because some part of the system thinks I have no credit. Cheers -- Best Regards Edd Barrett http://www.theunixzoo.co.uk

2 1

Accounting switch
by Johan ter Beest 17 Apr '15

17 Apr '15

Dear Atlas users, We are in the middle of switching the accounting back-end. We expect this work to be finished by next week: Tuesday, April 21. There are two spots where you would be impacted: - Transferring credits Credits transferred will show up in the new system but not in the old. We have temporarily disabled the transferring of credits using the website. If you need to have some credits transferred urgently, you can email us at atlas-dev(a)ripe.net and we will make the transfer for you - When you register a new probe and are a first time probe host (ie, you have no credits at all) The 50.000 credits welcome bonus is applied to the new system while the measurements scheduling checks the old system resulting in an error. This is a fairly rare scenario as most of our hosts have credits already. When we spot this, we will contact the host and adjust his credits manually. There will be no danger of losing credits or measurements being stopped accidentally as a result of this switch. Thank you for your patience while we make this switch. Kind regards, Johan ter Beest RIPE Atlas Team

1 0

Anexia Internetdienstleistungs Gmbh, Klagenfurt, Austria has joined RIPE Atlas anchors
by Eamonn Lane 17 Apr '15

17 Apr '15

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 at-klu-as42473 and is hosted by Anexia Internetdienstleistungs Gmbh in Klagenfurt, Austria. 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, RIPE Atlas Team RIPE NCC atlas(a)ripe.net

1 0

NZ Registry Services, Aukland, New Zealand has joined RIPE Atlas anchors
by Eamonn Lane 17 Apr '15

17 Apr '15

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 nz-lyj-as17746 and is hosted by NZ Registry Services in Aukland, New Zealand. 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, RIPE Atlas Team RIPE NCC atlas(a)ripe.net

1 0

negative RTT?
by Paul Vlaar 17 Apr '15

17 Apr '15

Hi all, I noticed that one of my DNS UDMs gave back a negative RTT: {"af":4,"dst_addr":"199.19.57.1","from":"171.98.64.220","fw":4680,"group_id":1957244,"lts":39041,"msm_id":1957244,"msm_name":"Tdig","prb_id":22726,"proto":"UDP","result":{"ANCOUNT":1,"ARCOUNT":1,"ID":8401,"NSCOUNT":0,"QDCOUNT":1,"abuf":"INGEAAABAAEAAAABA29yZwAABgABwAwABgABAAADhAAzAmEwA29yZwthZmlsaWFzLW5zdARpbmZvAANub2PAKHfkW2sAAAcIAAADhAAJOoAAAVGAAAApEAAAAAAAACYAAwAibnMwMDBiLmFwcDI3LmlhZDEuYWZpbGlhcy1uc3QuaW5mbw==","answers":[{"MNAME":"a0.org.afilias-nst.info.","NAME":"org.","RNAME":"noc.afilias-nst.info.","SERIAL":2011454315,"TTL":900,"TYPE":"SOA"}],"rt":-14281.576,"size":133},"src_addr":"192.168.1.51","timestamp":1428948041,"type":"dns"} -14281.576ms was standing out like a sore thumb on the graph that I create out of the results from these UDMs. This is quite interesting, maybe messages from the future? :) Anyone else ran into one of these? ~paul

3 3

University of Niš (RSINI) has joined RIPE Atlas anchors
by Eamonn Lane 13 Apr '15

13 Apr '15

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 rs-ini-as13303 and is hosted by University of Niš in Niš, Serbia. 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, RIPE Atlas Team RIPE NCC atlas(a)ripe.net

1 0

Read about the results of RIPE Atlas data visualization hackathon in the new RIPE Labs article
by Vesna Manojlovic 10 Apr '15

10 Apr '15

Dear all, In March 2015, a diverse group of contributors got together to come up with creative ways to visualise the health of the Internet using RIPE Atlas open measurements data. It was the first RIPE Atlas hackathon. Impressive results were hacked together by programmers, designers and operators during an intensive weekend of work and fun in Amsterdam. In this article we celebrate hackathon achievements, document and promote hackathon results, create a memento for participants and report in detail for the benefit of the rest of the community: https://labs.ripe.net/Members/becha/ripe-atlas-hackathon-results Numbers * We received more than 70 applications for participation * Present: 24 participants & one no-show, 6 jury members and 11 support staff (coincidentally: 42!) * 6 out of 25 participants were female (24%) * 3 jury members were female (50%!) * Ten final projects were presented * Four projects were awarded prizes * 14 free & open source software projects were published on GitHub * 20 litres of tea were consumed * 10 large pizzas were eaten for lunch on Saturday * Two kilograms of chocolate Easter Eggs were munched up * 12 Club-Mate bottles were emptied Links: - All code: RIPE Atlas community pages on GitHub: https://github.com/RIPE-Atlas-Community/ripe-atlas-community-contrib/blob/m… - Videos: on RIPE NCC YouTube channel https://www.youtube.com/user/RIPENCC/videos?shelf_id=0&view=0&sort=dd - Hackathon presentations and code: https://labs.ripe.net/Members/becha/ripe-atlas-hackathon-presentations More links & photos in the article... https://labs.ripe.net/Members/becha/ripe-atlas-hackathon-results Share & Enjoy! Vesna

1 0

list of country codes / UDM via API limit
by Paul Vlaar 09 Apr '15

09 Apr '15

Hi all, is there a list of country codes that have active probes in them? I've used the ISO3166 list but am finding that many CCs do not have probes in them, so setting up those UDMs is moot. I am also running into what appears to be the limitation of the amount of UDMs that I'm allowed to setup using the API: around 25. Has anyone else run into that limit? Is there a way to raise that limit somehow? Thanks, ~paul

4 3

survey on performance measurement platforms and related standards
by Bajpai, Vaibhav 08 Apr '15

08 Apr '15

Dear RIPE Atlas WG, I would like to share something with you today. As you know, IETF LMAP [1] is making efforts to standardize large-scale measurements to allow divergent measurement platforms to converge towards interoperability. Early discussions within this group often lead to folks asking for feature sets and possibilities of each contemporary performance measurement platform. So we started digging literature work in this space and found that although there were surveys on topology-based measurement platforms (such CAIDA Ark et al.); literature work on performance measurement platforms (such as RIPE Atlas, SamKnows et al.) was missing. Therefore, we started writing such a survey in 2013 to plug this gap and also complement this with current state of IETF standardization efforts happening within the LMAP and IPPM working groups. This work got published and came online this week. I thought would share this with you: ----------------8<-----------------8<-----------------8<-----------------8< A Survey on Internet Performance Measurement Platforms and Related Standardization Efforts Vaibhav Bajpai, Jürgen Schönwälder IEEE Communications Surveys & Tutorials April, 2015 A number of Internet measurement platforms have emerged in the last few years. These platforms have deployed thousands of probes at strategic locations within access and backbone networks and behind residential gateways. In this paper we provide a taxonomy of these measurement platforms on the basis of their deployment use-case. We describe these platforms in detail by exploring their coverage, scale, lifetime, deployed metrics and measurement tools, architecture and overall research impact. We conclude the survey by describing current standardization efforts to make large-scale performance measurement platforms interoperable. DOI: http://dx.doi.org/10.1109/COMST.2015.2418435 Author Copy: http://vaibhavbajpai.com/documents/papers/proceedings/lsmp-comst-2015.pdf ----------------8<-----------------8<-----------------8<-----------------8< Thanks! [1] https://datatracker.ietf.org/wg/lmap Best, Vaibhav ===================================================== Vaibhav Bajpai Research I, Room 91 Computer Networks and Distributed Systems (CNDS) Lab School of Engineering and Sciences Jacobs University Bremen, Germany www.vaibhavbajpai.com =====================================================

1 0

TNNet Oy Ltd (FI JYV)has joined RIPE Atlas anchors
by Eamonn Lane 02 Apr '15

02 Apr '15

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 fi-yyv-as30798 and is hosted by TNNet Oy Ltd in Jyvaskyla, Finland. 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, RIPE Atlas Team RIPE NCC atlas(a)ripe.net

1 0

Finding out the number of simultaneous measurements
by Sebastian Castro 01 Apr '15

01 Apr '15

Hi: While running some measurements for a research work we are doing, I encountered this error "You can't have more than 100 simultaneous measurements". I'm not surprised, because I have some long term measurements running, but the bulk of them are one-off. Although I could throttle my measurements in little batches, I would prefer a way to programmatically query Atlas and find out how many measurements I'm running. The API allows you to get the list of public measurements, but running the query with an API key for my account doesn't change the output. Is there a way to do this with the API? Cheers, -- Sebastian Castro Technical Research Manager NZRS Ltd. desk: +64 4 495 2337 mobile: +64 21 400535

2 1