Bug 14501

Summary: No Geofeeds are being imported for networks in the ARIN region
Product: Location Database Reporter: Michael Tremer <michael.tremer>
Component: liblocAssignee: Michael Tremer <michael.tremer>
Status: CLOSED FIXED QA Contact: Peter Müller <peter.mueller>
Severity: Minor Usability    
Priority: Will affect most users    
Version: unspecified   
Hardware: all   
OS: All   

Description Michael Tremer 2026-10-20 09:13:07 UTC
For ARIN, location-importer only imports delegated-arin-extended-latest and asns.csv, which have no comments, so that none of the Geofeeds that networks in the ARIN region refer to are being found. ARIN's WHOIS data can only be downloaded with Bulk Whois, which needs an agreement.

ARIN publishes its Internet Routing Registry every day without any agreement: https://ftp.arin.net/pub/rr/arin.db.gz

Its route objects can only be created by those who hold the address space (ARIN checks them against the registrations), and 7476 of them refer to a Geofeed, mostly as "remarks: Geofeed https://..." like the inetnum objects of the other RIRs. Those Geofeeds could be imported with the route as the network that they may contain.

This does not find Geofeeds that are only in the comments of a registration, like the one of Constant (NET-45-32-0-0-1, "Geofeed https://geofeed.constant.com/"), which only Bulk Whois or RDAP have.
Comment 1 Michael Tremer 2026-10-20 09:13:39 UTC
https://git.ipfire.org/?p=location/libloc.git;a=commit;h=2bde31ae9ac8363e553c30dd5b09cf812ecd8762

Author: Michael Tremer <michael.tremer@ipfire.org>

importer: Import the Geofeeds of route objects in ARIN's IRR

ARIN's WHOIS data can only be downloaded with an agreement, so that we
have not known about any of the Geofeeds of networks in its region.

ARIN publishes its Internet Routing Registry every day, in which route
objects can only be created by those who hold the address space. Many
of them refer to a Geofeed, like the inetnum objects of the other RIRs
do. We now import those, with the route as the network that the
Geofeed may contain, and nothing else of the IRR.

With the data of 2026-10-19, 7208 routes refer to 222 Geofeeds, which
gave 1574 networks a more specific country, mostly instead of US.
Networks and AS names are the same as before.

Fixes: #14501 - No Geofeeds are being imported for networks in the ARIN region
Signed-off-by: Michael Tremer <michael.tremer@ipfire.org>
Comment 2 Michael Tremer 2026-10-20 09:13:40 UTC
https://git.ipfire.org/?p=location/libloc.git;a=commit;h=69b82652865e8a84cc1712789c4b99da9b4c5ce3

Author: Michael Tremer <michael.tremer@ipfire.org>

man: Where location-importer finds the Geofeeds of ARIN

Fixes: #14501 - No Geofeeds are being imported for networks in the ARIN region
Signed-off-by: Michael Tremer <michael.tremer@ipfire.org>
Comment 3 Michael Tremer 2026-10-20 09:13:49 UTC
This has been implemented in the master branch of libloc (2bde31a, 69b8265).

"location-importer update-whois ARIN" now also reads https://ftp.arin.net/pub/rr/arin.db.gz, but only the route and route6 objects that refer to a Geofeed. The Geofeed may only contain networks inside of the route. It is being found in a geofeed: attribute, or in remarks or descr as "Geofeed https://...", in any spelling and with or without a colon. Nothing else of the IRR is being imported.

Tested with a local database with the data of ARIN of 2026-10-19:

* 7208 routes refer to 222 Geofeeds, of which 187 could be fetched, with 54492 networks inside of their routes.
* 1574 networks got a more specific country than the one that ARIN has for the organisation, mostly instead of US (e.g. 9.161.0.0/16 of IBM, now CA, AU, HU, PH, CL and MX).
* Networks and the names of the ASes of ARIN are the same as before.
* The import of ARIN takes 57 s.

Geofeeds that are only in the comments of a registration, like the one of Constant, are still missing. They would need Bulk Whois.

This will be in the database once the importer with these changes has been running.
Comment 4 Michael Tremer 2026-10-20 09:13:50 UTC
http://git.ipfire.org/?p=location/libloc.git;a=commit;h=2bde31ae9ac8363e553c30dd5b09cf812ecd8762

Author: Michael Tremer <michael.tremer@ipfire.org>

importer: Import the Geofeeds of route objects in ARIN's IRR

ARIN's WHOIS data can only be downloaded with an agreement, so that we
have not known about any of the Geofeeds of networks in its region.

ARIN publishes its Internet Routing Registry every day, in which route
objects can only be created by those who hold the address space. Many
of them refer to a Geofeed, like the inetnum objects of the other RIRs
do. We now import those, with the route as the network that the
Geofeed may contain, and nothing else of the IRR.

With the data of 2026-10-19, 7208 routes refer to 222 Geofeeds, which
gave 1574 networks a more specific country, mostly instead of US.
Networks and AS names are the same as before.

Fixes: #14501 - No Geofeeds are being imported for networks in the ARIN region
Signed-off-by: Michael Tremer <michael.tremer@ipfire.org>
Comment 5 Michael Tremer 2026-10-20 09:13:52 UTC
http://git.ipfire.org/?p=location/libloc.git;a=commit;h=69b82652865e8a84cc1712789c4b99da9b4c5ce3

Author: Michael Tremer <michael.tremer@ipfire.org>

man: Where location-importer finds the Geofeeds of ARIN

Fixes: #14501 - No Geofeeds are being imported for networks in the ARIN region
Signed-off-by: Michael Tremer <michael.tremer@ipfire.org>
Comment 6 Michael Tremer 2026-10-20 09:20:12 UTC
Correction to my comment above: the networks in 9.161.0.0/16 that got a more specific country are not those of IBM, but of Starlink (https://geoip.starlinkisp.net/feed.csv, e.g. 9.161.65.0/24 CA). 4604 route objects in ARIN's IRR refer to the Geofeed of Starlink, of which 40% of the networks had a different country in the database of 2026-10-17, mostly US.
Comment 7 Michael Tremer 2026-10-20 10:45:05 UTC
https://git.ipfire.org/?p=location/libloc.git;a=commit;h=54bdcf93d79bb620d64718b625444d648a3380e1

Author: Michael Tremer <michael.tremer@ipfire.org>

importer: Parse routes in the IRR with leading zeros in their octets

ARIN's IRR has 84 routes like 216.184.128.000/17, which Python does not
parse. None of them refers to a Geofeed at the moment, but they have
caused a warning each, and a Geofeed of one of them would have been
skipped.

Fixes: #14501 - No Geofeeds are being imported for networks in the ARIN region
Signed-off-by: Michael Tremer <michael.tremer@ipfire.org>
Comment 8 Michael Tremer 2026-10-20 10:45:21 UTC
ARIN's IRR has 84 routes with leading zeros in their octets, like 216.184.128.000/17, which caused a warning each. They are now being parsed (54bdcf9). None of them refers to a Geofeed at the moment.
Comment 9 Michael Tremer 2026-10-20 10:45:22 UTC
http://git.ipfire.org/?p=location/libloc.git;a=commit;h=54bdcf93d79bb620d64718b625444d648a3380e1

Author: Michael Tremer <michael.tremer@ipfire.org>

importer: Parse routes in the IRR with leading zeros in their octets

ARIN's IRR has 84 routes like 216.184.128.000/17, which Python does not
parse. None of them refers to a Geofeed at the moment, but they have
caused a warning each, and a Geofeed of one of them would have been
skipped.

Fixes: #14501 - No Geofeeds are being imported for networks in the ARIN region
Signed-off-by: Michael Tremer <michael.tremer@ipfire.org>
Comment 10 Michael Tremer 2026-10-26 16:43:31 UTC
This has been fixed in libloc 0.9.20, which has just been tagged. Closing this as fixed.