Try Webshare, here: [ Ссылка ]
At this moment, I don't use Webshare static residential IPs for bulk scraping use-case, but if I did, this is how I would get it done, while keeping costs down, and trying to attain a higher success rate.
For querying the same websites, repeatedly, many times, it's really not a large enough pool to be viable, but for diversified URLs, this kind of approach is something that could work effectively.
Even at a small scale, though, you would just be delaying the query rate by a small amount.
So, it's an interesting approach, but not necessarily a huge advantage, at-scale.
You kind-of drop your concurrency rates, and increase the backend of your pool, with this approach, compared to just using shared datacenter proxies, which gives you a smaller pool, but higher potential concurrency.
If you concurrency isn't that high, though, since it's limited by your hardware, then it actually does make more sense to use this type of residential proxy product, for the scraping use-case.
The great thing about the shared ones, of course, is you can also use them for more static use-case, as well as variated scraping.
If you were just scraping, though, the Static Residential Rotating IPs, here, do actually give you better value, at low concurrency.
