Proxy Status Codes

Understand proxy error responses and what each status code means.

Starting 21 September, proxy error responses will include clearer status information. This will help you understand whether a request failed because of the proxy connection or because of the destination website.

How to Read an Error Response

A proxy error can include:

  • An HTTP status code, such as 502, 503, or 504.
  • A Proxy-Status value that gives a more specific reason for the failure.

For example:

HTTP 504 Gateway Timeout
Proxy-Status: mrscraper; error=connection_timeout

In this example, the connection could not be established before the time limit was reached.

Proxy Error Codes

Proxy error codeHTTP statusWhat it means
connection_timeout504The connection could not be established within the time limit.
http_response_timeout504The destination website did not respond in time.
connection_read_timeout504The destination website stopped sending data before the response was complete.
connection_write_timeout504The request could not be sent within the time limit.
destination_unavailable503A working proxy connection is not available right now.
connection_limit_reached503The selected route is temporarily handling too many connections.
connection_refused502The destination website refused the connection.
connection_terminated502The connection ended before the response was complete.
dns_error502The destination website's domain name could not be resolved.
dns_timeout504Resolving the destination website's domain name took too long.
tls_protocol_error502A secure connection to the destination website could not be established.
http_request_denied403The request was blocked by policy.
destination_ip_prohibited502The destination is not allowed.

Responses Without a Proxy Error Code

A response might not include Proxy-Status in these cases:

  • The response came directly from the destination website.
  • Authentication failed and returned HTTP 407.
  • The error could not be classified and returned HTTP 502.
  • The request used SOCKS5, which returns SOCKS5 response codes instead of HTTP headers.

When a destination website returns its own error, such as 403 or 429, that response is passed through without adding a proxy error code.

Availability

These proxy status codes will be implemented for requests made from 21 September onward. Requests made before this date might only return the HTTP status code without the additional Proxy-Status value.

On this page