Windows Location Services resolving a correctly-geolocated Wi-Fi network to the wrong province

<h2>Summary</h2>

<p>Windows devices connected to a Wi-Fi network in Toronto, ON are being geolocated by Windows Location Services to Quebec. The same network, queried directly against a third-party Wi-Fi positioning service, resolves correctly to Toronto, ON (43.651464, -79.376914). Non-Windows devices (iOS, Android) on the identical network resolve correctly.</p>

<h2>Environment</h2>

<ul>

<li>Windows 10 and Windows 11 (reproduced on multiple machines)</li>

<li>Reproduced across Chrome, Firefox, and Edge — so this is a Windows Location Services issue, not browser-specific</li>

<li>VPN/proxy disabled; IP-based geolocation correctly resolves to Toronto, ON throughout</li>

</ul>

<h2>Observed behavior</h2>

<ul>

<li>Windows Location Services consistently returns a Quebec location for this network</li>

<li>The same network's access points, checked independently, resolve to Toronto, ON</li>

<li>The offset is large enough to be a different province, not typical Wi-Fi positioning noise</li>

<li>Behavior is persistent and reproducible over multiple weeks, not a one-off</li>

</ul>

<h2>Impact</h2>

<p>This causes location-dependent Windows applications (including regulated services that require accurate provincial geolocation) to make incorrect jurisdiction determinations for affected users.</p>

<h2>What we're not including</h2>

<p>We're intentionally not providing the specific BSSIDs/AP identifiers involved, to avoid exposing identifying network information for the end user. Happy to work through a private channel if Microsoft needs the raw data to investigate.</p>

<h2>Ask</h2>

<p>Could the Windows Location Services team look into why this network is being mis-registered, and whether there's a way to flag/correct mis-geolocated access points in the underlying database?</p>