I have the same issue of wrong IP location. I am in France. All IP location databases report my IP 212.114.28.25 as FR (see https://www.iplocation.net/ip-lookup).

But my IP is detected by fedora mirror manager in Russia and I am redirected to the server http://mirror.linux-ia64.org/.

Hmmm the GeoIP tool is giving the following:

$ geoiplookup 212.114.28.25
GeoIP Country Edition: RU, Russian Federation

Interesting. My IP isn't found from the geoiplookup tool...

$ geoiplookup 31.22.13.104
GeoIP Country Edition: IP Address not found

$ geoiplookup -v 31.22.13.104
GeoIP Country Edition: GEO-106FREE 20180327 Build 1 Copyright (c) 2018 MaxMind Inc All Rights Reserved

Does that mean it's using a 4 year old database?

This tool is definitively giving wrong answers :(. Its database is totally outdated even in Fedora 35. It depends of GeoIP-GeoLite-data-2018.06-8.fc35.noarch package. It explains why my IP location (modified in 2020 or 2021) and bcfse1 one (2019) were wrong.

See the location of the up-to-date RIPE record: https://apps.db.ripe.net/db-web-ui/query?bflag=false&dflag=false&rflag=true&searchtext=212.114.28.25&source=RIPE

It could be that we are using an out of date database. Not sure it was ever updated since we switched to geoip2.

It seems an account is required to get updated databases. Not sure if there if GeoLite2 is free of charge or not.

Does Fedora already have an account to use GeoLite2 databases? For MirrorManager the country edition would be good enough. There is also the anaconda geolocation service which uses a GeoLite2 database.

GeoLite2 free databases were removed from usage due to GDPR and some lawsuits. I don't think we currently have an account with GeoLite2.

OK I can download the 'Lite' versions with my old account, but I do not have time to automate this. This is going to need to be copied to a lot of different places to make this work.

I am changing the priority of this for the following reasons:
1. Multiple applications are broken:
* GNOME first boot placement for users
* Mirrorlist
* Fedora DNS zones
2. It is not going to be an easy fix.
* A role needs to be written to autodownload the updates (either paid or unpaid)
* The role needs to copy this to a place on various servers
* The above parts all look in different places so may need code changes.

OK I have slapped a fix on for the GNOME and Mirrorlist tooling which should help clean up these errors for people. This was done by manually downloading new databases and putting them on sundries (for gnome geoip) and mm-backend01 (for mirrorlist).

We also need it on all proxies.

ah missed that. It is currently provided by the package geolite2-city-20191217-5.fc35.noarch and geolite2-city-20191217-5.fc35.noarch . Either we need to make an rpm which overwrites this or a different way to distribute the files.

Turning it over to someone else to do that patching.

The mirrorlist-server process has a parameter to use the GeoIP2 database from another location. So if you copy the file to another directory I can provide the change to adapt the mirrorlist-server service file.

Ok so there seems to be some sort of problem with the proxies. Some proxies have geolite2-country-20191217-5.fc35.noarch and geolite2-city-20191217-5.fc35.noarch installed but only due to older playbook issues. I have made https://pagure.io/fedora-infra/ansible/pull-request/1068 to try and 'fix' this issue for the newer proxies and such.

OK I have pushed this fix and run it on the proxies. I hope this will clear up bad location data in the next 2 to 24 hours.

Amazing, thank you all. I can confirm mirrormanager is now returning mirrors in WEUR... much better than downloading from CN!

So, we have the temp fix for now here... do we want to keep this open to track regularly updating this/putting place automation to do so?

Or open a new one for that?

If it is fixed for now, I would say close it. A larger ticket needs to be made where a login/password and account set up are needed for getting this done regularly. I think that should be a different ticket.

Noticed this weekend that this has regressed, or load balancers in a pool have not been updated or a stale cache...

$ curl -s 'https://mirrors.fedoraproject.org/metalink?repo=fedora-36&arch=x86_64' | grep -o 'location="[A-Z]\{1,2\}"' | sort | uniq
location="CN"
location="ID"
location="JP"
location="SG"
location="TH"
$ curl -s 'https://mirrors.fedoraproject.org/metalink?repo=fedora-36&arch=x86_64' | grep -o 'location="[A-Z]\{1,2\}"' | sort | uniq
location="CN"
location="ID"
location="JP"
location="SG"
location="TH"
$ curl -s 'https://mirrors.fedoraproject.org/metalink?repo=fedora-36&arch=x86_64' | grep -o 'location="[A-Z]\{1,2\}"' | sort | uniq
location="AT"
location="BE"
location="BG"
location="BY"
location="CH"
location="CY"
location="CZ"
location="DE"
location="DK"
location="FI"
location="FR"
location="GB"
location="GR"
location="HU"
location="IS"
location="LT"
location="LU"
location="MD"
location="NL"
location="PT"
location="RS"
location="RU"
location="SE"
location="SK"
location="TR"
location="UA"
$ curl -s 'https://mirrors.fedoraproject.org/metalink?repo=fedora-36&arch=x86_64' | grep -o 'location="[A-Z]\{1,2\}"' | sort | uniq
location="AT"
location="BE"
location="BG"
location="BY"
location="CH"
location="CY"
location="CZ"
location="DE"
location="DK"
location="FI"
location="FR"
location="GB"
location="GR"
location="HU"
location="IS"
location="LT"
location="LU"
location="MD"
location="NL"
location="PT"
location="RS"
location="RU"
location="SE"
location="SK"
location="TR"
location="UA"
$ curl -s 'https://mirrors.fedoraproject.org/metalink?repo=fedora-36&arch=x86_64' | grep -o 'location="[A-Z]\{1,2\}"' | sort | uniq
location="CN"
location="ID"
location="JP"
location="SG"
location="TH"

The AS and geo-mapping of the IP in question hasn't changed in the last 3 months...

AS      | IP               | BGP Prefix          | CC | Registry | Allocated  | AS Name
208189  | 31.22.13.104     | 31.22.12.0/22       | GB | RIPE     | 2019-02-25 | Swish Fibre Ltd

I missed that this was re-opened.

Are you still seeing the issue? We have not changed these files in a while...

Please file a new issue if you are still seeing this?