In this Article
Carrier-grade NAT, or CGNAT, lets an internet provider share a public IPv4 address among multiple subscribers. It conserves IPv4 addresses by translating connections and tracking their address and port mappings.
The translation happens inside the provider’s network, beyond equipment the subscriber controls. RFC 6888 defines carrier-grade NAT; the practical questions are whether your connection uses it and whether your application needs inbound access.

Key Facts
- CGNAT lets multiple subscribers share a public IPv4 address.
- 100.64.0.0/10 is reserved Shared Address Space.
- A WAN/public IPv4 mismatch suggests upstream translation.
- CGNAT and dynamic IP assignment describe different network properties.
- Local port forwarding alone cannot configure a carrier’s NAT.
- A mobile proxy’s shared public address does not prevent detection.
How CGNAT works
For TCP and UDP traffic, the translator maps an internal address and port to an external address and port. Return packets follow that mapping back to the correct subscriber. RFC 3022 explains network address and port translation.
Example: Two subscribers connect to the same website through one public IPv4 address. Different translated source ports let the gateway distinguish their connections. This does not reveal how many other subscribers share that address.
A CGNAT platform means the provider-side infrastructure implementing translation, mapping state and operational controls. It is not a browser proxy setting or a feature you can switch off on your phone.
CGNAT and private IPv4 address ranges
The main CGNAT address range is 100.64.0.0/10, covering 100.64.0.0 through 100.127.255.255. It is distinct from the private address ranges commonly used on home networks.
| Address space | CIDR block | What it tells you |
|---|---|---|
| Shared Address Space | 100.64.0.0/10 | A WAN address here is a strong clue to carrier-side translation. |
| Private IPv4 | 10.0.0.0/8 | May appear on a LAN or an upstream private network. |
| Private IPv4 | 172.16.0.0/12 | Covers 172.16.0.0 through 172.31.255.255. |
| Private IPv4 | 192.168.0.0/16 | A device address here alone does not establish CGNAT. |
Sources: RFC 6598 on Shared Address Space and RFC 1918 on private IPv4 addresses.
Not every address beginning with 100 belongs to Shared Address Space. Conversely, an ISP can use private addressing upstream, so the absence of a 100.64.0.0/10 address does not rule out CGNAT.
How to check whether you are behind CGNAT
Disable VPNs and proxies, then compare your router’s WAN IPv4 with your public IPv4. A mismatch suggests upstream translation but does not alone prove CGNAT.
Step 1: Use the connection you want to investigate. Pause VPNs, browser proxies and other traffic relays.
Step 2: Open the router or cellular gateway’s connection-status page. Record its internet-facing WAN IPv4, not your computer’s Wi-Fi address.
If your device does not expose its cellular WAN IPv4 address, you cannot complete this comparison. Ask your carrier whether the connection uses CGNAT; a public-IP lookup alone cannot confirm it.
Step 3: Check the public IPv4 visible from that connection at roughly the same time. Our guide to looking up an IP address explains the distinction. Compare IPv4 with IPv4, not IPv4 with IPv6.
Step 4: Classify the WAN address using the ranges above. Matching public addresses suggest no upstream IPv4 translation on that path; a mismatch needs investigation.
Step 5: Check for another modem-router ahead of your router. Local double NAT can produce the same mismatch. Ask your ISP whether your service uses CGNAT and whether public IPv4 is available.
TP-Link’s WAN/public-IP troubleshooting guide explains this comparison and upstream-NAT restrictions. A website-only checker cannot inspect your router’s WAN address, so treat its result as a clue rather than confirmation.
CGNAT vs dynamic and static IP addresses
CGNAT describes address sharing; dynamic and static describe address assignment over time. A changing public IP is not proof of CGNAT.
- Dynamic IP: The assigned address can change. It can still be a public address assigned directly to your connection.
- Static IP: The address stays assigned. A static private LAN address does not remove upstream NAT.
- CGNAT: Multiple subscribers share public IPv4 resources, whether the visible address changes frequently or stays the same.
RFC 2131 describes dynamic address allocation. See also static vs dynamic IP addresses.
If hosting is your goal, ask for a public, inbound-reachable IPv4 address. Asking only for a static address leaves the important reachability question unanswered. Likewise, getting a new IP address does not necessarily change the network’s translation arrangement.
How CGNAT affects port forwarding and gaming
CGNAT can complicate game hosting and inbound connections; ordinary gameplay may still work. A port-forwarding rule on your router does not create a matching rule on the carrier’s translator.
Peer-to-peer connectivity depends on mapping and filtering behavior, not simply the presence of NAT. RFC 4787 discusses NAT behavior needed by applications including online games.
- Ask about public IPv4: Confirm that inbound connections are permitted, then configure your router and host firewall.
- Ask about supported IPv6: Both endpoints and the application must support it. Configure the necessary firewall access; IPv6 does not mean every incoming connection is allowed.
- Ask about carrier-supported port mapping: RFC 6888 specifies subscriber mapping control, preferably through Port Control Protocol. Confirm actual availability with your ISP.
RFC 6092 explains residential IPv6 filtering. Keep firewall rules limited to the service you intend to expose.
Shared IP reputation, rate limits and geolocation
A shared public IP is an unreliable substitute for a person or precise location. Policies applied only to that IP can affect unrelated subscribers.
The 4-part CGNAT effect model separates the consequences:
| Effect | What changes | Practical consequence |
|---|---|---|
| Geolocation | The public prefix can represent a distant gateway. | A city estimate may not match the device. |
| Blocking | Subscribers share an address. | An IP block can affect uninvolved users. |
| Rate limiting | Requests accumulate under one IP. | Users may share a per-IP allowance. |
| Inbound connections | Another translation layer sits upstream. | Hosting needs a reachable path through it. |
RFC 6269 documents address-sharing effects, including reduced geolocation granularity. CGNAT does not disable device-based location methods.
Detection can also use request fingerprints and behavior, as described in Cloudflare’s research on residential proxy abuse. That research does not establish a mobile-proxy success rate. Shared IPs are not immunity from blocking.
Why mobile proxies share IP addresses
Mobile proxies inherit the carrier’s network setup, which may include CGNAT. Carrier-side sharing and a proxy service sharing access among customers are separate arrangements.
Neither arrangement establishes a fixed subscriber count. A mobile address also does not prove that the request came from a human using a phone.
New NAT mappings do not inherently change the public IP or terminate existing connections. Mapping expiration or network disruption can affect connectivity; RFC 4787 explains UDP mapping refresh behavior. Plan for reconnection without assuming every session will break.
For network selection, see mobile vs residential proxies. Use the following decision matrix:
| Choice | Use it when… | Avoid it when… |
|---|---|---|
| Mobile proxy | Use mobile proxies when your task specifically needs a cellular exit network. | Avoid mobile proxies when you require a fixed public identity or exact device location. |
| Residential proxy | Your task requires a residential exit IP but does not require a cellular network. | Your task specifically requires a cellular exit network. |
| Inbound hosting connection | Use an inbound-reachable connection when others must connect to your service. | Avoid treating an outbound proxy as a replacement for inbound connectivity. |
Mobile proxy limits and DataImpulse options
DataImpulse is our product: mobile proxies cost $2/GB, with no carrier selection. A mobile exit does not guarantee access, precise location or a permanent IP.
Regular residential proxies start at $1/GB. Country targeting is free; state, city, ZIP and ASN targeting count traffic at 2x on regular residential. Premium residential costs $5/GB with all targeting included.
DataImpulse does not sell ISP/static residential proxies.
Test mobile and residential proxies against the same target using the same request count and concurrency. Record successful responses, latency, traffic consumed, and observed IP changes.
Frequently Asked Questions
Frequently Asked Questions
What is CGNAT in simple terms?
It is address translation operated by your internet provider so subscribers can share public IPv4 addresses. The gateway tracks connections to return traffic to the right subscriber.
Does a 192.168 address mean I am behind CGNAT?
A 192.168 address on your laptop usually identifies its private LAN connection. Inspect the router’s WAN IPv4 and compare it with the public IPv4 before drawing conclusions about upstream translation.
Is CGNAT the same as a dynamic IP?
No. A dynamic address can change over time, while CGNAT concerns sharing public addresses. Either a stable or changing visible address can exist behind carrier-side translation.
Can I disable CGNAT on my router?
Your router does not control the carrier’s translator. Ask the ISP about an alternative connection arrangement; if the issue is local double NAT, investigate your own upstream router separately.
Does CGNAT stop online gaming?
Not necessarily. Connecting to a game server may work while hosting or peer-to-peer features encounter difficulties. Check which function fails before changing your network setup.
Can I host a service on a mobile connection?
It depends on whether the service has an inbound-reachable path. Ask the carrier about public IPv4, usable IPv6 or supported port mapping, then check firewall rules.
Why can mobile IP geolocation show the wrong city?
The database may associate the public address with the carrier’s gateway region rather than the handset. An IP-based city result is an estimate, not a device-location reading.
Are shared mobile proxies protected from blocking?
No. Websites can still block shared addresses or evaluate other request signals. Address sharing does not guarantee successful requests.
Last updated: November 10, 2026.

State/City/Zip/ASN Targeting 



