CGNAT, or carrier-grade network address translation, lets an internet provider share public IPv4 addresses among multiple subscribers. Your router can have an address inside the provider’s network while internet services observe a different, shared public address. That is different from manually configuring an HTTP or SOCKS proxy in an application.
CGNAT matters when you want to accept incoming connections or explain why the public IP reported by a website differs from your router’s connection address. It is not, by itself, evidence that a connection is broken or that your device is using a commercial proxy.
Key points: compare the router’s WAN address with an external observation, ask the provider how the connection is delivered, and separate inbound connectivity from outbound browsing. An IP lookup alone cannot establish the complete network topology.
RFC 6598 reserves 100.64.0.0/10 as Shared Address Space for service-provider use. That block runs from 100.64.0.0 through 100.127.255.255. It is distinct from the private address ranges often used inside home networks.
The range is a useful clue when it appears on your router’s WAN interface. It is not a magic detection rule for every provider configuration. Record which interface displayed the address: a local Wi-Fi adapter and the router’s internet-facing interface answer different questions.
Start with your own router’s connection status page. Find the WAN or internet IPv4 address and record it privately. Then use an external IP lookup in the browser connected through that router. The What is my IP tool performs that kind of browser-side observation.
If the addresses differ, you have evidence of an address translation or routing difference to investigate. Before drawing a conclusion, account for a browser proxy, VPN, another router or another internet connection. Tell the provider what you observed and ask whether your service uses CGNAT and whether a public IPv4 option is available.
A practical note-taking format is:
| Observation | Record privately |
|---|---|
| Router interface | WAN or internet, not the local LAN address |
| Address family | IPv4, kept separate from IPv6 |
| External observation | Address seen for the same connection |
| Extra network layers | VPN, proxy, second router or tethering |
| Provider answer | Whether CGNAT is used and what options exist |
The table organizes evidence. It does not turn an external lookup into a definitive network audit.
A port-forwarding rule on your own router controls that router. It does not create a corresponding mapping on equipment operated by your provider. If an incoming connection must also cross the provider’s translation layer, changing only the home router may not make the service reachable.
For a service you own, ask about a public address or another supported inbound-connectivity option. Consider the application’s authentication and exposure requirements before making it internet-accessible. Do not assume that paying for an outbound proxy will configure inbound forwarding to your home network.
A proxy is selected by an application or network configuration to relay particular traffic. CGNAT is part of how the provider delivers connectivity. You can encounter both on the same path: the provider may translate the connection that your application uses to reach a proxy.
This distinction matters when choosing a fix. If your goal is inbound access to a home service, first discuss that requirement with your internet provider. If your goal is routing supported application requests through a selected endpoint, use the proxy setup and checking guide.
No. Sharing an address is not a complete privacy model. Applications can use account information and browser state, while network operators have their own records and technical responsibilities. A public IP does not uniquely describe a person, and its presence does not prove that a particular subscriber performed a particular action.
Keep troubleshooting claims narrow. “The site observed this address for my request” is an observation. “The connection is anonymous” is a much larger assertion that an IP lookup does not establish.
It is commonly encountered on connections that can make outbound requests. If browsing fails, diagnose the actual symptom rather than treating the CGNAT label as the explanation for every error.
Your router cannot change the provider’s service configuration. Ask the provider what addressing and inbound-connectivity options are available for your connection.
An outbound HTTP or SOCKS proxy is not a substitute for a supported way to reach your own service from the internet. Match the tool to the direction of the connection you need.