Rotation is a word providers use loosely, and the difference between two interpretations of it is the difference between a working scraper and a blocked one.

Some providers rotate on a timer. Every few minutes you get a new address, and every request in between shares one.

IPHTML advertises per request rotation, which means every single call goes out from somewhere different.

Why That Distinction Decides Outcomes

Picture a target that allows twenty requests per address before it starts challenging you.

On timed rotation, if your scraper sends two hundred requests in ten minutes, all two hundred come from one address. You hit the limit on request twenty one and spend the remaining nine minutes collecting CAPTCHAs.

On per request rotation, those two hundred requests come from two hundred addresses. No individual address does anything remarkable, so nothing triggers.

Same pool, same bandwidth, completely different result. It is the single most important question to ask a provider and most people never ask it.

The Network

Over 70 million residential addresses, described as real IPs, plus 4 million fast datacenter addresses and a mobile pool spanning 3G, 4G and 5G.

Static proxies on fixed ISP addresses are available for the work that needs the opposite of rotation, which is most account management.

Pricing is published per gigabyte for pools and per IP for static addresses, with SOCKS5, geo targeting, session control and a free trial. The site runs in English and Chinese.

Built for Developers, and It Shows

IPHTML says it is built for developers, and a few things back that up.

The solutions are described by what they solve rather than what they are: bypass blocks, global SERP data, detect ad fraud, price monitoring, multi account management. That is how an engineer describes a ticket, not how a marketer describes a product.

There is a developers section, API access, concurrency handling and documentation, so the integration path is clear rather than implied.

Simple Transparent Pricing

Every tier is published. No tier called contact us, no pricing that appears only after you create an account.

This keeps coming up in this series because it keeps being unusual, and it genuinely matters. You cannot compare providers on total cost if half of them will not tell you what they charge, and the ones who publish are effectively inviting the comparison.

Who It Fits

IPHTML suits scrapers hitting per address rate limits, developers who want proper API documentation, teams needing both rotating and static from one account, and anyone doing SEO or price monitoring at volume.

Who Might Look Elsewhere

Enterprise buyers wanting formal SLAs and named account management should look at the larger platforms.

If your work is a handful of manual tasks in a browser, this is more infrastructure than you need and a simpler provider will be easier to live with.

Final Verdict

IPHTML is a solid, technically credible provider that gets the rotation question right.

Per request rotation across a 70 million address pool, fast datacenter and mobile alongside, static ISP for the jobs that need stability, published pricing and documentation aimed at people who will actually integrate it.

If your scraper keeps hitting rate limits despite having a big pool, per request rotation is very likely the fix, and this is where to test that theory. Our scraping guide covers the other causes worth ruling out first.