> ## Documentation Index
> Fetch the complete documentation index at: https://www.octoparse.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Cloud IP pools

> Select an available Cloud IP Pool, test regional behavior, and distinguish cloud-region selection from paid proxy traffic.

Cloud IP Pool selects the public cloud region for an Octoparse Cloud run. It can be useful when a target site serves different regional content or reacts differently to the default cloud location. It does not change the IP used by Local runs, renew a login, or guarantee access to a target site.

## What a Cloud IP Pool changes

A Cloud IP Pool **only selects the region used for a Cloud run's network connection**. For example, choose Japan when a target site requires a Japanese location or shows Japan-specific content.

It does not:

* Turn the task into a paid proxy workflow
* Guarantee one fixed IP for every request or subtask
* Change the task's browser mode, User-Agent, Cookies, login state, or workflow steps
* Apply to task editing or Local runs

Cloud runs can use different cloud nodes and IPs within the selected region. After changing a pool, test the resulting page and data rather than assuming the location change resolved the issue.

## Available public regions

The current public pool list is **US, UK, Germany, Japan, Australia, France, China, Canada, Brazil, South Korea,** and **United Arab Emirates**, plus **Default**. Use Default when the target website works without a location-specific requirement. Select a country or region when the target's content or access rules depend on location.

## Change and validate the pool

1. Open the task's Cloud **Run Settings**.
2. Under **Public IP Pool**, select Default or the region needed for the target market.
3. Save the setting and run a small Cloud test.
4. Review the run event log and screenshot for redirects, access-denied pages, a login page, or a verification challenge.
5. Compare the expected regional page, fields, and record count with the baseline run.

## Public IP Pool and built-in proxies are different

| Option | What it changes | Scope |
| - | - | - |
| Public IP Pool | The region selected for Cloud execution | Cloud runs only |
| Octoparse built-in proxy | A managed residential proxy for task editing, Local runs, and Cloud runs | Proxy traffic is billed separately; see [Proxies and IP rotation](/docs/en/platform/proxy) |
| Custom proxy | A proxy you provide for a Local-run workflow | Use it for Local runs only |

Cloud runs can execute through different cloud nodes and IPs. Do not assume that every request will use one fixed IP, and do not treat an IP pool as a CAPTCHA or general anti-blocking solution.

<Tip>Start with Default when it returns the expected page. Change only one factor at a time, then keep the smallest configuration that produces complete, repeatable data.</Tip>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.