504 — Gateway Timeout
Something in the middle waited for the origin and gave up. Through a proxy this often means the exit node reached the target but the target never finished answering.
A proxy fixes part of this. Choosing the right pool fixes this more often than rotating within one. Residential trades speed for trust; if you do not need the trust, do not pay the latency.
Why it happens
The target is slow and your timeout is shorter than its response time.
A residential exit on a poor connection — the route exists but is too slow to complete.
Heavy pages fetched with a mobile-grade exit, where the bandwidth is the constraint rather than the block.
How to fix it
- Raise the client timeout before blaming the pool. 30 seconds is not generous for a heavy page through a residential hop.
- Retry on a different exit — the next peer may simply be faster.
- Use datacenter or ISP IPs where the target does not block them; they are dramatically faster than residential.
FAQ
What does 504 mean?›
Why am I getting 504?›
How do I fix 504?›
Will a proxy fix 504?›
Other errors
Stop getting 504
Residential IPs across 199 countries, from $7.35/GB — no commitment, no monthly plan.
Get residential IPs →