Skip to main content
Why doesn't my GEO request match correctly?
K
Written by Katy
Updated over a month ago

By default, we utilize MaxMind GEO database for all geolocation information. You can choose a different geolocation database when geo-targeting, however, by following this guide.

If you are using a third-party service to check the geolocation of the IP address that you are connected to then the third-party service may contain inaccurate or outdated information. For this reason, you may see something different than what you requested with geo-targeting.

You can check to make sure that the proxy server connected you to an IP address in the correct location in two places:

  1. Your dashboard

  2. The Proxyrack API

Dashboard:

Click on the "Proxy Endpoints" tab and then scroll down to the "Currently Assigned Ports" section. Here you can check that the geo-targeting parameters that you have set under the "Parameters" column match what you see under the "Country/City" column.

Proxyrack API:

Follow the guide here to find your sticky session information. In the API response, you will see the "parameters" and "proxy" sections, where you can check that the geo-targeting parameters you have set match the proxy that you have been assigned.

{
"id": "10000",
"port": 10000,
"expireTime": "2024-11-14T16:23:43Z",
"requestParams": {
"autoReplace": "city",
"country": "US", // geo-targeting parameter that was set
"timeout": "15s",
"ttl": "5400s"
},
"proxy": {
"online": true,
"id": "PRJJDZ5DWM",
"ip": "107.214.54.105",
"country": "US", // country that was assigned
"city": "Akron",
"isp": "AT\u0026T Internet"
}
}
Did this answer your question?