Proxy Servers in Bulk

No — and for scraping this matters more than the raw IP count. Many websites throttle or block entire /24 ranges at once, so a thousand addresses from three subnets behave like three proxies with extra steps. Our packages are spread deliberately: a 1,000-IP package draws from 50 to 150 subnets, and a 5,000-IP multi-country mix from 150 to 200. Adding more countries to the mix is the easiest way to widen the spread further — different locations mean different networks by definition.

Yes, and there's nothing to configure on our side. Whitelist each server's IP — a package supports multiple whitelist entries — and divide the list into ranges in your own configs: one slice per project. If your machines share a dynamic IP, username/password authentication works from anywhere. One rule keeps the split clean: give each project its own slice and don't point two projects at the same target website through the same addresses, or their combined request rate will get IPs flagged twice as fast.

Possibly, if both packages target the same region — and we'd rather tell you before checkout than have you find out with a diff. Packages are assembled from the least-loaded addresses in the pool at the moment of payment, so two large same-region orders can overlap. Two ways around it: order different regions (or a country mix) for the second package, or skip the second purchase and size one bigger package instead — the per-IP price falls with volume, so one 10,000-IP order costs less per address than two of 5,000.

No — the calculator on this page is self-service well past that mark, with checkout and delivery automated after payment. Talk to a human when you actually need one: orders beyond 50,000 IPs or a custom package mix are built to order with a volume quote, and business customers get a contract, invoices, net payment terms, and a dedicated account manager. Either way you're not required to sit through a sales call just to get volume pricing — the price breakpoints are public, in the calculator.