Skip to content

What Is CGNAT? Carrier-Grade NAT and Why Strangers Share One IP

CGNAT shares one public IPv4 address among many users. How carrier-grade NAT works, how to spot it, what it breaks, and the ways around it.

Billal AinaouiJuly 21, 2026Updated November 7, 202616 min read

What Is CGNAT? Carrier-Grade NAT and Why Strangers Share One IP

CGNAT, short for carrier-grade NAT, is how an internet provider shares one public IPv4 address among many subscribers. It exists because IPv4 ran out, and it blocks incoming connections such as port forwarding. Mobile networks run it almost everywhere: a 2016 study found it in more than 90% of them.

How hard the sharing runs depends on the network. We divided APNIC Labs' user estimates by the IPv4 addresses each network announces. On Globacom in Nigeria that comes to 386 users per address, on Reliance Jio in India to 68, and on Comcast in the US to 0.7. For proxies it settles two things: a shared address is costly for a site to block, and a device behind one cannot take incoming connections.

What is CGNAT?

CGNAT is network address translation run by the internet provider, one level above your home router. Your router already shares one address among the devices in your home. A carrier-grade NAT does the same for thousands of customers, so many homes or phones leave the internet from one public IPv4 address.

What is CGNAT?

CGNAT

a network technique

Network address translation run by an internet provider to share one public IPv4 address among many subscribers. Each customer gets a private address, and the provider rewrites their traffic to leave from a shared public one.

Also called
carrier-grade NATlarge-scale NATNAT444
Source: RFC 6888; RFC 6598 · hproxy.comProxy.

RFC 6888 sets the rules for these devices. It defines a CGN as a NAT function "used to share the same IPv4 address among several subscribers". The provider runs it, and the subscriber has no control over it. The RFC says so plainly: "A CGN is not managed by the subscribers."

How does carrier-grade NAT work?

Follow one request. Your device has a private address from your router, and your router has a private address from the provider. When you load a page, the provider's NAT rewrites the source to one of its shared public addresses. It remembers the mapping, so the reply finds its way back. Your traffic is translated twice, which is why engineers also call this setup NAT444.

One request through carrier-⁠grade NAT
  1. Your device

    a private address from your router

  2. Home router

    a 100.64.x.x address from the provider

  3. Carrier-grade NAT

    rewrites it to a shared public IPv4

  4. Website

    sees one address for many subscribers

Source: RFC 6888; RFC 6598 · hproxy.comProxy.

The sharing runs on ports. Each connection behind the shared address gets its own port number, and RFC 6888 sets rules for handing them out. REQ-4 says a CGN "MUST support limiting the number of external ports" per subscriber, so one heavy user cannot take them all. REQ-8 says a freed port should wait "at least 120 seconds" before it goes to someone else.

Providers set those limits in practice. Starlink caps its Residential and Roam plans at 1,200 concurrent sessions, and it counts every TCP or UDP connection as one. Past the cap, Starlink says, "new sessions automatically cause the oldest sessions to be dropped". It warns that "real-time communication tools" in particular need a high number of active sessions.

What is the 100.64.0.0/10 range?

It is the Shared Address Space, reserved in April 2012 by RFC 6598. The RFC set it aside "to accommodate the needs of Carrier-Grade NAT (CGN) devices". Providers use it to number the link between their NAT equipment and your router. It runs from 100.64.0.0 to 100.127.255.255, which is 4,194,304 addresses.

A separate range was needed because homes already use the private ranges. If the provider numbered its side with 10.x addresses and your home network used 10.x too, the two would collide. RFC 6598 notes that Shared Address Space "is intended for use on Service Provider networks", unlike the private ranges of RFC 1918.

Why do internet providers use CGNAT?

IPv4 has room for about 4.3 billion addresses, and the registries ran out of free ones in the early 2010s. Cloudflare puts it simply: "While the long-term solution is the transition to IPv6, CGNAT emerged as the immediate, practical workaround."

How common is it? A study presented at the ACM Internet Measurement Conference in 2016 found CGNAT in 17 to 18% of the networks that connect end users. In cellular networks it found it in more than 90%. Some operators in that study reported as many as 20 subscribers per IPv4 address. Cloudflare wrote in 2025 that "a single IPv4 address may represent hundreds or even thousands of users".

How many people share one IPv4 address?

No provider publishes that number, so we estimated it. APNIC Labs, the research group of the Asia-Pacific address registry, estimates how many users each network serves from its own ad measurements. The RouteViews routing table, published by CAIDA, shows how many IPv4 addresses each network announces. We took the three networks with the most users in 14 countries, 42 in all, and divided users by addresses.

Estimated users per IPv4 address, by networkAPNIC user estimates divided by the IPv4 addresses each network announces, early November 2026
GlobacomNigeria, mobile
386
RobiBangladesh, mobile
351
GrameenphoneBangladesh, mobile
194
Total PlayMexico, home broadband
167
BanglalinkBangladesh, mobile
109
Zong (CMPak)Pakistan, mobile
75
MTN NigeriaNigeria, mobile
72
Reliance JioIndia, mobile
68
Deutsche TelekomGermany
0.8
ComcastUnited States
0.7
On the busiest networks of Nigeria and Bangladesh, hundreds of users share each IPv4 address.
Source: APNIC Labs user estimates per network, November 2, 2026; RouteViews routing table via CAIDA, November 5, 2026; our calculation · hproxy.comProxy.

Globacom came first, with 10.3 million estimated users on 26,624 addresses. All of the top ten but one were mobile carriers; the exception, Total Play, sells home broadband in Mexico. Reliance Jio, India's largest network, served 287 million estimated users from 4.2 million addresses. At the other end, Comcast announces 68.2 million addresses for 44.6 million users, more than one address each.

The ratio measures pressure on a network's IPv4 space. It cannot say whether one particular customer sits behind CGNAT. Jio carries much of its traffic over IPv6, so its users lean on its IPv4 addresses less than the ratio suggests. Nigeria, where APNIC counted 5.6% of users as IPv6-capable in October 2026, has no such relief.

Which internet providers use CGNAT?

Most providers do not say. Two that document it are Starlink and T-Mobile's home internet service.

Starlink. Its default IPv4 policy "uses Carrier-Grade Network Address Translation (CGNAT) using private address space from the 100.64.0.0/10 prefix". That policy "does not allow inbound traffic". A public IPv4 address is "an optional configuration available to Local and Global Priority customers", and Starlink's own router "does not support port forwarding" at all. Every Starlink also receives an IPv6 /56 prefix.

T-Mobile home internet. T-Mobile's support page says its gateways "do not have the ability to enable and disable NAT/port forwarding" or to change the NAT type. It cannot switch a line from a dynamic to a static IP either. Calling services that support IPv6 work, the page adds. An engineer at T-Mobile USA co-wrote RFC 6877, which describes 464XLAT: "limited IPv4 connectivity across an IPv6-only network".

Mobile carriers. Here the 2016 study's figure of more than 90% applies, and the chart above shows the scale on the largest networks.

How do you know if you are behind CGNAT?

Compare two addresses:

  1. Your public IP. Our proxy IP checker shows the address a site sees.
  2. Your router's WAN address. Open the router's admin page and read the internet or WAN address.

If the WAN address falls between 100.64.0.0 and 100.127.255.255, you are behind CGNAT. That is what a Starlink router shows on the default plan. If it is another private address, such as 10.x or 192.168.x, some other NAT sits in front of you. If the WAN address and your public IP match, you hold a public address of your own. On mobile data, CGNAT is the normal case.

Is CGNAT bad?

For browsing, streaming and apps that only connect outward, you will rarely notice it. It hurts in two places: incoming connections and shared reputation.

Incoming connections. Nothing on the internet can open a connection to you, because the public address is not yours alone. Port forwarding, game hosting and remote access to a home device break. The IETF tested real applications behind CGNAT for RFC 7021. Some "did not first send outgoing traffic and hence did not open an incoming port through the CGN". Peer-to-peer gaming on Xbox failed in those tests.

Shared reputation. Whatever one user does, every user on the address carries. RFC 7021 warns about a shared address that "is added to a blacklist" or meets a per-address connection limit. Either way, "it could negatively impact legitimate users". Cloudflare measured exactly that in 2025:

Bot traffic behind CGNAT and other IP addressesShare of requests Cloudflare scored as bots, per IP address
  • CGNAT addresses
  • Other addresses
Median bot rate
4.8%
4.7%
Mean bot rate
7%
13.1%
CGNAT addresses carried no more bot traffic, yet Cloudflare found them rate-limited three times as often.
Source: Cloudflare, One IP address, many users: Detecting CGNAT to reduce collateral effects, October 29, 2025 · hproxy.comProxy.

The median bot rate was 4.8% on CGNAT addresses against 4.7% on others, and the mean was lower, 7% against 13.1%. Yet CGNAT addresses were "subject to rate limiting three times more often than non-CGNAT IPs". Per-address rules punish the crowd for one user. Our guides to a Discord IP ban and to being blocked from editing Wikipedia show how that lands on real people.

There is one upside. Cloudflare notes that CGNAT has "the positive side effect of protecting many home devices that might be vulnerable to compromise". Nothing outside can reach them directly.

Is CGNAT bad for gaming?

It can be, for hosting and voice chat. Consoles grade how easily other players can reach you. Xbox calls the grade a NAT type and says, "You need your NAT type to be Open" to fix multiplayer and party chat problems. Its usual fixes, turning on UPnP and forwarding ports, work on your own router. Behind CGNAT they stop at the provider's NAT. Tailscale's engineers put it plainly: "you can't reconfigure the ISP's CGNAT!"

T-Mobile gives gamers the same answer for its home internet. Settings such as "NAT/Port forwarding, UPnP/Static IP" for gaming consoles "cannot be configured on the T-Mobile gateway". Matches still work when the game runs its own servers, since your console connects out to them.

What decides the rest is how the NAT treats ports. RFC 4787, the standard for NATs and UDP traffic, rules that "A NAT MUST have an 'Endpoint-Independent Mapping' behavior". Such a NAT keeps the same outside port for one device whoever it talks to. Tailscale calls that kind an easy NAT. A NAT that changes the port per destination is a hard NAT, and Tailscale writes that "these hard NATs are a big problem" for direct connections.

How do you get around CGNAT?

The provider's NAT stays where it is. Each way below gives incoming connections a path around the shared address.

Way around itInbound?What it needs
Public IPv4YesYour provider
IPv6YesBoth ends
Outbound tunnelYesA server
Dynamic DNSNoOnly a name
A proxyNoOutbound only

Ask for a public IPv4 address. RFC 6888 expects CGNAT to run alongside other services, "such as IPv6 services or regular IPv4 service assigning public addresses to subscribers". Some providers sell that as an option. On Starlink, Priority plans include a public IP address "and do not have the session limitations associated with CGNAT".

Use IPv6 where both ends have it. IPv6 traffic needs no shared address, so a device with an IPv6 address can accept connections from other IPv6 devices. Your router's firewall still decides what gets in.

Tunnel out to a server that has a public address. The connection starts from inside your network, so the CGNAT treats it like any other outgoing traffic. Cloudflare describes its Tunnel product this way: it "uses an outbound-only connection model to enable bidirectional communication". A rented server and an SSH reverse tunnel do the same job by hand; our SSH SOCKS proxy guide covers the tool. For peer-to-peer apps, Tailscale falls back to "a relay that both sides can talk to unimpeded" when no direct path exists.

What does not help. Dynamic DNS gives an address a name, and the shared address still refuses connections. A proxy changes the address your outgoing traffic uses. It opens no door inward.

Does CGNAT hide who you are?

It hides you from the website, which sees only the shared address. It does not hide you from your provider. RFC 6888 notes that a provider may need "to identify a subscriber" from the external address, port and timestamp. The reason it gives is "to deal with abuse". RFC 6302 asks the other side to keep its half of that trail. It recommends that internet-facing servers log the source port of each connection, along with the address and an accurate timestamp.

Keeping that trail is expensive for the provider. RFC 7422 cites US operators at about 33,000 connections per household a day. Logged one by one, that is about 5 MB per subscriber a day. A provider with a million subscribers would store about 150 TB a month. RFC 7422 proposes assigning port ranges so that providers can "significantly reduce the amount of logging required while providing traceability for abuse response".

With the address, the port and the time, a provider can trace a request back to one subscriber. Sharing an address spreads its reputation across many people, and a log can still single one of them out.

Is CGNAT the same as a proxy?

They sit in different places. Your provider runs CGNAT, and you cannot choose or switch it off. A proxy is something you pick: RFC 9110 defines it as "a message-forwarding agent that is chosen by the client". You can use a proxy from behind CGNAT, and then a site sees the proxy's exit address and never your provider's shared one.

Does IPv6 replace CGNAT?

Over IPv6, yes, where the provider offers it. IPv6 has enough addresses for every device, so IPv6 traffic needs no shared IPv4 address. Adoption is uneven. APNIC Labs measures the share of users who can use IPv6 in each country:

Users who can use IPv6, by countryIPv6-capable share of users, 30-day average to October 19, 2026
France
85.8%
India
76.3%
Germany
72.4%
United States
62.3%
Brazil
59.7%
United Kingdom
54.5%
China
49%
Indonesia
29.5%
Kenya
16.5%
Nigeria
5.6%
South Africa
4.3%
Source: APNIC Labs IPv6 measurement, per country, read October 22, 2026 · hproxy.comProxy.

Where IPv6 is rare, more traffic depends on shared IPv4 addresses. Cloudflare found the highest ratios of users to IPv4 addresses in large parts of Africa and South Asia. It also found that "Africa has a much higher ratio of user agents to IP addresses than other regions". Our own count above points the same way, with Nigeria and Bangladesh at the top.

What does CGNAT mean for proxies?

Mobile proxies sit on shared addresses. A mobile proxy exits from a carrier address, and carriers run CGNAT almost everywhere. A site that blocks such an address blocks every subscriber behind it, the collateral damage RFC 7021 and Cloudflare both describe. Our guides to what a mobile proxy is and mobile vs residential proxies go further. Our mobile proxies cost $1.50 per GB.

A shared address is no free pass. Sites have started to count users behind a shared address separately. Cloudflare's rate limiting rules offer a key called "IP with NAT support". Cloudflare describes it as a way "to handle situations such as requests under NAT sharing the same IP address". Its 2025 post says it uses its CGNAT detection to tune its security features.

Reputation is shared too. We read Scamalytics' list of its highest-risk addresses on October 22, 2026. It held mobile carriers such as Claro and MTN Nigeria at a score of 100. Many people sharing one address can give it a record that none of them earned alone.

Free proxies almost never sit on mobile networks. On October 22, 2026, 4,992 free proxies were working on our list. Only 4 sat on mobile carrier addresses. A free proxy is a server that waits for strangers to connect. RFC 7021 found that an application behind CGNAT that does not connect out first opens no port the outside can reach.

A datacenter IP is the opposite case. It belongs to a hosting network, which a site can identify through its ASN, and nobody else shares it. A home connection with its own address sits in between; our guide to residential IP addresses explains how sites read it. Our dedicated datacenter addresses and IPv4 or IPv6 options cover the far end, and our pricing page lists every product.

What this page could not check

  • Who runs CGNAT today. No registry lists it. The shares by network come from the 2016 IMC study, and newer per-network figures are not public.
  • Our users-per-address count. It shows how hard a network's IPv4 space is shared, not whether a given customer sits behind CGNAT. APNIC's users are estimates from ad measurements. An operator can announce addresses under more than one network number, and users who reach a site over IPv6 still count in the ratio.
  • Provider pages. Starlink's and T-Mobile's help pages carry no dates and change with their plans. We read them on November 7, 2026.
  • Cloudflare's view. The bot and rate-limit figures describe traffic Cloudflare sees, in a 2025 post updated July 15, 2026.
  • Capable is not used. APNIC measures whether users can use IPv6. Their traffic to IPv4-only sites still needs an IPv4 address.
  • Our free list only. The mobile count covers the public free proxies our checker collects.
  • Check by February 7, 2027. Plan terms, APNIC estimates, routing tables and IPv6 shares all move.

Sources

  • RFC 6888: Common Requirements for Carrier-Grade NATs (CGNs). IETF, April 2013.
  • RFC 6598: IANA-Reserved IPv4 Prefix for Shared Address Space. IETF, April 2012.
  • RFC 7021: Assessing the Impact of Carrier-Grade NAT on Network Applications. IETF, September 2013.
  • RFC 7422: Deterministic Address Mapping to Reduce Logging in Carrier-Grade NAT Deployments. IETF, December 2014.
  • RFC 4787: Network Address Translation (NAT) Behavioral Requirements for Unicast UDP. IETF, January 2007.
  • RFC 6877: 464XLAT, Combination of Stateful and Stateless Translation. IETF, April 2013.
  • RFC 6302: Logging Recommendations for Internet-Facing Servers. IETF, June 2011.
  • RFC 9110: HTTP Semantics. IETF, June 2022.
  • A Multi-perspective Analysis of Carrier-Grade NAT Deployment. Richter and others, ACM Internet Measurement Conference, 2016.
  • One IP address, many users: Detecting CGNAT to reduce collateral effects. Cloudflare blog, October 29, 2025, updated July 15, 2026.
  • Rate limiting rule parameters. Cloudflare developer documentation, read October 22, 2026.
  • Cloudflare Tunnel. Cloudflare developer documentation, read November 7, 2026.
  • What IP address does Starlink provide?, What are CGNAT session limits and how do they affect my connection? and Can I port forward with the Starlink router? Starlink Help Center, read November 7, 2026.
  • Connect your Devices to T-Mobile Internet. T-Mobile support, read November 7, 2026.
  • Troubleshoot NAT errors and multiplayer game issues. Xbox Support, read November 7, 2026.
  • How NAT traversal works. Tailscale, August 2020, read November 7, 2026.
  • Visible ASNs, customer populations (estimated), per economy. APNIC Labs, dated November 2, 2026.
  • RouteViews prefix-to-AS mapping of November 5, 2026, 12:00 UTC. CAIDA.
  • IPv6 measurement per country. APNIC Labs, 30-day average to October 19, 2026, read October 22, 2026.
  • IP fraud check, list of high-risk addresses. Scamalytics, read October 22, 2026.
  • HProxy free proxy list, working addresses by network type, October 22, 2026, 06:57 UTC.

Frequently asked questions

What is CGNAT?

CGNAT, or carrier-grade NAT, is how an internet provider shares one public IPv4 address among many subscribers. RFC 6888 defines it as a NAT function used to share the same IPv4 address among several subscribers. Each customer gets a private address, and the provider's NAT rewrites their traffic to leave from a shared public one.

What is the 100.64.0.0/10 range?

It is the Shared Address Space that RFC 6598 reserved in April 2012 for carrier-grade NAT. Providers use it to number the link between their NAT equipment and your router, so it never collides with the 10.x or 192.168.x ranges inside your home. It runs from 100.64.0.0 to 100.127.255.255.

How do I know if I am behind CGNAT?

Compare two addresses. Check the public IP that websites see, then read the WAN or internet address in your router's admin page. If the router shows an address from 100.64.0.0 to 100.127.255.255, you are behind CGNAT. If it shows any other private address and the public IP differs, another NAT sits in front of you.

Can you port forward behind CGNAT?

Not on the provider's side. A forwarding rule on your router opens a port on an address the provider has already translated, and nothing outside can reach it. Starlink says its default CGNAT policy does not allow inbound traffic, and T-Mobile says port forwarding cannot be set on its home internet gateways. The ways in are a public IPv4 address from the provider, IPv6, or a tunnel to a server that has a public address.

Does Starlink use CGNAT?

Yes, by default. Starlink documents its default IPv4 policy as carrier-grade NAT on the 100.64.0.0/10 range, with no inbound traffic. Its Residential and Roam plans are capped at 1,200 concurrent sessions. A public IPv4 address is an option on the Local and Global Priority plans, and every Starlink also receives an IPv6 prefix.

Is CGNAT bad?

For browsing and streaming it is usually invisible. It hurts anything that needs incoming connections, such as port forwarding, game hosting and some peer-to-peer apps. Sharing an address also means sharing its reputation: Cloudflare found CGNAT addresses were rate-limited three times as often as other addresses, with no more bots behind them.

Can IPv6 get around CGNAT?

Over IPv6, yes, where your provider and the other side both offer it, because IPv6 does not run out of addresses and needs no shared IPv4 address. Cloudflare calls IPv6 the long-term solution and CGNAT the immediate workaround. Adoption varies widely: about 62% of users in the US could use IPv6 in October 2026, against 4% in South Africa.

What does CGNAT mean for mobile proxies?

Mobile carriers use CGNAT almost everywhere, so a mobile proxy usually exits from an address that many real subscribers share. Blocking it hits all of them, which RFC 7021 warns about. Sites now try to tell users apart behind a shared address, so a shared IP is no free pass.

Proxies that don't die mid-job

Residential, ISP, datacenter and mobile, verified by the same engine that runs tens of millions of checks. They read as a real device and hold up under load. Pay as you go, and your balance never expires. $0.23/GB is the 10,000 GB+ rate; a single gigabyte is $0.50/GB, with no minimum order.

129M+ proxy checks run · 100+ countries · HTTP / HTTPS / SOCKS · re-checked every few minutes · no signup

HProxy.

Honest guides and comparisons on proxies, scraping and staying unblocked, from the team that runs the network.

RSS feed