- ripe-atlas - mailman.ripe.net

Glitch in measurements today?
by Stephane Bortzmeyer 31 Jan '15

31 Jan '15

Many: {u'id': 7, u'name': u'Failed'} when querying measurements. It seems OK, now.

1 0

Implementing new RIPE Atlas Service Terms and Conditions
by Vesna Manojlovic 30 Jan '15

30 Jan '15

Dear colleagues, As agreed on the MAT-WG mailing list, we are in the process of implementing the new RIPE Atlas Service Terms and Conditions that clearly state the role and responsibilities for the RIPE NCC, RIPE Atlas hosts and users: https://atlas.ripe.net/legal/terms-conditions/ This is the implementation plan: - End of January, existing probe hosts will be notified by email about the upcoming transition to the new terms and conditions. - From next week (during February), existing users and probe hosts will be presented with a banner when they log in to the RIPE Atlas website, to inform them of the upcoming transition. - As of 2 March 2015, the new RIPE Atlas Service Terms and Conditions will come into effect; new probe hosts will be asked to agree to the new terms and conditions when applying for a probe; all existing probe hosts will be subject to the new terms and conditions. Thank you for your feedback and for helping us to refine these new terms. Regards, Vesna Manojlovic Measurements Community Building RIPE NCC

1 1

Hitech Service LLC (Kiev, Ukraine) has joined RIPE Atlas Anchors
by Alastair Strachan 27 Jan '15

27 Jan '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 ua-iev-as29632 and it is hosted by Hitech Service LLC in Kiev, Ukraine). 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

VNET a.s. (Bratislava, Slovakia) has joined RIPE Atlas Anchors
by Alastair Strachan 23 Jan '15

23 Jan '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 sk-bts-as29405 and it is hosted by VNET a.s. in Bratislav, Slovakia. 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

Proposal for public HTTP measurements
by Robert Kisteleki 22 Jan '15

22 Jan '15

Dear RIPE Atlas users, The topic of publicly available HTTP measurements in RIPE Atlas comes up from time to time. There were a number of discussions about pros and cons for this feature over the years (including exposing probe hosts to unnecessary risks of other users "measuring" just about any kind of HTTP content out there), with no firm outcome. While we understand that this feature would come handy for some of our users, it does not benefit everyone. Therefore our proposal is the following: 1. We'll enable HTTP measurements to be performed by all atlas users, from any probes. 2. The targets of such measurements can only be RIPE Atlas anchors (these already run HTTP servers, see https://atlas.ripe.net/docs/anchors/) 3. Parameters like costs, minimum frequency, maximum number of probes involved, etc. will be set by the development team, just as with the other measurements. 4. The RIPE NCC will still be able to support other, vetted HTTP measurements as long as it benefits the community, as well as other HTTP measurements that we deem operationally useful. These will be evaluated on a case by case basis. Please speak up at the MAT working group list (mat-wg(a)ripe.net) if you support / don't support this proposal, of if you have any other opinion about it. Regards, Robert Kisteleki RIPE NCC R&D manager, for the RIPE Atlas team

10 15

Re: [atlas] problems creating measurements with old web interface
by Massimo Candela 21 Jan '15

21 Jan '15

Hi, Thanks for the feedback! > > Subject: [atlas] problems creating measurements with old web interface > Date: Wed, 21 Jan 2015 13:49:48 +0100 > From: Klaus Darilion <klaus.mailinglists(a)pernau.at> > To: ripe-atlas(a)ripe.net > > Hi! > > Today I created some DNS tests with the old web interface. The creation > process was fine, but the measurements did not work. (my target was > ignored and "use probe's resolver" was automatically enabled). > See UDMs: 1841832, 1841839, 1841840 > > btw: I can not stop 1841839 and 1841840 via the new web interface > > > The DNS measurements only work if I create them via the new web interface. > > > regards > Klaus > > PS: IMO the new web interface is not very user friendly when choosing > the probes - eg I failed to select 100 probes word wide (how to do this > in the map)? You can do it by searching for “worldwide” (there is autosuggestion) and the widget will ask the number of probes and the tags you want to use. The number of probes is suggested and bounded according to the maximum number of probes selectable for the measurement. The idea is that whatever you write in the text field, it will try to help/guide you creating the valid (and, if needed, complex) selection you were looking for. E.g. you can do a combination by searching for “Canada ipv6” to select all the ipv6 probes in Canada Of course it can be improved, so let us know if you have other feedback! Best regards, Massimo > It would be nice to have a textual alternative as my > browser gets incredibly slow when showing all the probes on the map. > > > >

1 0

One hundred RIPE Atlas anchors online
by Vesna Manojlovic 16 Jan '15

16 Jan '15

Dear all, You have been hearing about each RIPE Atlas anchor as they get activated - and now we have reached a milestone with one hundred anchors online! We wrote an article on RIPE Labs to cover all the details: https://labs.ripe.net/Members/suzanne_taylor_muzzin/one-hundred-ripe-atlas-… To apply for your own RIPE Atlas anchor: https://atlas.ripe.net/get-involved/become-an-anchor-host/ Kind regards, Vesna Manojlovic Measurements Community Building Team RIPE NCC

1 0

DK Hostmaster A/S (Ballerup, Denmark) has joined RIPE Atlas Anchors.
by Alastair Strachan 14 Jan '15

14 Jan '15

Dear RIPE Atlas users, We're very excited to announce that the 100th RIPE Atlas anchor has joined the network! This anchor is now available as a target for probe hosts conducting their own user-defined measurements. The new anchor is called dk-blp-as39839 and it is hosted by DK Hostmaster A/S in Ballerup, Denmark. 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

Nordiska Servercentralen (Solna, Sweden) has joined RIPE Atlas Anchors.
by Alastair Strachan 13 Jan '15

13 Jan '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 se-sln-as49515 and it is hosted by Nordiska Servercentralen in Solna, Sweden. 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

Deprecating the old measurement UI
by Robert Kisteleki 09 Jan '15

09 Jan '15

Dear all, In October last year, we introduced a new UI for browsing and scheduling measurements. For details, see: https://labs.ripe.net/Members/suzanne_taylor_muzzin/ripe-atlas-new-measurem… Your feedback about this was predominantly positive, and we’d like to thank everyone who helped this development with suggestions and bug reports. As stated at the time, we plan to deprecate and eventually remove the old interface (both the UI and the "API" it used). Our timeline is the following: 1. We'll make the new UI the default, and remove links to the old UI from the RIPE Atlas main menu, around 21 January. The old pages will still be accessible if one reaches them from somewhere else, such as a browser bookmark or hard-coded scripts. 2. Around the beginning of March, we'll remove the old pages from the system (/atlas/udm.html and related pages). This step will include the "deep links" that some of our users directly access to schedule and manage measurements from scripts (notably /atlas/*udm*.json). We'd like to encourage all of our users to switch to the new UI and API in the following weeks, if you haven't already done so. As always, we're happy to answer any questions or hear any feedback you might have. Regards, Robert Kisteleki, for the RIPE Atlas team

1 0