> 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/getting-started/what-are-proxidize-proxies.md).

# What are Proxidize Proxies?

Learn what proxies are and how Proxidize mobile and residential proxies work, why mobile and residential IPs are trusted, and common use cases.

A proxy routes your internet traffic through another device, so the website you visit sees that device's IP address instead of your own.

Proxidize provides proxies on mobile and residential networks, so your traffic looks like an ordinary user rather than automated or datacenter traffic.

## Mobile Proxies

Mobile proxies route your traffic through upstream devices on the major U.S. mobile ISP networks, so it appears to come from an ordinary mobile user.

Mobile networks use CGNAT, a standard setup where many devices on the network share a pool of public IPs.

At any moment, one mobile IP can be in use by many ordinary subscribers.

Platforms are reluctant to block an IP that so many everyday users rely on, which makes mobile proxies the hardest-to-block option.

CGNAT is also why a mobile IP can be shared with other users of the network, and why the network can change it on its own.

{% hint style="info" %}
Mobile proxies are available in the **United States only**.
{% endhint %}

Learn more in [Mobile Proxies](/getting-started/choose-between-mobile-and-residential-proxies.md#when-to-choose-mobile-proxies).

***

## Residential Proxies

Residential proxies use IP addresses from residential ISPs, ethically sourced.

Because the traffic comes from ordinary ISP connections, most websites trust it.

Residential proxies cover **195+ countries** with state, city and ISP targeting, which suits large-scale, geo-targeted work anywhere in the world.

Learn more in [Residential Per GB](/per-gb-proxies/residential-pergb.md).

***

## Why mobile and residential IPs are trusted

Both types use IPs from consumer networks, so they blend in with normal user traffic.

Datacenter IPs, by contrast, come from hosting providers and are easy for websites to identify and block.

Mobile IPs are the hardest to block, and residential IPs offer the widest global coverage.

***

## What people use them for

* Ad verification
* Web scraping and large-scale data collection
* Price and SEO monitoring
* Market research and AI/LLM data collection
* Geo-targeted testing
* Brand protection

***

## Which one should you use?

For a side-by-side decision, see [Choose Between Mobile and Residential Proxies](/getting-started/choose-between-mobile-and-residential-proxies.md).

For plans and prices, see [Plans and Pricing](/plans-and-features/plans-and-pricing.md).

***

## Quick FAQ

<details>

<summary>Are mobile proxies available outside the United States?</summary>

Not currently.

For other countries, use [Residential Per GB](/per-gb-proxies/residential-pergb.md), which covers 195+ countries.

</details>

<details>

<summary>Why are mobile IPs hard to block?</summary>

Mobile networks share each public IP between many users.

Blocking one would block all of them, so platforms tend to leave mobile IPs alone.

</details>

***

## Related articles

* [Choose Between Mobile and Residential Proxies](/getting-started/choose-between-mobile-and-residential-proxies.md)
* [Plans and Pricing](/plans-and-features/plans-and-pricing.md)
* [Glossary](/reference/glossary.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/getting-started/what-are-proxidize-proxies.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.