New on LowEndTalk? Please Register and read our Community Rules.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
how long to update ip geolocation?
it has been a month since a provider has promised to update the ip geolocation which was swiped wrong at the DC. They are claiming that the fix was done on the DC end and it could take a while before it updates to the global db. I seem to remember having a similar issue with another provider INIZ but that ip geo was fixed in 2 weeks time and not a month.
Comments
It can be years if whatever you're checking doesn't update their database on a regular basis from Maxmind or any of the other "prime" sources.
Otherwise, Maxmind updates every Tuesday.
Just by SWIP'ing to correct details? The changes as above could take months/years to update.
If they manually submit corrections to 3-4 of the more known databases others will follow pretty quickly.
In most cases a SWIP isn't required but most geo databases follow this data, others like ip2location & neustar have probes which detect the route/location as well and ignore SWIP if incorrect.
Oh, god, i still face people asking why our servers are not in italy as promised even when we have the correct info in RIPE for YEARS!
So, yeah, it can take years...
Just ignore geolocation. Eventually the world will wake up to how useless it is.
Somewhere between 1 day and +inf.
Maxmind makes corrections whenever they feel like it, regardless of the frequency you submit that form.
It took roughly 2 years of submitting that form ~5 times a year before they got it right in our case. Not sure if thats the result of them finally probing our allocation, or thats just the queue length.
Incorrect, just pop up on live chat and they'll tell you why it never updated. In most cases submitting more than one request with different locations on the same subnet will mean the request will probably be ignored but if you ask to them to re-check on live chat they'll process it for the next update.
It all depends on databases, and when they update. Its like one of my OVH subnets can access BBC iPlayer, and another cant.