- 🇺🇸United States tr Cascadia
I switched the database loading strategy like I suggested in #3122426-4: IP Address 47.107.231.180 is not assigned to a country despite what ARIN says on their website? → . The issue where that was done is 📌 Improve service for fetching data Fixed .
With this new strategy, your original test case of 116.50.58.180 shows as being from India.
Your original link shows the IP to be owned by an Australian company that does business in India, and the IP address block is managed by APNIC, which covers both India and Australia, so this is the primary source of information and I have no reason to believe it's incorrect.
For the case mentioned in #6:
The IP (31.134.103.235) is in SK (Slovakia), and the module now reports it as being in SK as expected if you load the data base using the new "Use all registries" option. (Go to the configuration page, change the registry, save the configuration page.)I believe the data is now a lot better, because we're not relying on potentially incomplete and outdated data download from a specific RIR (such as ARIN, which seems to have more than its share of problems) but instead we are now querying all 5 RIRs to get from each only the data that they are responsible for maintaining.
In short, I believe the quality of the data being used is a lot better now.
Automatically closed - issue fixed for 2 weeks with no activity.