> 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/mobile-per-proxy/how-proxy-assignment-works-on-per-proxy-plans.md).

# How Proxy Assignment Works on Per Proxy Plans

How proxies are assigned on Per Proxy plans: upstream devices, what rotation changes compared with an ISP reassignment, and who controls the public IP.

Each proxy on a Per Proxy plan runs through its own upstream device, and your location and ISP choices decide which device it can use.

This article explains how that works underneath, what changes when the IP changes, and which part of it you control.

***

## Is my proxy dedicated to me?

Each proxy runs on its own upstream device, and no two of your proxies share an upstream at the same time.

Upstreams are pooled rather than permanently assigned, so the public IP may occasionally be shared.

Pooling is what lets you switch location and ISP on demand.

Rotation and ISP reassignment don't change your credentials, so there is nothing for you to update.

***

## What decides which device your proxy uses

Each proxy carries its own **Location** and **ISP** setting, and every rotation uses an available upstream device that matches them.

**Fastest** gives the proxy the widest choice of devices, while a specific state, city or ISP keeps it exactly where you want it.

To set a location or ISP, and to choose what happens when no device matches, see [Location, ISP and Fallback on Per Proxy](/mobile-per-proxy/location-isp-and-fallback-on-per-proxy.md).

***

## What rotation changes

A proxy rotates when you rotate it yourself, when its rotation interval comes due, or when you call its rotation URL or the Proxidize API.

In every case the proxy moves to a different upstream device and receives a new IP, within whatever location and ISP you have set.

The switch happens on our side, so your hostname, port, username and password all stay the same.

Your IP can also change without any rotation, because the ISP can reassign it on its own.

| Event                      | What changes                            | What stays the same                                     |
| -------------------------- | --------------------------------------- | ------------------------------------------------------- |
| A rotation                 | The upstream device, and the IP with it | Your credentials, and your location and ISP choices     |
| An ISP reassigning your IP | The public IP only                      | The upstream device, your credentials, and your filters |

For the ways to rotate, see [Rotating Your Per Proxy IPs](/mobile-per-proxy/rotating-your-per-proxy-ips.md).

***

## Who controls the public IP

The public IP itself is assigned by the mobile ISP.

Mobile networks share public IPs between many users through CGNAT, which is standard practice across mobile networks worldwide. See [What are Proxidize Proxies?](/getting-started/what-are-proxidize-proxies.md).

Because of that, two proxies on separate upstream devices can sometimes exit through the same public IP.

The ISP can also change the public IP as its own network conditions change, for example during a handover between towers.

Your proxy stays on the same upstream device through all of this, and your credentials and filters are untouched.

Proxidize controls which upstream device your traffic uses, and you control that through your location, ISP and rotation settings.

***

## Quick FAQ

<details>

<summary>Two of my proxies came out on the same IP. Is something wrong?</summary>

No. Mobile networks share public IPs between many users, so separate upstream devices can occasionally exit through the same public IP. Rotate one of them if you need the two to exit differently.

</details>

<details>

<summary>Do I need to update anything when the ISP changes my IP?</summary>

No. Your credentials, location and ISP stay the same, so your tools keep working as they are.

</details>

***

## Related articles

* [Mobile Per Proxy](/mobile-per-proxy/mobile-per-proxy.md)
* [Location, ISP and Fallback on Per Proxy](/mobile-per-proxy/location-isp-and-fallback-on-per-proxy.md)
* [Rotating Your Per Proxy IPs](/mobile-per-proxy/rotating-your-per-proxy-ips.md)
* [Per Proxy Pooling](/mobile-per-proxy/per-proxy-pooling.md)
* [Per Proxy vs Per GB](/plans-and-features/perproxy-vs-pergb.md)

***

## <mark style="color:$primary;">Need help?</mark>

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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.proxidize.com/mobile-per-proxy/how-proxy-assignment-works-on-per-proxy-plans.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.