Uploaded November 2025 | Updated November 2026, 3 hours ago
RIPE RIS collects BGP data from collectors worldwide, providing visibility into routing dynamics. While this data powers RIPEstat and various third-party applications, operators and researchers often need analyses beyond what standard tools offer. On the other hand, using raw data MRT directly, is challenging. It is computationally intensive and requires custom parsing scripts.
We are now publishing RIPE RIS data as indexed Parquet files, covering recent BGP
RIBs and updates. This means you can query routing data using SQL or datascience
tools rather than using MRT parsers. An analysis that previously took 10+ minutes
can now be done in seconds.
This approach has already proved valuable for our internal operations. When the
Baltic Sea cables were damaged, we could quickly explore the BGP impact. When analysis
the effects of the Iberian Peninsula power outage on BGP, we could investigate effects
within minutes instead of hours. This new data makes using route collector data
much faster and much more accessible.
This presentation will introduce the files and show how to use these new capabilities
through practical examples. I'll show how network operators can analyse bview/RIB/bgp snapshot
data and BGP updates this way - from investigating routing over time, to analysing stuck prefixes, or analysing the upstreams of a network as seen by collectors.
This data removes the traditional barriers of MRT processing, and makes BGP data analysis much more accessible, using much more tools and skills.
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 collects BGP data from collectors worldwide, providing visibility into routing dynamics. While this data powers RIPEstat and various third-party applications, operators and researchers often need analyses beyond what standard tools offer. On the other hand, using raw data MRT directly, is challenging. It is computationally intensive and requires custom parsing scripts.
We are now publishing RIPE RIS data as indexed Parquet files, covering recent BGP
RIBs and updates. This means you can query routing data using SQL or datascience
tools rather than using MRT parsers. An analysis that previously took 10+ minutes
can now be done in seconds.
This approach has already proved valuable for our internal operations. When the
Baltic Sea cables were damaged, we could quickly explore the BGP impact. When analysis
the effects of the Iberian Peninsula power outage on BGP, we could investigate effects
within minutes instead of hours. This new data makes using route collector data
much faster and much more accessible.
This presentation will introduce the files and show how to use these new capabilities
through practical examples. I'll show how network operators can analyse bview/RIB/bgp snapshot
data and BGP updates this way - from investigating routing over time, to analysing stuck prefixes, or analysing the upstreams of a network as seen by collectors.
This data removes the traditional barriers of MRT processing, and makes BGP data analysis much more accessible, using much more tools and skills.
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.


![Keynote: Why Do We Have Self-Driving Cars, But Not Autonomous Networks?
Self-driving cars were imagined as early as 1918 [1], accelerated by the DARPA Grand Challenge era (2004–2007) [2], and are now beginning to operate at commercial scale.
Self-driving networks were framed as an industry ambition in Kireeti Kompella’s 2017 NANOG talk [3]. But in networking, “driving” has come to mean several different things: configuration automation, network control, or automated operations.
The industry has made significant progress in configuration automation and network control, including traffic engineering and VPN control. Yet most network operations still live in an alert → ticket → operator loop, assisted by runbooks and, increasingly, copilots and agents. This talk focuses on autonomous network operations, the missing piece for network autonomy.
So, nearly ten years on, why are self-driving cars becoming reality at scale, while autonomous network operations is still an industry ambition?
The answer isn’t that networks are somehow harder than cars. The issue is more fundamental. Networking is approaching autonomous operations as an observability and workflow problem, building on the systems we already have. That is the natural first step when applying AI to network operations. But self-driving cars have shown that autonomy is not simply another AI capability added to existing systems. It requires a paradigm shift in architecture, signals, models and control.
In this keynote, we apply the control-system approach used in self-driving cars and robotics to autonomous network operations, assess what is missing today, show where autonomy can be deployed safely first, and describe a realistic path for the industry to move from assisted operations towards autonomous control.
[1] Apex.AI — “The Driverless Car Era Began 100 Years Ago”
https://www.apex.ai/post/the-history-of-automated-driving-part-one-the-driverless-car-era-began-100-years-ago
[2] DARPA — “The DARPA Grand Challenge: 10 Years Later”
https://www.darpa.mil/news/2014/grand-challenge-ten-years-later
[3] Kireeti Kompella (NANOG, June 2017) — “The Self-Driving Network™: How to Realize It”
https://www.nanog.org/sites/default/files/1_Kompella_The_Networking_Grand_Challenge.pdf
John Evans:
John Evans works on the development of AI-native systems at the intersection of network architecture, telemetry, control and operations, with the goal of making large-scale network infrastructure more autonomous.
He has worked in large-scale network infrastructure for over two decades, including network architecture, traffic engineering, planning, telemetry, service assurance and operational control. Most recently, he was a Principal Network Engineer for Network AI at AWS, working across network planning, engineering and operations. Before AWS, he was a Distinguished Engineer at Cisco, focused on service provider architecture and strategy, and held technical leadership roles at Cariden and BT.
Across those roles, John has seen network operations evolve from alert and ticket pipelines toward increasingly automated systems. His current work focuses on what is required to move beyond incremental automation toward autonomous network operations.
John has represented AWS and Cisco at NANOG and the IETF, and currently co-authors IETF OPSAWG work on packet discard reporting and classification. He is a Fellow of the IET, CCIE #4125, a named inventor on multiple networking patents, and the author or co-author of publications including IP/MPLS QoS for Multiservice Networks and MPLS Next Steps. Keynote: Why Do We Have Self-Driving Cars, But Not Autonomous Networks?](https://i.ytimg.com/vi/Jf_2t1GF9mA/mqdefault.jpg)







