September 2024 - mat-wg - mailman.ripe.net

Join the Using RIPE Atlas Webinar on 4 July 2024 - Registration Open
by training mailbox 07 Apr '26

07 Apr '26

Dear colleagues, We are pleased to announce that the RIPE NCC will host another *Using RIPE Atlas Webinar* session on *Thursday, 4 July 2024*. *Duration*: 2 hours *Cost*: Free *Open to*: Everyone interested This webinar helps you to monitor your network and troubleshoot it with RIPE Atlas. Create specific tailor-made measurements that suit your needs using API calls or the command line interface. *Prerequisites:* - Basic knowledge of networks - How the Internet works - Basic understanding of IP, ASN, domains - Familiarity with pings and traceroutes *After this webinar, you will be able to:* - Monitor your network using RIPE Atlas measurements - Troubleshoot your network using measurements from RIPE Atlas - Use the RIPE Atlas command line interface and the API to create tailor-made measurements For more *information and registration*, please visit: https://learning.ripe.net/w/courses/17-using-ripe-atlas-webinar *Help Us Spread the Word*: We'd greatly appreciate your support in promoting this webinar. Please share our social media posts with your network: *LinkedIn*: https://www.linkedin.com/posts/ripe-ncc_webinar-onlinelearning-bgp-activity… *Facebook*: https://www.facebook.com/share/p/9XkXAtTPxve7dH3E/ *X (Twitter)*: https://x.com/ripencc/status/1805210020272914863 Thank you for your assistance in helping us reach a wider audience. Kind regards, Olivia Ruimwijk RIPE NCC -- To unsubscribe from this mailing list, get a password reminder, or change your subscription options, please visit: https://www.ripe.net/mailman/listinfo/mat-wg/

1 2

some thoughts on add-path and bmp at ripe/ris
by Randy Bush 19 Nov '25

19 Nov '25

i have some small thoughts on add-path and BMP in RIPE/RIS. this may hinder more than help, unfortunately. as a researcher, of course i would love a wider view into the AS graph and the views of as many ASs as possible. nom nom. but ... add-path, if not done very carefully, and documented in detail for each peer, will produce views i will not understand. it is analogous to not knowing what view a BGP peer gives RIS today. did it give me a full Nth view into peer X? is the path that of a peer, a customer, a provider? and add-path is worse because it prunes in configuration and vendor- dependent and otherwise unpredictable ways. and, as an operator if P is a RIS peer, and they give RIS BMP showing their input from their peers, upstreams, and customers, those peers, upstreams, and customers have not given thir consent to have their internals published! if they want to have RIS publish their internals, they would peer with RIS and choose what view they present. and, of course, the researcher does not know what view, peer, upstream, or customer P's BMP peer is giving them. same problem as above under add-path. randy

4 5

Some historical RIPEstat data will not be available from 24 September
by Felipe Silveira 30 Sep '24

30 Sep '24

Dear colleagues, As we shared back in May, we have been working to reduce our data centre footprint by managing the data for RIS and RIPEstat more efficiently[1]. We have experienced some problems which mean that parts of the historical RIPEstat data will not be available for an extended period. To reduce our data centre usage, we have been exporting RIS-related datasets from the database that contains our largest datasets (HBase) to a new environment, which allows us to decommission our old Hadoop cluster. During the migration, we encountered timeouts and memory limitations with old servers and software that held historical data. Here we faced a difficult choice: we could either extend our data centre contracts at considerable additional cost, or we could accept that certain historical data would not be available to users for an extended period. We decided on the second approach. It is important to be clear that we haven’t lost anything here. However, this does mean that we will not be able to provide aggregated historical data for a number of API calls and their corresponding widgets for some time after we complete our migration. These include: as-path-length, as-routing-consistency, asn-neighbours, asn-neighbours-history, bgp-update-activity, bgp-state, bgp-updates, bgplay, ris-peerings, routing-status, visbility. As mentioned, this has been a difficult process. We may still encounter other issues when we make the switch to the new environment tomorrow (24 September). My team is doing their utmost to keep any disruption to a minimum, but there are no guarantees everything will go to plan. We will be looking at the most efficient way to rebuild access to the historical data in the coming months, and we will share more details in an article on RIPE Labs soon. Kind regards, Felipe Victolla Silveira Chief Technology Officer RIPE NCC [1] For more on this, refer to the following: - Reducing our Data Centre Footprint (RIPE Labs): https://labs.ripe.net/author/felipe_victolla_silveira/reducing-the-ripe-ncc… - RIPE 88 Technology Update (slides 10-20): https://ripe88.ripe.net/wp-content/uploads/presentations/89-RIPE-88-RIPE-NC…

3 2

RIPEstat database migration postponed
by Felipe Silveira 26 Sep '24

26 Sep '24

Dear colleagues, Following Monday’s announcement, we have decided to postpone the move of our largest datasets (HBase) to a new environment by one month. As I mentioned in my last email, this has been an unexpectedly complex process that has required a massive effort from our engineering teams. To ensure that RIPEstat will continue operating, we did not feel confident going ahead when this could result in the service being severely disrupted. I am sure many of you have questions. We plan to publish a RIPE Labs article with more details soon, including which historical data will be delayed when the migration is fully completed. Kind regards, Felipe Victolla Silveira Chief Technology Officer RIPE NCC

1 0