
Paul Williams (Customer) asked a question.
According to MaxMind's own lookup service "https://www.maxmind.com/en/locate-my-ip-address" the IP address "195.143.80.174" is based in the UK (it was previously being reported as being in the US) - checked on October 23rd and again today.
The latest downloadable geodata.patch file appears to be updating again (now showing in Kemp as GeoLite2-City: Version 20261030 Library Build 1.3.2 Database and Contents Copyright (c) 2026 MaxMind, Inc.) but this IP address is still being treated as a US address ( [client 195.143.80.174] Wafd: Critical. Blocking client [msg "Client from blocked country(US)"] )
I also restarted the load balancers to clear any cached lookups so it would be using fresh queries against the geodata.patch file.
Is there any way to validate that the contents of the geodata.patch file contains current MaxMind information (rather than just going by the file saying it has a new datestamp/version number)?
This was the previous thread/question about it not being updated:
Hi Paul,
I reached out to one of our developers, they clarified that we update the file once a week, and we publish the version from Friday on Monday morning (around 09:00 UTC). So there will be a bit of drift from the absolute latest version.
If you would like to see this updated on a more regular basis, you can submit a feature request letting us know via our portal: https://kemp.ideas.aha.io/
Best Regards,
Hi Andrew,
Thank you, but my question was more about how the IP address in the updated file was still being treated as a US address instead of UK when the MaxMind lookup was showing it as a UK address for at least a week earlier.
(Friday 23rd October it was showing as UK on their website, Monday 2nd November you published the data from Friday 30th October, which should have also shown that IP as being UK based)
Maxmind has 195.143.80.128/25 (which contained 195.143.80.174) as being based in Bristol, UK
(51.5409, -2.5623)
Is it possible for your developers to look at the information being used to update the geodata.patch file to see why this doesn't match?
(I have no idea if the file is generated from scratch every week from MaxMind data downloads, or if gets incremental updates - I will apply today's version on Monday when it gets published but what options are there if it still incorrectly reports 195.143.80.174 afterwards as being US based despite MaxMind's online lookup showing it as UK?)
Apologies, and thank you in advance,
Paul
Hi Andrew,
We have updated to Version 20161106, but the issue remains.
Can the developers check the contents of whatever MaxMind information they are using to update the file and verify it is being applied?
IP 195.143.80.174 is showing as UK on the MaxMind website, but Loadmaster thinks it is in the US.
[client 195.143.80.174] Wafd: Critical. Blocking client [msg "Client from blocked country(US)"] [data "195.143.80.174"]
Paul
Hi Paul,
Dev would like to investigate this further to ensure that we are receiving the latest up to date information from Maxmind. I'll let you know when I have more information about this, and I appreciate you bringing this up to us.
Best Regards,
Hello Paul,
I was able to view the maxmind mmdb file to verify the IP address, this IP appears to still be showing up as "US" when I check the latest GEoLite2-Country database from Maxmind. See attached screenshot.
Usually Maxmind are good to update the databases quickly when IP addresses change but maybe they missed this one. Corrections can be submitted to them or wait a bit longer for their next updates to see if the change is reflected.
Let me know your thoughts.
Thanks,
Thank you.
Very strange, as the MaxMind website lookup for that IP address is already showing the correct info, and has been for some time. I will try contacting MaxMind support as whilst they merge addresses together into less accurate locations on the GeoLite version, this shouldn't include different non-bordering countries.