Collecting and analyzing routing information with Rotonda#

Luuk Hendriks, Jasper den Hertog — NLnet Labs

• Why: Route monitoring at scale is hard: vendor platforms give limited insight, especially into RPKI's effect on routes. Rotonda is adoptable, open-source tooling that lets an operator ask their own questions of their BGP/BMP data — the kind of tooling the triage guidance says to up-rank.
• What: A single self-contained Rust binary that ingests routing data via BMP (pre/post-policy Adj-RIB-in/out and Loc-RIB), live BGP, and MRT files, combines it with RPKI data via RTR, and exposes HTTP API, MQTT, and file outputs. Its distinguishing feature is Roto, a strongly-typed scripting language for filtering routes and monitoring events — compiled to native machine code (via Cranelift, to x86_64 or ARM64), so customization costs negligible overhead even in the hottest ingestion paths.
• How: Operators write small typed filters (reject iBGP, drop specific peers, log prefixes matching prefix lists) that run inside the collection pipeline rather than as post-processing. Designed to scale from 50 routes to 50 million with the same single binary.
• Where applicable: General-purpose and self-hostable by networks of any size — explicitly built for small operators who find heavyweight monitoring disproportionate. Still young; the presenters were actively soliciting feedback and use cases.