Hi, since I used your data, API (RIPEstat) and tools (RPKI validator) I figured I send you also my IRR and RPKI measurement results:
https://medium.com/@nusenu/how-vulnerable-is-the-tor-network-to-bgp-hijacking-attacks-56d3b2ebfd92 Thanks for making RIPEstat available for everyone. If anyone can comment on how hard it is to get a ROA for a legacy IP block for a RIPE member without converting it to ALLOCATED PA block first, that would be interesting. Also: is there any reason why a RIPE member would prefer to retain the LEGACY status? (instead of converting it) thanks, nusenu btw: While collecting the IRR data I stumbled on a problem with RIPEstat where it would say there is no IRR entry but NTTCOM actually had it (Christian is looking into it). https://stat.ripe.net/data/prefix-routing-consistency/data.json?resource=36.55.0.0/16 (if you change it to /17 the expected record will appear) "routes": [ { "origin": 10013, "irr_sources": [], <<<<------------------- "in_whois": false, <<<<------------------- "asn_name": "FBDC - FreeBit Co.,Ltd.", "prefix": "36.55.0.0/16", <<<<------------------- "in_bgp": true } vs whois -h rr.ntt.net 36.55.0.0/16 route: 36.55.0.0/16 descr: FreeBit CIDR origin: AS10013 notify: [email protected] mnt-by: MAINT-FBDC changed: [email protected] 20120821 source: NTTCOM -- https://twitter.com/nusenu_ https://mastodon.social/@nusenu
signature.asc
Description: OpenPGP digital signature
