Forum Discussion
IPv6 impossible travel wrong geo-ip data
Peter Holland Here is what I suggest we do - methodically log each instance of inaccurate IPv6 geo-tagging and report it to Microsoft through official support channels. The more precise, actionable data we provide, the better chance engineering teams have of identifying gaps and improving their datasets. This problem won't be resolved overnight.
However, by contributing concrete examples rather than just venting frustration, we stand a better chance of getting Microsoft's attention focused on tightening up IPv6 accuracy. I'm happy to help compile feedback examples if others want to contribute. Though it will take time, hopefully Microsoft will refine their IP geolocation capabilities to reduce these false alerts.
I agree with reporting the inaccurate instances of IPv6 geolocation to Microsoft, in theory. In practice, however, I don't have anyone on my team who has time to do this. This is something Microsoft needs to get right. If there are other databases that are more accurate, then MS needs to get access to that data. They are using bad IPv6 data for geofencing and, as has already been reported in this thread, this can lead to admins being locked out of their management and admin portals, not to mention reporting being wrong for logging, etc.
