Oxylabs 429 'limited to 1 req/s due to a low success rate' - domain throttle trips below 40% success

TL;DR

Do not just retry harder; fix the cause first: either your custom headers/cookies are interfering with Oxylabs' access logic, or the site's bot protection is beating it. If Oxylabs Web Scraper API suddenly 429s you on one domain only, check the message - 'limited to 1 req/s due to a low success rate' means your success rate on that domain dropped below 40% in the last 5 minutes, and Oxylabs throttled that domain to 1 request per second until it recovers.

Fix

1. Do not just retry harder; fix the cause first: either your custom headers/cookies are interfering with Oxylabs' access logic, or the site's bot protection is beating it. Expected: You get the expected result; the problem is gone.

When to use

• You are dealing with this situation.
• The symptom matches: Oxylabs 429 'limited to 1 req/s due to a low success rate' - domain throttle trips below 40% success.

When NOT to use

• Unrelated issues with a different cause.
• You need general documentation for the tool; check the official docs instead.

Compatibility

Reported per the linked source. Source: https://developers.oxylabs.io/products/web-scraper-api/usage-and-billing/rate-limits.

Variant phrasings

Oxylabs 429 'limited to 1 req/s due to a low success rate' - domain throttle trips below 40% success

Why it happens

Official Oxylabs docs (Web Scraper API rate limits): Web Scraper API continuously monitors your success rate on every domain you scrape. If your success rate on any domain goes below 40 percent measured over the last 5-minute window, your request rate to that domain is limited to 1 req/s until the success rate recovers. You get a 429 with the message 'Access to {domain} has been limited to 1 req/s due to a low success rate.' Two causes: Oxylabs cannot handle the site's bot control, or your own cookies/headers interfere with its web access logic.

Edge cases

• If your error message differs even slightly, this is probably a different issue; search the exact text.
• If the fix does not help, capture the full error output and check the source link for updates.

Source

https://developers.oxylabs.io/products/web-scraper-api/usage-and-billing/rate-limits

Source: Official Oxylabs docs (Web Scraper API rate limits): Web Scraper API continuously monitors your success rate on every domain you scrape. If your success rate on any domain goes below 40 percent measured over the last 5-minute window, your request rate to that domain is limited to 1 req/s until the success rate recovers. You get a 429 with the message 'Access to {domain} has been limited to 1 req/s due to a low success rate.' Two causes: Oxylabs cannot handle the site's bot control, or your own cookies/headers interfere with its web access logic.

Verified resolution: If Oxylabs Web Scraper API suddenly 429s you on one domain only, check the message - 'limited to 1 req/s due to a low success rate' means your success rate on that domain dropped below 40% in the last 5 minutes, and Oxylabs throttled that domain to 1 request per second until it recovers. Do not just retry harder; fix the cause first: either your custom headers/cookies are interfering with Oxylabs' access logic, or the site's bot protection is beating it. The limit lifts automatically when the success rate recovers. Domain-level throttle is per-domain, so other domains keep their normal rate.

Source URL: https://developers.oxylabs.io/products/web-scraper-api/usage-and-billing/rate-limits