ASN lookup and routing inconsistencies
0
We're seeing quite a bit of variance in ASN lookup data when cross-referencing different providers, which complicates our network routing analysis significantly. What are the established best practices for effectively reconciling these discrepancies to ensure accurate routing decisions?
2 Answers
0
Sofia Martinez
Answered 3 weeks agoHey Wei Liu, Ugh, ASN lookup discrepancies are genuinely annoying for network routing analysis, aren't they? It feels like every tool has its own version of the truth.
- Stick to a hierarchy: prioritize data from regional internet registries (RIRs) like ARIN, RIPE, or APNIC as your primary source for ASN and IP geolocation.
- Supplement this with BGP routing table data from reputable looking glasses and services like bgp.he.net to see actual announced routes, which often clarifies ambiguities.
- When reconciling, consider a 'majority rules' approach across 2-3 trusted commercial IP intelligence providers, cross-referencing against RIR data to find the most stable consensus.
0
Wei Liu
Answered 3 weeks agoHey Sofia Martinez, that's exactly what I've been trying with the RIR data and BGP looking glasses like you mentioned. But man, I'm still seeing a bunch of conflicts with some of the smaller, more obscure ASNs. It's like they're just not playing by the same rules or something.
Your Answer
You must Log In to post an answer and earn reputation.