- mat-wg - mailman.ripe.net

RIPE 91 MAT WG agenda
by Stephen Strowes 21 Oct '25

21 Oct '25

Hi all, We're pleased to share our agenda for the upcoming MAT WG session at RIPE 91! The session will take place in the main room on Tuesday, 21 October, 16:00 -- 17:30 local time (which is UTC +0300). Our planned agenda is: *16:00 [05 min]: *WG chairs, welcome *16:05 [20 min]: *Geoff Huston: Preserving Privacy vs Open Measurement *16:25 [15 min]: *Raffaele Sommese: Disrupting the Internet in the name of copyright: An Italian Story *16:40 [15 min]: *Remi Hendriks: An empirical evaluation of longitudinal anycast catchment stability *16:55 [15 min]: *Ties de Kock: Querying the DFZ *17:10 [15 min]: *Willem Toorop: Who is really running email? *17:25 [05 min]: *WG chairs, closing remarks If you have not yet registered for RIPE91, you can do so at https://ripe91.ripe.net/register/ We are looking forward to seeing you all at the session! S.

2 1

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

25 Sep '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

3 4

IMWG Agenda - LACNIC44 / LACNOG2025
by Elisa 16 Sep '25

16 Sep '25

Dear all, We are happy to announce the agenda for the next session of the Internet Measurements Working Group (IMWG) at LACNIC 44/LACNOG 2025. The session will take place on Friday, October 10. We look forward to seeing you in San Salvador or remotely! --- AGENDA --- 11:30 - 11:45 - Welcome - Chairs 11:45 - 12:05 - Analyzing the Effect of an Extreme Weather Event on Telecommunications and Information Technology: Insights from 30 Days of Flooding - Leandro Bertholdo 12:05 - 12:25 - Mapping DNS blocking trends in LATAM - Camila Breventano 12:25 - 12:40 - IPv6 Adoption Measurement in the LAC Region: Current Status, Challenges, and Future Perspectives - Kamruzzaman Khan 12:40 - 12:55 - Tracking Visibility Gaps in Allocated Internet Resources - Pedro Ferreira 12:55 - 13:00 - Closing Remarks - Chairs Best regards, Massimo, Elisa (IMWG Chairs)

1 0

Removal of three low-usage RIPEstat endpoints on 13 October
by Ties de Kock 12 Sep '25

12 Sep '25

Dear colleagues, Over the past year, we have been migrating RIPEstat infrastructure to a new environment. As part of this process, we reviewed all components to ensure long-term maintainability. Three components with very low usage and ongoing data issues will be deprecated and removed in a month. We are announcing the immediate deprecation of the following API endpoints: * /data/speedchecker-bandwidth-measurements/… * /data/meternet-bandwidth-measurements/… * /data/generic-data (undocumented) These endpoints have not been visible in RIPEstat for a considerable period and have experienced ongoing issues with data updates. Removing these endpoints will reduce our application and systems maintenance overhead. These endpoints are deprecated with immediate effect and will be completely removed on 13 October 2025. Analysis shows very low external usage of these endpoints (fewer than 10 IP addresses in August 2025). We therefore do not expect this change to affect most users. However, we recognise that API deprecations can be disruptive, and we welcome feedback from anyone who relies on these services. We are particularly interested in hearing from users who require bandwidth measurement data, as we understand this represents a niche but potentially valuable use case. We would like to understand your specific usage patterns and requirements for this type of data. If the removal of these endpoints will impact your operations, please contact us immediately. Kind regards, Ties de Kock RIPE NCC

1 0

Call for presentations at MAT WG at RIPE 91
by Stephen Strowes 29 Aug '25

29 Aug '25

Hi all, RIPE 91 will take place 20 -- 24 October in Bucharest. We are seeking presentations for the MAT WG session, scheduled on Tuesday, 21 October! Interesting topics include (but are not limited to): * Measurement research which has an operational impact * Operational initiatives that could inspire new research directions * Projects focused on network data collection * Tools for network data analysis and visualization * Innovative measurement techniques and proposals Starting from RIPE 91, both plenary and working group proposals can be submitted through the same system, Pretalx: https://pretalx.ripe.net/ripe91/ The Pretalx submission form will ask you for various details. Please select the MAT track, and include a title & abstract (these will eventually become public). For our evaluation, please include the following in your proposal: * an outline of your presentation (under 'notes') or provide a draft slide deck * the slot duration you'd like; we tend towards 15-20 minutes including Q&A, but please specify * whether you intend to present in person or online The deadline for MAT WG proposals is 15 September 2025. We will make our selections and post our agenda soon after. If you have any questions, please contact us at mat-wg-chairs [at] ripe.net. Thanks! - Nina, Massimo, Stephen as WG chairs

1 1

Planned maintenance to data.ris.ripe.net, ftp.ripe.net, data-store.ripe.net on 25 July, 11:00-15:00 UTC
by Ties de Kock 01 Aug '25

01 Aug '25

Dear colleagues, The webserver that distributes RIS files, data.ris.ripe.net, as well as ftp.ripe.net and data-store.ripe.net, will be down for maintenance on 25 July. During the maintenance, a storage appliance will be moved to a different data centre. This is part of the RIPE NCC’s effort to reduce our data centre footprint and increase the geographical distance between our data centres. BGP sessions with RIS collectors will be established as usual, and no data will be lost. However, downloads from https://data.ris.ripe.net will not be available. Other RIS services are not affected. Start: Friday July 25, 2025 11:00 UTC End: Friday July 25, 2025 15:00 UTC Affected: * data.ris.ripe.net * ftp.ripe.net * data-store.ripe.net We expect service to be unavailable for two hours in this window. Kind regards, Ties de Kock RIPE NCC

1 2

Forecasting Cloud Performance with RIPE Atlas
by Alun Davies 22 May '25

22 May '25

Dear colleagues, What kind of latency do cloud service users actually experience? Can we forecast future connectivity performance based on latency characteristics for specific locations? New on RIPE Labs, Rita Ingabire and colleagues share answers to these questions and more based on the findings of a three-month traceroute study they conducted using RIPE Atlas: https://labs.ripe.net/author/rita-ingabire/forecasting-cloud-performance-wi… Best regards, Alun Davies RIPE Labs Editor RIPE NCC

1 0

MAT WG agenda for RIPE90
by Massimo Candela 13 May '25

13 May '25

Dear all, The MAT working group session will take place on Tuesday 13 May at 16:00 UTC+1. This is the agenda: 16:00 - Welcome - Chairs 16:05 - Lost in Encryption: Monitoring Audio and Video Flows without Payload in Video-Conferencing Applications - Julien Gamba 16:20 - WhoActuallyIs? Finding the Companies Behind the Networks - Joshua Levett 16:30 - Pontus: A Memory-Efficient and High-Accuracy Approach for Persistence-Based Item Lookup in High-Velocity Data Streams - Weihe Li 16:45 - Frontiers of LEO Space Networks: Understanding the Intricacies of Starlink's Internet Access - Nitinder Mohan 17:00 - Hardware-assisted Virtual Networking for low-latency network services - Florian Wiedner 17:15 - RIPE Atlas and RIPEstat updates - Robert Kisteleki 17:20 - Closing Remarks - Chairs See you in Lisbon! Ciao, Massimo (for the MAT WG Chairs)

1 1

Call for presentations for MAT WG at RIPE 90
by Massimo Candela 01 Apr '25

01 Apr '25

Hi all, RIPE90 will take place 12-16 May in Lisbon. We are seeking presentations for the MAT WG session, scheduled on Tuesday, 13 May! Interesting topics include (but are not limited to): * Measurement research which has an operational impact * Operational initiatives that could inspire new research directions * Projects focused on network data collection * Tools for network data analysis and visualization * Innovative measurement techniques and proposals Please submit your proposal at mat-wg-chairs [at] ripe.net by **Thursday 17 April**. Include the following in your email: * a title * a draft of the presentation (an outline is okay!) * a paragraph describing the topic and why it is of interest to the community * whether you intend to present in person or online Thanks! Nina, Stephen, Massimo as WG Chairs

2 1

release of the new RIPEstat UI
by Ties de Kock 27 Feb '25

27 Feb '25

Dear colleagues, Following our announcement last week on the RIPE discussion list [0], we have now deployed the new user interface for RIPEstat: https://stat.ripe.net. We invite you to take a look and share any feedback you might have with us. To learn more about the new RIPEstat UI and what has changed, check out this article: https://labs.ripe.net/author/ties/introducing-the-new-ripestat-ui. Best regards, Ties de Kock RIPE NCC On behalf of the RIPEstat team [0]: https://mailman.ripe.net/archives/list/ripe-list@ripe.net/message/L7S3RGSCJ…

1 0

New on RIPE Labs: Easy RIPE Atlas Data Analysis with SQL
by Alun Davies 12 Feb '25

12 Feb '25

Dear colleagues, In this step-by-step guide on RIPE Labs, Giovane Moura and Andra Ionescu dig into RIPE Atlas data to show how fans of SQL can use DuckDB as an alternative to Pandas for data analysis. Read more on RIPE Labs: https://labs.ripe.net/author/giovane_moura/easy-ripe-atlas-data-analysis-wi… Best regards, Alun Davies RIPE Labs Editor RIPE NCC

1 0

A Deep Dive Into the Baltic Sea Cable Cuts
by Emile Aben 27 Dec '24

27 Dec '24

Dear colleagues, last week we posted our analysis on the Baltic Sea cable cuts using the traceroutes that the RIPE Atlas anchor mesh produced: https://labs.ripe.net/author/emileaben/a-deep-dive-into-the-baltic-sea-cabl… We hope this provides for some interesting reading and insights about these events, and also about where we could improve our RIPE Atlas anchor deployments to better see the effects of these types of events. kind regards, Emile Aben RIPE NCC

1 0

Join Us for the "Exploring the RIPE Atlas UI" Webinar on 17 December 2024
by Olivia Ruimwijk 11 Dec '24

11 Dec '24

Dear all, We are excited to invite you to the upcoming *Exploring the RIPE Atlas UI Webinar*, scheduled for *Tuesday, 17 December 2024*. Join Stephen Suess for a 45-minute webinar showcasing the key features and tools of the RIPE Atlas UI. This interactive session is designed to enhance your understanding and usage of this powerful platform. *By the end of this webinar, you will be able to:* - Identify and utilise key RIPE Atlas UI features to efficiently find and analyse existing Internet measurements. - Evaluate various data visualisation and analysis tools to gain meaningful insights from measurement results. - Customise the RIPE Atlas UI to suit specific usage patterns and prioritise the information you need. *For more information and to register, please visit:* https://learning.ripe.net/w/courses/64-exploring-the-ripe-atlas-ui/305 Kind regards, Olivia Ruimwijk Training Coordinator RIPE NCC

1 0

MAT WG agenda for RIPE89
by Massimo Candela 29 Oct '24

29 Oct '24

Dear all, The MAT working group session will take place on Tuesday 29 October at 16:00 CET. This is the agenda: 16:00 - 16:05 - Welcome - Chairs 16:05 - 16:20 - Measuring and Visualizing DNS Watersheds - Jim Cowie 16:20 - 16:30 - A First Look at User-Installed Residential Proxies From a Network Operator's Perspective - Etienne Khan 16:30 - 16:45 - IoT bricks over v6 - Tianrui Hu 16:45 - 17:00 - Target Acquired? Evaluating Target Generation Algorithms for IPv6 - Lion Steger 17:00 - 17:15 - What’s in the Dataset? Unboxing the APNIC User Populations - Vasilis Giotsas 17:15 - 17:25 - RPKI flutter - Emile Aben 17:25 - 17:30 - Closing Remarks - Chairs If you are not already registered: https://ripe89.ripe.net/attend/register/ See you in Prague! Ciao, Massimo (for the MAT WG chairs)

1 1

A Detailed Look at Our Recent RIPE Atlas Infrastructure Migration
by Robert Kisteleki 02 Oct '24

02 Oct '24

Dear colleagues, Today we published a RIPE Labs article about the work we've been doing on the RIPE Atlas infrastructure. Please feel free to read it here: https://labs.ripe.net/author/kistel/a-detailed-look-at-our-recent-ripe-atla… Regards, Robert Kisteleki RIPE NCC

1 0

Changes to the RIPEstat UI
by Ties de Kock 01 Oct '24

01 Oct '24

Dear colleagues, Over the next few months, we will be making changes to RIPEstat, our information service and open data platform. Most noteworthy, we will introduce a new user interface (UI) that combines elements of the two previous versions introduced in 2013 and 2020. Initially, we will focus on reverting to the 2013 UI and adding the unique features that were available only in the 2020 UI. Afterwards, we will continue building on what we have, and on what we learned, and build something better that aligns with what our users need. Finally, we will sunset the 2020 UI as we continue developing the newer user interface. Our decision was made after extensive user research whilst we maintained two interfaces for a few years, and tried to bridge the gap between the ‘old’ and ‘new’. Our aim now is not simply to bring back an older platform, but to focus on the elements that matter to RIPEstat users the most, and build on them to modernise the product altogether. You can read more details about our decision in our RIPE Labs article: https://labs.ripe.net/author/adonis_stergiopoulos/streamlining-ripestat-bui… We welcome your comments on this mailing list, on the RIPE NCC Forum or by emailing us at stat(a)ripe.net. Kind regards, Ties de Kock Specialist software engineer RIPE NCC

1 0

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

Call for presentations for MAT WG at RIPE 89
by Massimo Candela 26 Aug '24

26 Aug '24

Hi all, RIPE89 will take place 28 Oct - 1 Nov in Prague. We are seeking presentations for the MAT WG session, scheduled on Tuesday, 29 Oct! Interesting topics (not limited to): * Measurement research, preferably with operational impact * Operational initiatives that could inspire new research directions * Projects focused on network data collection * Tools for network data analysis and visualization * Innovative measurement techniques and proposals Submit your proposal at mat-wg-chairs [at] ripe.net by **Friday 4 October**. Include in your proposal: * a title * a draft of the presentation (an outline is okay) * a paragraph describing the topic and why it is of interest to the community * if you are planning to present in person or remote. Thanks! Nina, Stephen, Massimo as WG Chairs

1 0

Join the Using RIPE Atlas Webinar on 4 July 2024 - Registration Open
by training mailbox 28 Jun '24

28 Jun '24

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 0

Session started at RIPE88
by Massimo Candela 22 May '24

22 May '24

Hi all, The MAT session started at RIPE88. Join remotely at: https://ripe88.ripe.net/live/main/ Ciao, Massimo

2 1

Summary of the discussions about previous proposals
by Robert Kisteleki 13 May '24

13 May '24

[This is the same message I sent to the RIPE Atlas ML. The majority of the content relates to RIPE Atlas.] Dear all, In response to community feedback, as well as to the observed behaviour of RIPE Atlas, earlier we put out some proposals about some aspects of future behaviour of RIPE Atlas. We’d like to summarise what we’ve heard so far (written responses as well as verbal discussions we participated in), and the path we plan to take based on these. Probe farming: There were many voices who agreed with some form of limiting this behaviour. We were also asked to reach out to users who are using many probes this way now. We did and the short summary is that most (but not all) answers give reasonable justification. Conclusion: we’ll add the relatively simple proposed rules (in short: limit the number of software probes from the same IP/prefix). Later on we can consider softer approaches, e.g. reducing the number of credits given to hosts with excess probes or using probe similarity metrics. Measurement aggregators: We proposed to embrace this existing phenomenon, ask these users to in the future give the system an indication about the distinct clients they serve, and perhaps step up as sponsors in such cases. We received many responses to this proposal. For the most part, current aggregators who responded stated that they have no significant issues with providing such client information – in an anonymised way of course. At the same time some of them stated that adding a “mandatory sponsorship” would discourage them from using RIPE Atlas in the future. Some argued that by having enough credits to do so, they were in fact contributing positively to the network already, and in fact some of them are or were sponsors. Conclusion: we’ll add the features needed to implement such aggregations, and work on incentives for these users to become RIPE Atlas sponsors. We’ll also add the need for proper attribution to the service, similar to what the commercial use policy describes. We may also look at additional requirements to ensure proper funding for our membership services. Data retention principles: This proposal was a high level one and we received limited feedback. One discussion raised how “financially sustainable” is defined; perhaps the best summary of this is the recent RIPE Labs article published by our CTO Felipe: https://labs.ripe.net/author/felipe_victolla_silveira/reducing-the-ripe-ncc… Conclusion: we are implementing our data storage and access features along the principles we laid out. For transparency, we’ll also include summaries of proposals we put out earlier (see: https://labs.ripe.net/author/kistel/five-proposals-for-a-better-ripe-atlas/) for which we haven’t provided a written conclusion. Remove per-hop “late” packets from traceroute [LATE-PACKETS]: we only heard support for this, therefore it’s in our plans now. Measure well-known CDNs [CDN-HTTP]: Multiple responses argued that by selecting a “short list” of CDNs that are included by default, there’s an implicit statement and/or bias in the system towards bigger providers, contributing to some aspects of centralisation. Others pointed out that this approach reflects the reality of generic users, since the majority of the content they consume is provided by said CDNs. In addition, there were some voices supporting this proposal because of the value it provides to (smaller) CDNs or because it incentivises probe hosts to join or to keep their probes connected. Based on these discussions we’ll not go ahead with a full set of CDN measurements; however we’ll try a smaller scale experiment to discover the potential benefits to all users. Generic HTTP measurements [GENERIC-HTTP]: the discussions centered around some reiterations of the previous arguments (i.e. the safety of both the probe host and the providers’ sides) and if/how the proposed opt-in activity of the probe host would help this. Given these arguments, and that only a few voices expressed their explicit support for this, we’ll put this activity on hold; we can revisit this if/when the community wishes so. Add support for STARTTLS measurements [STARTTLS]: there were lengthy discussions about how certain SMTP servers may react to such incoming measurements. The general agreement was that this measurement type can be useful, with the confirmation that these checks will explicitly stop after STARTTLS (i.e. they will not have the ability to even try initiating sending mails or such). Remove support for non-public measurements [ONLY-PUBLIC]: the discussion raised both arguments for and against changing the system’s behaviour. Some people also raised the possibility of making private measurements more costly (in terms of credits). We’d also like to note the reference to the data retention principles (private measurement results are not available to all users, therefore we’ll only store them for a limited time). All in all, for the time being we do not plan to make behavioural changes about this feature. Regards, Robert Kisteleki RIPE NCC

1 0

MAT WG agenda @ RIPE 88
by Stephen Strowes 10 May '24

10 May '24

Hi all, RIPE 88 is on the horizon! The MAT working group session will take place on Tuesday 21 May at 16:00 CEST. If you are not already registered, information on how to attend the meeting is available here: https://ripe88.ripe.net/attend/register/ Our current agenda is: - 16:00: Welcome (WG chairs) - 16:05: 20 Years of Inferring Inter-domain Routing Policies (Savvas Kastanaki) - 16:25: WHOIS Right? An analysis of WHOIS and RDAP consistency (Simon Fernandez) - 16:40: Analysis of Usage Patterns in RIPE Atlas Measurements (Pavlos Sermpezis) - 16:55: WetLinks and Starlink on the Road: Exploring the Stationary and Mobile Performance of Starlink (Eric Lanfer) - 17:15: NCC Update (Robert Kisteleki) - 17:30 Session closes This agenda ought to be reflected on the meeting plan soon: https://ripe88.ripe.net/programme/meeting-plan/mat-wg/ Hope to see you there, either online or in-person! Cheers, -S, as WG co-chair

1 0

Call for presentations for MAT WG at RIPE 88
by Stephen Strowes 08 Apr '24

08 Apr '24

Hi all, RIPE88 is coming up: the meeting will take place 20 -- 24 May. Once again, we are seeking your presentations for the next MAT WG session, scheduled on Tuesday, 21 May! Presentations for the WG session are preferably 10-15min long. Please include in your proposal: * a title * a draft copy of your proposed presentation; an outline is okay! * a paragraph describing the topic and why it is of interest to the community. Interesting topics include (but are not limited to): recent measurement research which has an operational impact; recent operational work that may open avenues to research; projects, tools, or datasets that support either operations or research. Please submit your presentation proposal by **Monday 29 April** by emailing us at mat-wg-chairs at ripe.net. We will make our selections and post the agenda soon after. RIPE meetings are fully hybrid with sessions facilitated through meetecho. We encourage presentations from anywhere; to help us plan, we'd appreciate it if you can indicate whether you are likely to be online or on-site. Please ask if you have any questions regarding the setup on either side. Thanks! Nina, Massimo, Stephen, as WG co-chairs

1 1

RIS beacon ROA configuration error
by Martin Pels (RIPE NCC) 04 Mar '24

04 Mar '24

Dear all, As documented on [1], we operate several RIS Routing Beacons for RPKI. Due to a configuration error, two of the beacons were advertised with an incorrect RPKI status for several days. This concerns the "RPKI Unknown" beacons, which are the following prefixes: * 2001:7fb:ff03::/48 * 84.205.83.0/24 For both these prefixes, a ROA was created at 2024-02-27 7:55 UTC, turning these announcements into RPKI Valid. Upon receiving a report about this incorrect change we have removed the ROA again. This was done at 2024-03-04 11:31 UTC. Kind regards, Martin Pels RIPE NCC [1] https://ris.ripe.net/docs/routing-beacons/#special-beaconing-setups

1 0