Accurate MNC MCC lookup challenges

Our SaaS platform is increasingly reliant on highly accurate mobile carrier detection for real-time user segmentation and targeted service delivery. We're developing a new feature set that demands precision far beyond what standard ISP identification provides, specifically needing to differentiate between various mobile network operators for localized content and service optimization. The inherent difficulties with current mobile carrier detection methods are proving to be a significant blocker. Our primary challenge stems from the reliance on conventional IP-to-ISP databases. These databases, while useful for general geolocation, exhibit inherent inaccuracies when it comes to mobile users. Dynamic IP allocations, prevalent in cellular networks, coupled with the widespread use of VPNs and frequent Wi-Fi offloading, mean that an IP address often resolves to a broadband ISP or a data center rather than the actual cellular network operator a user is currently connected to. This leads to a substantial misidentification rate, rendering the data unreliable for our purposes. Client-side methods, such as leveraging WebRTC or the navigator.connection API, have also been explored but present their own set of insurmountable hurdles. Browser support for these APIs is inconsistent across different platforms and versions, creating a fragmented detection landscape. More critically, strict browser privacy policies and the explicit user permissions required for many of these methods make them entirely unsuitable for the passive, server-side detection we require for a seamless user experience across our platform. We cannot prompt users for connection details just to segment them. Furthermore, DNS-based lookups, while offering some insights, are limited in their ability to resolve to the actual mobile carrier. They frequently point to a CDN edge node, a proxy, or a generic access ISP, rather than providing the granular detail of the cellular network operator we need for precise targeting. The core technical block we're facing is precisely how to reliably obtain the Mobile Network Code (MNC) and Mobile Country Code (MCC) from a user's connection. This must be achieved *without* requiring any client-side user interaction, explicit app permissions, or relying solely on IP geolocation, which, as discussed, frequently falls short. There appears to be a fundamental disconnect between the IP address a user presents and the true cellular network operator identification, especially when considering the complex routing and NATing inherent in modern mobile networks. We need a method that can consistently pierce through this abstraction to reveal the actual mobile carrier. We’ve extensively evaluated various commercial IP geolocation APIs, including prominent players like MaxMind and IPinfo. While their offerings provide 'mobile carrier' fields, our testing reveals that these are often derived from the same problematic IP-to-ISP mapping, leading to insufficient accuracy and lacking the real-time reliability crucial for our dynamic platform. The data often identifies the network that *owns* the IP block, not necessarily the specific cellular operator serving the end-user. Explorations into leveraging HTTP headers such as X-Wap-Profile, Via, and even detailed parsing of User-Agent strings have largely hit dead ends. X-Wap-Profile is effectively deprecated, Via headers are inconsistent and often stripped or modified by proxies, and while User-Agent can hint at device type, it rarely offers the granular cellular network operator data we require for modern mobile browsers and networks. As mentioned previously, the navigator.connection API was thoroughly investigated for client-side detection but ultimately ruled out due to its pervasive cross-browser compatibility issues and the inherent user privacy limitations that prevent its passive, widespread deployment. So, the core question remains: what robust, server-side, real-time methods exist for achieving highly accurate mobile carrier detection? We are specifically seeking novel or less-common techniques that can effectively bridge this gap and provide reliable MNC/MCC data without requiring direct client-side access, explicit user permissions, or relying on the often-misleading IP geolocation. We need solutions that can function at scale for a rapidly growing SaaS platform, providing definitive cellular network identification.