---
title: "What is a mobile proxy?"
url: https://proxy.wiki/glossary/mobile-proxy/
type: Glossary Term
author: "proxy.wiki editorial"
published: 2026-08-19
updated: 2026-10-21
site: proxy.wiki
topics: ["Proxy fundamentals"]
license: CC BY 4.0; quote freely with attribution to https://proxy.wiki/
---

# What is a mobile proxy?

> A proxy that exits through a mobile carrier's network, on a public address that real subscribers share behind carrier-grade NAT.

The address a site records is not the phone’s own. Carriers short of IPv4 space put subscribers behind [carrier-grade NAT](/glossary/carrier-grade-nat/): each device gets an internal address, and a translator at the edge of the carrier’s network maps many subscribers onto a smaller pool of public ones. A mobile proxy sends your traffic out through one of those subscriber connections, typically a SIM in a modem or a phone running a provider’s app. The destination then sees a public address that ordinary customers of the same carrier are using at the same moment.

That sharing is the reason the type exists. A site that blocks one carrier address risks refusing service to everyone translated through it, and the cost of that mistake lands on the site. Whether a given target actually treats mobile traffic more gently is something to measure on the target, using the procedure in [Residential vs datacenter vs ISP vs mobile: which to use](/guides/residential-vs-datacenter-proxies/), before paying for it.

## Three addresses on one connection

A mobile proxy built on a modem shows a different address at each layer. RFC 6598 reserved 100.64.0.0/10 for the middle one, the link between a subscriber’s equipment and the carrier’s translator. That block holds 4,194,304 addresses, and it is neither private space in the RFC 1918 sense nor routable on the internet.

| Where you look | What the address usually is | Who can reach it | Does a website see it |
| --- | --- | --- | --- |
| A machine behind the modem or hotspot | RFC 1918 space, such as 192.168.0.0/16 | Only devices on that local network | No |
| The modem’s cellular interface | Carrier-assigned: 100.64.0.0/10 shared space, or RFC 1918 space | Only the carrier’s own network | No |
| The translator’s public pool | An ordinary public address registered to the carrier | The whole internet | Yes, and other subscribers appear from it too |

Python’s standard library knows the middle row is special. In Python 3.15.0:

```
>>> import ipaddress
>>> a = ipaddress.ip_address("100.64.12.7")
>>> a.is_private, a.is_global
(False, False)
>>> ipaddress.ip_address("10.20.30.40").is_private
True
```

The documentation calls this out: for the shared address space, and only there, `is_private` and `is_global` are both `False`. If a modem’s cellular interface reports an address like that, the carrier is translating it, and the address a site sees will be a different one. Compare the two by opening the [IP check on the tools page](/tools/) through the proxy.

## What the carrier’s translator promises

RFC 6888 sets the requirements for a carrier-grade NAT, and two of them shape how a mobile exit behaves. REQ-2 makes “Paired” address pooling the default, so all of one subscriber’s connections leave through the same public address while the mappings last. The RFC’s justification is that applications depend on “the external address remaining constant”. REQ-4 says a CGN must support limiting the number of external ports assigned per subscriber.

Put those together and two practical points follow. Your parallel connections through one mobile exit share one public address, so spreading them across connections does not spread them across identities. And a burst of parallel connections can hit the carrier’s per-subscriber port limit, a ceiling you cannot see from your side and that no setting in your client raises.

The other half of the arrangement is in RFC 6302. Because one public address stands for many people, it recommends that internet-facing servers log the source port and a timestamp accurate to the second alongside the address. Without them, the RFC says, operators “will not be able to identify unambiguously customers” when they handle abuse reports. A site that logs only addresses sees a crowd behind each mobile exit. That is the property a mobile proxy sells.

The carrier decides when the public address changes. Rotating a mobile exit means reconnecting to the carrier and taking whatever address its pool assigns next, and that can also happen when you did not ask for it. Work that needs one identity for hours fits an [ISP proxy](/glossary/isp-proxy/) better.

## What it does not hide

A carrier address changes the network a site classifies you by. It does not change the request. A library’s default headers, a missing cookie jar and a TLS handshake no phone would send are all visible on a mobile exit exactly as on any other, and the study [Chromium varied all 12 captured handshakes. curl and Go stayed the same across 3 each](/research/tls-clienthello-fingerprints/) shows how far apart those handshakes are. When requests through a mobile exit still fail, the [403 vs 407 vs 429 guide](/guides/403-vs-407-vs-429/) separates a block at the target from a failure at the proxy.

## Frequently asked questions

### Why are mobile proxies harder to block?

Because a carrier's public address is shared by many subscribers through carrier-grade NAT. A site that blocks it may also block ordinary customers of that carrier, so the cost of the block falls on the site.

### Can I keep the same mobile IP for a long session?

Not reliably. The carrier decides when the public address changes, and a reconnect can move you to another address in its pool. If the work needs one stable identity, an ISP proxy fits better.

### How do I know a proxy is really mobile?

Look up the exit address's ASN and confirm it belongs to a mobile carrier rather than a hosting company. IP databases also record a connection type; MaxMind's, for example, uses Cellular for carrier ranges.

## Sources

1. [RFC 6598: IANA-Reserved IPv4 Prefix for Shared Address Space](https://www.rfc-editor.org/rfc/rfc6598.html)
2. [RFC 6888: Common Requirements for Carrier-Grade NATs](https://www.rfc-editor.org/rfc/rfc6888.html)
3. [RFC 6302: Logging Recommendations for Internet-Facing Servers](https://www.rfc-editor.org/rfc/rfc6302.html)
4. [RFC 1918: Address Allocation for Private Internets](https://www.rfc-editor.org/rfc/rfc1918.html)
5. [Python: ipaddress is_private and is_global](https://docs.python.org/3/library/ipaddress.html)
6. [MaxMind GeoIP web services: connection_type (Cellular)](https://dev.maxmind.com/geoip/docs/web-services/responses/)
