- ripe-atlas - mailman.ripe.net

Probe management sharing - LIR
by Abreu, Alexandre, Vodafone Portugal 08 Sep '15

08 Sep '15

Hi all I've shared the management of my probes using the LIR option. It worked fine for 2 LIR users (one of them is me and I now see the probes as "mine" and "shared with me") but one other LIR user doesn't see anything unless I specify his username explicitly. What kind of users are these? Aren't these the LIR users we can add on the LIR portal? Thanks in advance. Alexandre Abreu

1 0

Booking.com (Frankfurt DE, Hong Kong and Ashbury US) have joined the RIPE Atlas Anchors
by Alastair Strachan 08 Sep '15

08 Sep '15

Dear RIPE Atlas users, We're happy to announce that three more RIPE Atlas anchors have joined the network and are now available as targets for probe hosts conducting their own user-defined measurements. The new anchors are all hosted by Booking.com: de-fra-as43996, in Frankfurt (Germany) hk-hkg-as43996 in Hong Kong (Hong Kong) us-abn-as43996 in Ashburn (US) Anchoring measurements (ping, ping6, traceroute and traceroute6) are scheduled towards these anchors 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 RIPE NCC atlas(a)ripe.net <mailto:atlas@ripe.net>

1 0

Telus (CA) has joined RIPE Atlas anchors
by Lia Hestina 28 Aug '15

28 Aug '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 ca-van-as852 and it is hosted by TELUS in Vancouver, Canada. 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 atlas(a)ripe.net <mailto:atlas@ripe.net>

1 0

Missing module
by Jacques Lav!gnotte. 26 Aug '15

26 Aug '15

Hello, I am trying to run Stephane's B. resolv-name.py and I get : import RIPEAtlas ImportError: No module named RIPEAtlas I can't figure out where to get this module. Any help ? Jacques -- GnuPg : C8F5B1E3 WeUsePGP Because privacy matters http://weusepgp.info/

3 3

X.509 certificate monitoring
by Stephane Bortzmeyer 25 Aug '15

25 Aug '15

I do not find a lot of examples of X.509 certificate retrieving and analysis? I just committed <https://github.com/RIPE-Atlas-Community/ripe-atlas-community-contrib/blob/m…> which is useful for me when watching certificate expiration for anycasted sites (where the cert retrieved depends on the probe). Any other examples? And by the way, do not hesitate to submit your scripts to <https://github.com/RIPE-Atlas-Community/ripe-atlas-community-contrib> (fork and pull request, or open an issue with the attached script).

1 0

Re: [atlas] Question about "location setting" of RIPE Atlas
by Tomáš Hetmer 23 Aug '15

23 Aug '15

Hi, I'd use the simplest logical interpretation and enter the actual physical location no matter if the actual interconnect is right there, 900 km away or transmitted from a satellite. Also, if you placed it to that location 900km away you wouldn't skew the results for your own town, but anyone measuring the latency there would see a +20ms difference from reality, so that doesn't improve anything. Many networks are large and complex, such as an ADSL for a whole country being connected to the net via a local MPLS network via a central point at one main location - should you use that one for all the probes in the country? Of course not, you enter wherever the endpoint is. If you'd like however, you can mention your specific configuration in the probe details. That's my personal view on this, others might differ. Regards Tomáš Hetmer 2015-08-22 23:42 GMT+02:00 Anurag Bhatia <me(a)anuragbhatia.com>: > I have been hosting one of RIPE probes and recently I have switched over my > ISP. > > > Basically my previous ISP provider was regular ISP network with full L3 PoPs > nearby but in my new setup I have got a point to point to a city 900km away > and getting IP transit over there. > > > Now under such case, I am "technically" customer of that network. Should I > still keep my location as I have current one or better update it to that new > location 900km away? > > > The latency of course is low (as it is provisioned on fiber and hence just > 20ms roundtrip) but I think it will confuse off stats if anyone considers to > use this probe for any data in my region. > > > What you all think? Can someone recommend on correct location? > > > > Thanks. > > -- > > > Anurag Bhatia > anuragbhatia.com > > > PGP Key Fingerprint: 3115 677D 2E94 B696 651B 870C C06D D524 245E 58E2

1 0

Afilias, Los Angeles, CA, United States has joined RIPE Atlas anchors
by Eamonn Lane 21 Aug '15

21 Aug '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-lax-as63403 and is hosted by Los Angeles, CA, United States. 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

: Afilias, Ashburn, VA 20147, United States has joined RIPE Atlas anchors
by Eamonn Lane 21 Aug '15

21 Aug '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-qas-as393246 and is hosted by Afilias, Ashburn, VA 20147, United States. 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

Afilias (US, Ashburn and Los Angeles) have joined RIPE Atlas anchors
by Michela Galante 20 Aug '15

20 Aug '15

Dear RIPE Atlas users, We're happy to announce that two more RIPE Atlas anchors have joined the network and are now available as targets for probe hosts conducting their own user-defined measurements. The new anchors, both hosted by Afilias in United States, are: us-qas-as393246, in Ashburn (Virginia) us-lax-as63403, in Los Angeles (California) Congratulations to Afilias for their second and third anchor online! Anchoring measurements (ping, ping6, traceroute and traceroute6) are scheduled towards these anchors 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

Case sensitive DNS queries from the probe
by Yang Yu 19 Aug '15

19 Aug '15

Hello, Looking through DNS queries log I saw tons of queries from the probe for case sensitive names. Can someone please enlighten me what the possible use cases are? query: wWw.FacebOOK.COm IN A query: wWW.Wikia.COM IN A query: WwW.wIkIA.cOM IN A query: POOl.NTP.ORg query: Www.wikiA.CoM IN A query: wWW.FacebOoK.COM IN A query: wWw.faCeBOoK.cOM IN A Yang

7 15