Bug 13826 - Wrong Ip Location Correction
Summary: Wrong Ip Location Correction
Status: CLOSED FIXED
Alias: None
Product: Location Database
Classification: Unclassified
Component: Database (show other bugs)
Version: unspecified
Hardware: unspecified Unspecified
: - Unknown - - Unknown -
Assignee: Michael Tremer
QA Contact: Michael Tremer
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2025-02-27 01:48 UTC by Annoyed Badger
Modified: 2025-03-10 09:53 UTC (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Annoyed Badger 2025-02-27 01:48:30 UTC
The following ips show up as U.S. in the database, it would be nice to have this corrected to their correct locations, unless I'm unaware of an override that was instated to their AS numbers (Provider is Linode).

172.232.141.150 - Correct Location Sweden
172.104.142.74 - Correct Location Germany

Thank you.
Comment 1 Annoyed Badger 2025-03-08 14:44:35 UTC
Another ip
172.104.101.207 - Tokyo, Japan
Comment 2 Michael Tremer 2025-03-09 12:57:47 UTC
Hello Badger,

thank you for your submission. I can confirm that these IP addresses are tracing to the countries that you named. However, in the whois entry, they are all mapped to the US:

> NetRange:       172.104.0.0 - 172.105.146.255
> CIDR:           172.105.128.0/20, 172.105.144.0/23, 172.105.146.0/24, 172.104.0.0/16, 172.105.0.0/17
> NetName:        LINODE
> NetHandle:      NET-172-104-0-0-2
> Parent:         LINODE-US (NET-172-104-0-0-1)
> NetType:        Reassigned
> OriginAS:       AS63949, AS48337
> Organization:   Linode (LINOD)
> RegDate:        2022-12-21
> Updated:        2023-09-18
> Comment:        Geofeed https://ipgeo.akamai.com/linode-geofeed.csv
> Ref:            https://rdap.arin.net/registry/ip/172.104.0.0

As you can see there, there even is a Geofeed available from Akamai. On those, the subnets in question are missing.

We could now add all those IP addresses manually to the database, but with an organisation of the size of Akamai, this would be a lot of work and we will never get it right. It would be nice to have them added to the Geofeed so that we can automatically parse them and react to any changes promptly.

I assume it is a mistake that those subnets are not included.

Do you have a contact to report this to Akamai?
Comment 3 Annoyed Badger 2025-03-09 15:17:33 UTC
Sorry I might not be understanding, on the geofeed from Akamai they seem to be included.

172.104.101.0/24,JP,JP-13,Tokyo,
172.232.141.0/24,SE,SE-AB,Stockholm,
172.104.142.0/24,DE,DE-HE,Frankfurt,

I am new to all this stuff so if I am incorrect, I can open a ticket with Linode to get this hopefully resolved.
Comment 4 Michael Tremer 2025-03-10 09:53:21 UTC
Oh in that case, I must just be blind.

> https://git.ipfire.org/?p=location/location-database.git;a=commitdiff;h=a9b8ffcd3b4da9f6508cb10e68cc24f0e368ac8f

I manually added the Geofeed (because ARIN does not easily publish them), and I trigged a new update for the database which should be done in about 10 minutes.

Thank you for reporting this. Please feel free to send us more issues like this.