403/429 spikes mid-crawl
Likely causes
- - Rate too high for the target
- - Retries hammer the same URL
Verified remedy
Cut CONCURRENT_REQUESTS, add backoff, honor Retry-After, and resume slowly.
Proxy troubleshooting
Ranked causes, ordered diagnostics, and a verified remedy for scrapy banned despite proxy - ending with a final connection check.
Quick answer
Fix: Scrapy blocked while using a proxy. Confirm endpoint values, test with curl through the endpoint, apply the matched remedy, then re-verify the exit IP is your assigned endpoint.
Ranked causes, ordered diagnostics, and a verified remedy for scrapy banned despite proxy - ending with a final connection check.
Fix: Scrapy blocked while using a proxy. Confirm endpoint values, test with curl through the endpoint, apply the matched remedy, then re-verify the exit IP is your assigned endpoint.
Likely causes
Verified remedy
Cut CONCURRENT_REQUESTS, add backoff, honor Retry-After, and resume slowly.
Likely causes
Verified remedy
Move to a dedicated static residential endpoint so only your traffic shapes the address.
The original action completes and the exit IP matches the endpoint.
If curl through the endpoint also fails, the problem is endpoint-level: check dashboard status or swap to a spare endpoint.
Facts last reviewed 2026-09-01.
Dedicated endpoints plus pacing turn bans into a controllable, per-target tuning problem.
Work the diagnosis tree top to bottom: confirm endpoint values, test with curl through the endpoint, apply the remedy, then run the final connection check.
Recurring proxy failures usually trace to an unstable mapping - rotating endpoints or shared addresses. A dedicated static endpoint per profile makes behavior predictable.
Buy self-serve now, or talk with us about a larger agency inventory.