How to Rotate Residential Proxies Properly

Rotation is not the goal — trust is

Rotating every request looks like the safest default and often is not. Many sites treat a session that changes IP mid-flow as a stronger anomaly than one that keeps the same address for a plausible amount of time.

The right unit of rotation is the logical session: one IP per user journey, rotated between journeys.

Match the geography to the content

Prices, availability, language and even layout vary by location. If you are collecting German prices, use a German IP with a German locale and Accept-Language header. Mismatched signals are both a data-quality problem and a detection signal.

curl -x "http://customer-acme-country-de-city-berlin-session-a91:KEY@proxy.irmu.com:8080" \
  -H "Accept-Language: de-DE,de;q=0.9" \
  https://www.example.de/product/42

How pools get burned

Hammering one target from a narrow subnet, ignoring 429s, retrying instantly on failure and reusing an IP after it has been challenged all degrade pool quality — for you and for everyone else on it.

Back off exponentially, cap concurrency per domain, and retire IPs that fail rather than retrying them. Irmu does this automatically and exposes per-domain success telemetry so you can see it working.