Proxies for bots and automation

A script that sends thousands of requests from one address quickly runs into a site's limits. Proxies spread requests across many IPs or keep one address for a whole session.

Datacenter proxies — $0.80/GB

What they are used for

collecting public data and monitoring prices on a schedule;
checking site and ad availability from different countries;
automated UI tests from different regions;
bots that work with APIs and web pages on behalf of your team.

Rotation or a sticky address

Rotation — port 823 (HTTP) or 824 (SOCKS5): every request comes from a new address. Good for independent requests where no session is needed. Sticky IP — ports 10000–20000: the address is kept for 1 to 120 minutes. Needed where a bot logs in to an account or performs several steps in a row. Each port is a separate address, so give parallel threads different ports.

Which proxy type to choose

Datacenter proxies are the cheapest and fastest and are enough for sites without strict protection. Residential proxies are for sites that block datacenter addresses. Mobile proxies suit mobile versions and apps. Start with datacenter and move up if the site rejects them.

How to connect

One plan allows up to 1,000 concurrent connections. There are ready examples for Python requests, aiohttp, Node.js, Puppeteer, Playwright, Selenium and Scrapy. You can manage plans from code through the API: create them, add traffic and fetch connection lines.

What to know up front

The proxies carry TCP traffic only; UDP is not supported. The address pool is shared. Automation must stay within the target site's rules and our acceptable use policy: spam, engagement fraud, password guessing and attacks are prohibited, and we stop such plans.