We use the MaxMind GeoIP2 database to assign our exit nodes
cityvalues. This database is updated weekly.
Some other public IP databases may show different locations. In cases where there can not be any location mismatches, please double-check if the location of the assigned proxy is the same on the IP database used by the target website.
Find the most common response codes while using our residential proxy pool below. If you receive any other response code, contact your dedicated account manager for more information.
A proxy server can return this error code if the request did not contain a host to connect to or if there was a generic error when parsing an HTTP request. Make sure you formed the request correctly, including the URL in the request, then try again.
Request lacks proxy authentication information, or username or password is invalid. Include the Proxy-Authorization header in your request, ensure that your username and password are formed correctly, then try again.
Proxy server has encountered an internal error. Retry request at a later time.
A proxy server received an invalid response from the upstream server. Retry request. Response Code
A proxy server did not receive a response from the upstream server in time. Retry request.
Custom HTTP status code - this means the proxy could not find an exit node that satisfies the request. Change request filter parameters or try again at a later time.
If you want to use your own backconnect entry node DNS name, you can point your subdomain/domain to our entry node. To do that, you need to add a DNS
pr.oxylabs.ioas the target. This is how such setup looks on Cloudflare DNS manager for