Geolocation database discrepancies

Our tool, "What is My Country?", is designed to accurately display a user's current country and IP location. We've been experiencing persistent issues with IP geolocation data discrepancies, particularly when cross-referencing against various commercial and open-source databases. This leads to inconsistent results for users, especially those utilizing VPNs or mobile networks, which severely impacts the tool's reliability.

For instance, a specific IP address might return conflicting country codes from different IP geolocation APIs. We're seeing scenarios like this regularly:

API_A: 192.0.2.1 -> Country: US (United States)
API_B: 192.0.2.1 -> Country: CA (Canada)
API_C: 192.0.2.1 -> Country: MX (Mexico)

We are seeking advice on the best practices for reconciling such conflicting IP geolocation data. What are the most effective strategies for improving accuracy, and are there any robust, highly accurate IP geolocation providers or aggregation methods that handle these discrepancies more gracefully?