> For the complete documentation index, see [llms.txt](https://docs.replicacyber.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.replicacyber.com/faqs/how-does-ip-address-geolocation-work.md). # How does IP address geolocation work? The majority of third-party websites and services that attempt to geolocate IP addresses do so via commercial geolocation databases, such as MaxMind. The methods used to generate these databases are proprietary and can vary depending on the database, but generally are estimates of location based on a multiple sources of information. Furthermore, IP addresses are often reassigned to different physical locations by network providers, so these databases can quickly go out-of-date. Due to this, it is not uncommon for two different geolocation databases to report different locations for a given IP address. IP geolocation services are often fairly accurate at the country level, but are less accurate at a local level. Because of the limitations of IP address geolocation, websites that attempt to geolocate your connection via these methods may not always return accurate information. Egress locations included in the Replica platform are labelled by their true physical location as a top priority, rather than labelling them by estimates given by any particular IP address geolocation service. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.replicacyber.com/faqs/how-does-ip-address-geolocation-work.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.