> For the complete documentation index, see [llms.txt](https://help.proxidize.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.proxidize.com/legacy-products/proxy-builder/proxy-builder-cloud-dashboard/proxy-pools.md).

# Proxy Pools

{% hint style="warning" %}
**Available on:** Business plan only **Supported hosts:** Linux-based hosts only (SX2, SX4, Ubuntu, Raspberry Pi)
{% endhint %}

#### **Overview**

Proxy Pools let you group multiple endpoints under a single proxy address. Instead of connecting to individual proxies, all traffic is routed through the pool and distributed across the selected endpoints automatically. This is useful for increasing throughput and avoiding overloading a single connection.

***

#### **Load Balancing Methods**

When creating a pool, you choose how incoming requests are distributed across endpoints:

| Method               | Behavior                                                                                          |
| -------------------- | ------------------------------------------------------------------------------------------------- |
| **Round Robin**      | Requests are distributed randomly across all selected endpoints                                   |
| **Least Connection** | All requests are routed to one endpoint until it becomes overloaded, then spills over to the next |

***

#### **Creating a Proxy Pool**

Go to **Proxies → Proxy Pools** and click **Create Proxy Pool**. Fill in the following fields:

![](https://146351401.fs1.hubspotusercontent-eu1.net/hubfs/146351401/image-png-Apr-05-2026-03-02-44-6366-PM.png)

**Host** Select the host containing the endpoints you want to include in the pool.

**Endpoints** Select one or more endpoints from the chosen host to include in the pool. You can add as many endpoints as needed.

**Name** Give the pool a descriptive name to identify it in the table.

**Proxy Type** Choose the proxy protocol for the pool:

* HTTP IPv4
* HTTP IPv6

**Port Type** Choose how the pool's port is assigned:

* **Random** — a random available port is assigned automatically
* **Random with Range** — a random port is assigned within a specified range
* **Manual** — you specify the port number directly

**Backend Balance** Select the load balancing method: **Round Robin** or **Least Connection**.

Once configured, click **Save**. The pool will appear in the Proxy Pools table with its name, pool type, host, proxy address, balance method, and the endpoints included.

***

#### **Managing Proxy Pools**

From the Proxy Pools table you can:

* **Edit** an existing pool to update its endpoints, type, or balance method
* **Filter** pools by host
* **Export** the table as a CSV

***

#### Need Help?

If you have any questions, concerns, or need further clarification, feel free to reach out to us via live chat or email us directly at **<support@proxidize.com>**.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://help.proxidize.com/legacy-products/proxy-builder/proxy-builder-cloud-dashboard/proxy-pools.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.