IP geolocation accuracy
A map with a pin over your city looks precise, but the data behind it does not come from your router: it comes from a commercial database associating entire IP ranges with an approximate point. Understanding that origin explains why the right city sometimes comes with the wrong neighborhood.
A range reserved only for written examples, never delegated to a real ISP; any geolocation returned for it would be fictitious.
It never leaves the local network, so no public geolocation database has that address associated with any place.
Even so, the returned city is usually where the provider registered the block administratively, a regional hub, not necessarily the end user physical address.
No. GeoIP indicates an approximate region and can vary by ISP, VPN, CDN or database update.
No. The database returns an approximate point plus an accuracy radius in kilometers around it, and measures an entire network block, not a specific device. Street-level accuracy is not part of what this kind of data promises.
Because the carrier typically concentrates mobile data traffic through a handful of NAT gateways; the public IP that shows up can be registered in the gateway city, not yours, even while you are physically far from there.
Yes. The geolocation now points to the VPN exit server, usually a commercial datacenter, and there is no way to tell that apart from the user real address by looking at the IP alone.
No. RFC 1918 addresses never leave the local network or reach the public internet without going through NAT, so no geolocation database has those blocks associated with a real place.
The tool prefers local GeoLite2. If the local database is missing and the server is configured with IPinfo Lite, the lookup can use that public API from the backend; nothing is called directly from the browser.