- mat-wg - mailman.ripe.net

New on RIPE Labs: Visualisation of a New Node in LACTLD Anycast Service
by Mirjam Kuehne 10 Jul '15

10 Jul '15

Dear colleagues, Please read on RIPE Labs how RIPE Atlas was used to measure improvements to the LACTLD infrastructure (by Hugo Salgado): https://labs.ripe.net/Members/hugo_salgado/visualisation-of-a-new-node-in-l… Kind regards, Mirjam Kuehne RIPE NCC

1 0

New on RIPE Labs: Improving RIPE Atlas Coverage. What Networks are Missing?
by Mirjam Kuehne 02 Jul '15

02 Jul '15

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

Re: [mat-wg] feature request: have stat report on transitted prefixes
by Christian Teuschel 30 Jun '15

30 Jun '15

Dear colleagues, I wanted to follow-up on Job's feature request, about RIPEstat also displaying prefixes transited by an ASN, since several of you also said you would find this feature useful. Supporting this feature will require some work on RIPEstat's front-end as well as on the back-end (our Hadoop storage platform). Implementing this for all available historic RIS data would have a large impact on our storage capacity. However, we will be able to implement this feature for a sliding window of 30 days, as you suggested. So RIPEstat will be able to show the prefixes for which an ASN provided transit during the previous 30 days. At the moment I don't have a concrete delivery date for this feature, but we will merge the necessary development work into our work plan and let you know before the end of June when we expect to be able to support this feature in RIPEstat. We will make sure it is implemented before RIPE 71 in November. Please let me know if you have any further feedback or questions. Regards, Christian Teuschel & Romeo Zwart RIPE NCC On Mon, May 11, 2015 at 01:15:09PM +0200, Job Snijders wrote: > Hi MAT, > > I'd really like the stat team to implement a tool that tells me > what prefixes are originated AND transitted by a given ASN. The > use-case is that I (before setting up BGP sessions) can make an > automated assessment what amount of prefixes the network will > announce, which prefixes they are likely to announce and if that > matches up with the prefix-filter I would apply on that bgp > session. > > A second use case is that when I want to connect a peer or customer > to which I have never been connected before, I have no idea what > they will announce to me. Should I want to make predictions for > traffic engineering purposes, it would be beneficial if I could > fetch a list of prefixes this peer is likely to announce to other > peers from the stat system. > > A sliding window of say 30 days would be perfect, for my purposes I > do not need the tool to offer data going back to the beginning of > time. > > Do others agree that the above would be a useful feature? > > Kind regards, > > Job >

2 1

Eleven new RIPE Atlas anchors have joined the community
by Michela Galante 24 Jun '15

24 Jun '15

Dear colleagues, More and more organisations from all over the world are hosting RIPE Atlas anchors: in the last 6 weeks, on average, 2 anchors were activated every week! We are proud to announce that eleven new RIPE Atlas anchors have been activated since our previous announcement, bringing the total to 132: * us-els-as40528 located in El Segundo, California and us-rtv-as16876 located in Reston, Virginia, hosted by ICANN. * nl-dro-as51430, hosted by ALTUSHOST B.V. in Dronten, The Netherlands. * us-pou-as6124 hosted by Marist College in Poughkeepsie, New York. * pk-isb-as7590 hosted by COMSATS Internet Services in Islamabad, Pakistan, and sponsored by APNIC. * ph-qzt-as9821 hosted by ASTI in Quezon City, Philippines, and sponsored by APNIC. * nl-hrd-as34612 hosted by Matrix DATA in Harderwijk, The Netherlands. * at-szg-as5404 hosted by conova communications GmbH in Salzburg, Austria. * fr-ysd-as201958 hosted by ADP in Saint-Denis, France. * de-fra-as49024 hosted by FHE3 GmbH in Frankfurt am Main, Germany. * de-ham-as201709 hosted by Netzwerge Hamburg eK in Hamburg, Germany. The map of all anchor locations is available at: https://atlas.ripe.net/anchors/map/ You can access the anchoring measurements for all anchors at: https://atlas.ripe.net/anchors/list/ And here are the logos and links to hosting companies: https://atlas.ripe.net/get-involved/community/#!tab-anchor-sponsors We are still accepting new applications from individuals and organisations interested in hosting a RIPE Atlas anchor. We are particularly interested in deploying anchors in the Middle East, Western Asia, Latin America and Africa, in order to add more geographical diversity to the measurement data. There are more organisations that want to host a RIPE Atlas anchor but don’t have the necessary funding. To learn more about sponsoring an anchor, please contact us at mcb(a)ripe.net To apply for your own RIPE Atlas anchor: https://atlas.ripe.net/get-involved/become-an-anchor-host/ For any other questions, please contact us at atlas(a)ripe.net Regards, Michela Galante Measurements Community Building RIPE NCC

1 0

[training] RIPE NCC Webinars - new dates
by Training Services 18 Jun '15

18 Jun '15

Dear colleagues, We are pleased to announce the dates for the RIPE NCC Webinars for the coming quarter. These interactive on-line learning sessions take about one hour, and give you the opportunity to learn and interact with our trainers without leaving your desk. In the next 3 months you can participate in the following Webinars: - Advanced RIPE Atlas Usage (NEW!) - Introduction to the RIPE Database - RIPE Database - Advanced Topics - IPv6 in the RIPE Database - IPv6 Addressing Plan - Webinar for New LIRs - Resource Certification (RPKI) Register now at https://www.ripe.net/support/training/learn-online/webinars Participation is limited to 20 people, so don't hesitate if you want to take part! If you have any questions, please email <training(a)ripe.net>. We look forward to seeing you online. Kind regards, RIPE NCC Training Service

1 0

New on RIPE Labs: HTTP Measurements with RIPE Atlas
by Mirjam Kuehne 16 Jun '15

16 Jun '15

Dear colleagues, After a discussion with the community about HTTP measurements, we'll 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, Mirjam Kuehne RIPE NCC

1 0

problems with RIPE Atlas website
by Romeo Zwart 08 Jun '15

08 Jun '15

dear colleagues, We are currently investigating issues with the RIPE Atlas service that cause the RIPE Atlas web pages to fail. We will update you of any further developments through https://www.ripe.net/support/service-announcements/service-and-security-ann…. We apologise for the inconvenience caused. Kind regards, Romeo Zwart RIPE NCC

1 0

Re: [mat-wg] Geoloc API covered_percentage
by Christian Teuschel 28 May '15

28 May '15

Dear Noriyuki, The "covered percentage" value shows how much of the referenced IP space is known in the geoip database (MaxMind's GeoLite City, [1]). This referenced IP space depends on the look-up type: - For a prefix look-up it is the given prefix itself. - For an ASN look-up it is related to the prefixes this ASN originates. A recent update to the documentation makes it more clear, https://stat.ripe.net/docs/data_api#Geoloc. Best regards, Christian [1] http://dev.maxmind.com/geoip/legacy/geolite/ On 19/05/15 12:00, Arai Noriyuki wrote: > > hi all, > > i am trying to do something with the geoloc API and i found there is > an item named "covered percentage" for every location. what does it > mean? > > (i once thought it is the percentage of the IP addresses in that > location among the whole address space of the object resource. but it > sounds i was wrong. :P) > > thanks and regards, > noriyuki >

1 0

Geoloc API covered_percentage
by 荒井則之（ネットワーク本部）- Arai Noriy uki - 18 May '15

18 May '15

hi all, i am trying to do something with the geoloc API and i found there is an item named "covered percentage" for every location. what does it mean? (i once thought it is the percentage of the IP addresses in that location among the whole address space of the object resource. but it sounds i was wrong. :P) thanks and regards, noriyuki

1 0