Response Codes

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.


400 Bad Request

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.

407 Proxy Authentication Required

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.

500 Internal Server Error

Proxy server has encountered an internal error. Retry request at a later time.

502 Bad Gateway

Response Code 502 signifies that the IP assigned to your session ID is no longer available or we do not have exit nodes that meet your provided parameters (e.g. city, ASN etc.) at a given time.

If you encounter this error, there are two ways to work around it. The first is to wait for one minute as the system automatically assigns a new IP address to your session ID. Another approach is to switch to a new session ID (i.e., change the sessid parameter) – this way, you will receive a new IP address.

522 Timeout

A proxy server did not receive a response from the upstream server in time. Retry request.

525 No Exit Found

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.

Last updated