Making WordPress.org

Opened 6 weeks ago

Last modified 6 weeks ago

#8390 new defect (bug)

Incorrect IP geolocation for Starlink customer IP — geofeed available for correction

Reported by: mliyala Owned by:
Priority: normal Milestone:
Component: General Keywords:
Cc:

Description

WordPress.org's IP-based geolocation is returning an incorrect location
for a Starlink-served IP address. The correct location is available via
Starlink's published geofeed, which follows the RFC 8805 geofeed format.

Correct location:
Kajiado County, Kenya (also verifiable as Nairobi/Kenya more broadly)

Authoritative source (Starlink geofeed):
https://geoip.starlinkisp.net/feed.csv

This CSV follows the geofeed convention (RFC 8805) and is the source Starlink
publishes for correcting third-party geolocation databases. Could the team
confirm which geolocation data source wordpress.org uses internally (e.g.
MaxMind GeoIP), and whether that data source can be corrected by referencing
this geofeed directly, or whether wordpress.org's own logic needs a manual
override for this range?

Happy to provide additional verification (traceroute, WHOIS, etc.) if useful.

Change History (2)

#1 @Otto42
6 weeks ago

WordPress.org generally doesn't use IP based geolocation. Where are you seeing this shown on the website?

#2 @tobifjellner
6 weeks ago

Is this about the "language guessing", which is based on HTTP Accept-Language headers?

Note: See TracTickets for help on using tickets.