Uploaded October 2026 | Updated November 2026, 3 hours ago
RIPE RIS has been collecting BGP data for more than 25 years. We maintain a long-term archive, and that comes with its own challenges: the volume only grows, and noisy or low-value data stays with us forever. In recent years, we have therefore been quite selective about accepting new peering sessions. We now want to reconsider that approach: collecting data from more peers, while keeping the long-term volume manageable.
In this talk, I will recap the data RIS has been collecting and show some of the results --- and artifacts --- we see in the archive, including noisy peers, unstable sessions, and the growth of BGP attributes over time. I will then present ideas for a new peering policy that would allow us to be more open to new peers while keeping the resulting archival volume manageable.
We get a lot of input from researchers about RIS, but we also want to hear from network operators: what data is useful to you, and what should we avoid collecting? We would particularly like feedback on these ideas before turning them into a new RIS peering policy, which we hope to publish later this year.
Ties de Kock:
Ties de Kock is a software engineer at RIPE NCC where he works on internet measurement projects RIS and RIPEstat. In this role, he analyses BGP datasets for both operational incidents and long-term routing trends. Ties mostly spends his time developing tools that help network operators and researchers understand global routing behaviour. Prior to this, he worked on RPKI - from building certificate authority software to contributing to RPKI standardisation.
RIPE RIS has been collecting BGP data for more than 25 years. We maintain a long-term archive, and that comes with its own challenges: the volume only grows, and noisy or low-value data stays with us forever. In recent years, we have therefore been quite selective about accepting new peering sessions. We now want to reconsider that approach: collecting data from more peers, while keeping the long-term volume manageable.
In this talk, I will recap the data RIS has been collecting and show some of the results --- and artifacts --- we see in the archive, including noisy peers, unstable sessions, and the growth of BGP attributes over time. I will then present ideas for a new peering policy that would allow us to be more open to new peers while keeping the resulting archival volume manageable.
We get a lot of input from researchers about RIS, but we also want to hear from network operators: what data is useful to you, and what should we avoid collecting? We would particularly like feedback on these ideas before turning them into a new RIS peering policy, which we hope to publish later this year.
Ties de Kock:
Ties de Kock is a software engineer at RIPE NCC where he works on internet measurement projects RIS and RIPEstat. In this role, he analyses BGP datasets for both operational incidents and long-term routing trends. Ties mostly spends his time developing tools that help network operators and researchers understand global routing behaviour. Prior to this, he worked on RPKI - from building certificate authority software to contributing to RPKI standardisation.










