HTTP 504 Gateway Timeout
HTTP 504 Gateway Timeout means a server acting as a gateway or proxy did not receive a timely response from an upstream server needed to complete the request.
HTTP 502 Bad Gateway
HTTP 502 Bad Gateway means a server acting as a gateway or proxy received an invalid response from an upstream server while handling the request. It identifies a gateway-stage failure, not a specific defective exit IP.
HTTP 429 Too Many Requests
HTTP 429 Too Many Requests means the client has sent too many requests within a period defined by the responding service. The response asks the client to reduce its request rate and may include Retry-After.
Retries and Backoff
A retry repeats an operation after a failure. Backoff delays subsequent attempts, while a retry budget limits how much extra work is allowed. Safe use depends on the operation’s semantics and the reason for failure.
Proxy Timeout
A proxy timeout occurs when a client or intermediary stops waiting for a stage of communication. The timeout stage matters: connection establishment, reading, writing, and connection-pool waiting are different failures.