- ripe-atlas - mailman.ripe.net

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