APNIC 62 panel looks at geofeeds, RIR data and IP geolocation accuracy
A panel at APNIC 62 discussed how geofeeds, registry data and third-party geolocation providers fit together, and why accuracy and privacy both need attention.
What changed
At APNIC 62 in Mumbai, a panel discussed IP geolocation: how self-published geofeeds, RIR registration data and commercial geolocation providers work together, and why improving accuracy while protecting user privacy is becoming more important. APNIC published a summary on 24 September.
Why it matters for BYOIP teams
When a prefix moves between networks, clouds or regions, third-party geolocation databases can keep showing the old location for some time. That affects content licensing, fraud checks and regional routing for the services using those addresses. Publishing a geofeed gives geolocation providers an authoritative statement of where the addresses are used.
What to check
- Whether you publish a geofeed (the CSV format is defined in RFC 8805) and whether it is referenced from your registry records, as described in RFC 9632.
- Update your geofeed as part of the change plan whenever a prefix moves to a new cloud region.
- Check major geolocation providers after a move to confirm they picked up the change.
Sources
- IP geolocation at APNIC 62, challenges, geofeeds, and data quality perspectives
APNIC Blog · published 24 Sept 2026 · checked 30 Sept 2026
- RFC 8805, A Format for Self-Published IP Geolocation Feeds
IETF · checked 30 Sept 2026
- RFC 9632, Finding and Using Geofeed Data
IETF · checked 30 Sept 2026