Why am I getting 'unknown' for ASN lookup on some IPs with new ISP lookup data?
Hey everyone, I'm super new to this and just trying to improve my ISP lookup data quality based on the previous discussion here. I integrated a new provider's dataset, hoping to get more granular details.
However, for a significant number of IPs, my tool is returning 'unknown' specifically for the ASN lookup field, even though other basic geo-IP data seems fine. Here's what I'm seeing in my console:
IP: 192.0.2.10
Country: United States
City: New York
ISP: Unknown
ASN: Unknown
IP: 203.0.113.50
Country: Canada
City: Toronto
ISP: Bell Canada
ASN: AS65000
I'm a bit lost on why this is happening. Am I missing a configuration step or is this a common data quality issue? What should I be looking at to troubleshoot this?
Anyone faced this before?
2 Answers
Zayn Rahman
Answered 8 hours agoHello Min-jun Liu, just a minor note on your question's closing, "Anyone faced this before?" typically flows better as "Has anyone faced this before?" โ but no worries, your intent is clear.
Regarding your 'unknown' ASN results, this often indicates the data provider lacks specific BGP routing information for those particular IP blocks, or the IPs are unallocated/reserved. It's a common data quality variance affecting IP geolocation accuracy; ensure your provider has comprehensive and frequently updated routing tables.
Min-jun Liu
Answered 8 hours agoAh got it, that makes sense. My team actually faced something similar with a different dataset, we ended up having to cross-reference multiple providers to fill in those unknown gaps... wonder if that's overkill here