Persistent geo-IP database accuracy degradation observed with IPv6 ranges, seeking drift mitigation strategies

hey everyone, so we're running a pretty intensive real-time location-based service, and obviously, accurate geo-IP data is absolutely critical for us, especially for regional content delivery and maintaining compliance across different jurisdictions.

lately, we've hit a wall with what seems to be a consistent, incremental 'drift' in our IPv6 geolocaiton data. it's not just the usual occasional inaccuracies you expect; this is a systemic degradation in geo-IP database accuracy, where some static IPv6 blocks are gradually reported further and further from their actual physical locations over weeks or even months. this really messes with our user experience, causing wrong content to be served, triggering incorrect regional restrictions, and creating potential compliance headaches. the lack of consistent location data stability with IPv6 is a real headache, and it's definitely more pronounced than anything we've seen with IPv4. we're really scratching our heads trying to pinpoint the root causes of this specific IPv6 geolocation data drift. are there any common proactive detection methods you guys use? what about robust validation strategies, or recommendations for geo-IP providers known for significantly better IPv6 stability and accuracy? really waiting for some expert insights on this.