The Geo cookie set by Varnish is not very good for IPv6 connections so in most cases CentralNotice ends up reaching out to https://geoiplookup.wikimedia.org/ (IPv4-forced) to get the data asynchronously.
This causes a notable delay in banner load time.
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Open | None | T121937 [EPIC] Fix and improve geolocation, and ensure it's working properly for FR campaigns | |||
| Resolved | BBlack | T121925 [EPIC] GeoIP lookup for IPv6 connections delays banner loading | |||
| Resolved | BBlack | T100902 Get rid of geoiplookup service | |||
| Resolved | BBlack | T143270 ULS GeoIP should not use meta.wm.o/geoiplookup | |||
| Resolved | Nikerabbit | T143542 Switch default ULS geoip provider | |||
| Resolved | AndyRussG | T143271 CN: Stop using the geoiplookup HTTPS service (always use the Cookie) | |||
| Resolved | BBlack | T99226 Switch Varnish's GeoIP code to libmaxminddb/GeoIP2 | |||
| Resolved | BBlack | T89688 Varnish GeoIP is broken for HTTPS+IPv6 traffic | |||
| Resolved | BBlack | T146638 Remove "GeoIP lookup" service from https://status.wikimedia.org | |||
| Resolved | None | T121938 Fix GeoIP lookup for IPv6 | |||
| Resolved | BBlack | T122092 CentralNotice: Fix GeoIP cookie synthesis or loading to prevent repeated calls to geoiplookup for IPv6 users who can't be geolocated by their address on that protocol |