ParseHub proxy setup goes through its IP Rotation feature: in a project's Settings, tick Rotate IP Addresses and paste your proxies into the Custom Proxies box, one per line, as IPAddress:Port:Username:Password. Two conditions come first. IP Rotation is a paid-plan feature, and custom proxies must be switched on for your account by ParseHub support. Static ISP IPs from ProxyHive fit the format directly.

Checked on 2026-09-30 against ParseHub's help article Adding Custom Proxies to ParseHub (for all Paid Plans) (last updated 2025-10-17) and the ParseHub pricing page. We have not run a ParseHub project through a ProxyHive IP ourselves.

Is ParseHub IP rotation plan-gated? What we found

Yes, twice over:

  1. Plan. On 2026-09-30, ParseHub's pricing page listed IP Rotation under the Standard and Professional plans. The free Everyone plan showed a dash in that row.
  2. Account switch. ParseHub's help article says custom proxies "will need to be enabled on your account" and asks you to contact [email protected] to do it. Being on a paid plan is not enough on its own.

Without custom proxies, ParseHub runs projects from its own IPs. Its help center says runs without IP rotation use addresses in North America, mostly American with some Canadian, and that runs with its built-in rotation use IPs from many countries, allocated at random. Custom proxies are how you choose the country, the carrier, or a fixed IP.

Why static IPs suit ParseHub

ParseHub's help article asks for proxies with a username and password, recommends static HTTP proxies, and warns that some providers' gateways are not compatible. Each ProxyHive ISP or datacenter IP is that shape: its own address and port, fixed for the term you buy, with credentials on the order.

  • ISP proxies are registered to consumer carriers, which helps on sites that refuse hosting ranges. You choose them by country, region, city and carrier, from one IP at $3.20/IP.
  • Datacenter proxies cost the same per IP at entry level and are fine for sites that do not care. See ISP vs datacenter for where each fits.

Residential is a poor match here: it rotates on its own and ParseHub's field needs a fixed address per line.

Before you start

  1. Confirm you are on a plan with IP Rotation and email [email protected] to have custom proxies enabled.
  2. Buy the IPs and open the order in the dashboard at https://app.proxyhive.io.
  3. Keep the order on username and password authentication. ParseHub runs projects on its own servers, so an IP allowlist would have to list ParseHub's addresses, which you do not control.
  4. Choose the HOST:PORT:USER:PASS copy format and copy the list, using each IP's HTTP port.

ParseHub proxy setup: add custom proxies

1. Open the project settings

Open ParseHub, go to the project, and open its Settings menu.

2. Turn on IP rotation

Tick the checkbox next to Rotate IP Addresses. A Custom Proxies text box appears at the bottom of the screen. If it does not, custom proxies are not enabled on your account yet.

3. Paste your proxies

One proxy per line:

203.0.113.10:PORT:USERNAME:PASSWORD
203.0.113.11:PORT:USERNAME:PASSWORD

Replace each value with the ones from your order. Every ISP or datacenter IP has its own port and credentials, so copy them per line rather than reusing one.

4. Save and run

Save the project and run it. ParseHub spreads the run across the proxies in the list.

How rotation behaves with a few static IPs

ParseHub rotates through the list you gave it. With three IPs, requests take turns across those three; it does not create new addresses. Rotating vs static proxies explains the difference in more depth.

  • One IP in the list gives you a fixed exit: useful when a partner allowlists your address or a site ties a session to an IP.
  • Several IPs in one country spread load for a large public crawl.
  • Several countries in one list mixes markets inside one run. For price or content comparisons by country, run one project per country, each with that country's IPs.

Verify the exit IP

  1. Create a small project that opens https://api.ipify.org?format=json and selects the page text.
  2. Turn on Rotate IP Addresses with your list and run it.
  3. The IP in the results should be one of the addresses on your order.

If it shows a North American address you do not recognise, the run used ParseHub's own IPs: custom proxies are not active on the account or the box was empty.

Troubleshooting

  • No Custom Proxies box. The feature is not enabled on your account. Contact ParseHub support.
  • Runs fail after you add proxies. Check the order of the fields: ParseHub wants IP, port, username, password, separated by colons. A line in USER:PASS@HOST:PORT form will not parse.
  • Authentication errors. Make sure the order is on username and password, not IP allowlist, and that each line carries that IP's own credentials.
  • Blocked or CAPTCHA pages. The proxy works; the site is refusing. Slow the project down, and read avoiding blocks while scraping.

Check the target against our allowed-use policy before you run. If you use Octoparse too, it needs the opposite setup (IP allowlist, no password): see Octoparse proxy setup.