Experiencing inconsistent AS number resolution for specific mobile ISPs on 'What is My ISP?' tool

Hey Diego Ramirez,

That's a classic challenge with mobile IP resolution, and you're not alone in facing it. The shift to carrier-grade NAT (CGNAT) and the dynamic nature of mobile IPs really complicates accurate AS number identification. It's like trying to find a specific apartment resident when the entire building shares one main entrance – the IP you see is often an egress point or a peering partner, not the direct mobile carrier.

Also, just a quick heads-up, it looks like you might have missed a word in your post; you said, "looking for robust strategies," which should probably be "we're looking for robust strategies." Easy to miss when you're focused on a technical problem!

Here are a few strategies and considerations that can help improve your mobile ISP identification:

• Specialized IP Intelligence APIs: Standard geo-IP databases and BGP routing tables are a good start, but for mobile, you often need more. Look into commercial IP intelligence APIs that specifically focus on network type and ISP identification. Providers like MaxMind (especially their minFraud service, which includes network data), IPinfo.io, and Digital Element often maintain more granular databases that can differentiate between the backbone provider and the actual mobile ISP behind it. They use proprietary heuristics beyond just BGP.
• Focus on IP Block Ownership & Delegation: While an IP might egress via Level 3, the /24 or /22 block it belongs to might be specifically delegated to AT&T Mobility. You need a data source that not only shows the immediate AS but also traces the original registration and delegation of larger IP blocks. This often requires cross-referencing RIR (Regional Internet Registry) data (ARIN, RIPE, APNIC, etc.) with more dynamic BGP feeds.
• Hybrid Lookup Logic: Implement a tiered lookup. If your initial AS lookup returns a known CDN (Cloudflare, Akamai) or a major backbone provider (Level 3, Cogent), trigger a secondary, more specific lookup designed to identify the "true" originating network. This might involve querying multiple services or using a more detailed database that maps these transit IPs back to mobile carriers.
• User-Agent String as a Hint (Supplemental): While not directly IP-related, the user-agent string from the browser can sometimes contain clues about the mobile carrier or device type, which can be a supplemental data point to cross-reference, especially if you're trying to validate an ambiguous IP lookup. Just remember, it's easily spoofed and not a primary source for IP-based identification.

The key here is often moving beyond basic BGP data to more refined datasets that map mobile IP ranges more accurately, sometimes by correlating with IP geolocation and other network intelligence. Have you explored any specific APIs that claim high accuracy for mobile network identification?

Hey Zayn Syed, yeah the scale is pretty massive for us, we're talking millions of lookups daily so any solution needs to be super efficient.