#rpki

5 posts · Last used 18d

Back to Timeline
Pawel Foremski @pjf@infosec.exchange · Jul 27, 2026
bgpipe v0.22 is out! 🚀 New: MRT table dump support. A full RIB snapshot from RouteViews or RIPE RIS now streams as BGP updates, each tagged with the peer it came from. Which means every stage you already use just works on them: bgpipe --rpki -- read rib.bz2 -- rov -- grep 'tag[rov/status] == INVALID' That is RPKI validation of an entire routing table. 4.1M routes in 7s, validated in 8s. https://bgpipe.org #BGP #RPKI #networking
0
0
0
John Kristoff @jtk@infosec.exchange · Jul 24, 2026
0
0
0
Stéphane Bortzmeyer @bortzmeyer@mastodon.gougere.fr · Jul 21, 2026
#BGP #RPKI "With eight Firehol level 1 blocklist matches out of only 79 prefixes, repo.rpki.space stands out immediately. Inspection of BGP Tools DNS records for this server reveals a high density of mailing domains, strongly suggesting that spam mailing infrastructure is hosted across the prefixes in question. " An interesting survey of "small" RPKI servers. https://labs.ripe.net/author/ties-dirksen/whos-running-all-those-tiny-rpki-servers/
0
1
0
John Kristoff @jtk@infosec.exchange · Jul 12, 2025
2
0
2
Bryton Herdes @next_hopself@mastodon.social · Jun 24, 2026
ASPA object typo? Saw this in a path w/ @mingwei@infosec.exchange 🇨🇭AS8298 ↔️ 🇨🇭AS58299 ↔️ 🇺🇸AS13335 AS relationship is inferred as peer-peer between 8298 and 58299. ASPA object for AS8298 defines AS52899 as a provider, thinking that's meant to be AS58299 🙂 https://radar.cloudflare.com/routing/rpki/as8298#rpki-aspa-providers
2
0
3

You've seen all posts