ARTICLE · 7 MIN READ

How to Check for CGNAT on Your Internet Connection

How to Check for CGNAT on Your Internet Connection

A game server that works on your home Wi-Fi but cannot be reached by friends, a security camera that fails outside the house, or a VPN that will not accept inbound connections can all point to the same issue: carrier-grade NAT. The fastest way to learn how to check for CGNAT is to compare the WAN IP address assigned to your router with the public IP address the internet sees.

CGNAT is common on mobile, fixed wireless, satellite, and some fiber or cable services. It is not automatically a problem. For normal browsing, streaming, video calls, and most online games, you may never notice it. It matters when you need a direct inbound connection from the internet, such as port forwarding for a game server, remote desktop, NAS, camera system, or self-hosted service.

What CGNAT Means

CGNAT stands for Carrier-Grade Network Address Translation. Your internet service provider uses it when many customers share one public IPv4 address. Instead of assigning a unique public IPv4 address to your router, the ISP gives your router a non-public address and translates traffic again within its own network.

Think of it as two reception desks between your device and the public internet. Your home router handles the first translation between your private home network and its WAN connection. The ISP handles the second translation before traffic reaches the shared public IPv4 address.

This arrangement conserves scarce IPv4 addresses. The trade-off is that unsolicited inbound traffic reaches the ISP’s shared address first. Unless the ISP specifically supports a forwarding arrangement, it has no way to know which customer’s router should receive that connection.

How to Check for CGNAT: Compare Two IP Addresses

The most reliable home-user check takes only a few minutes. You need the WAN or Internet IP address shown by your router and the public IPv4 address reported by an external IP lookup.

1. Find your router’s WAN IP address

Sign in to your router’s administration page. The location varies by manufacturer, but look for a page labeled Internet, WAN, Status, Connection Status, or Network Map. Find the value called WAN IP Address, Internet IP Address, or IPv4 Address.

Do not use the IP address shown on your computer or phone’s Wi-Fi settings. That is usually a private LAN address, such as 192.168.1.25, assigned by your router. It only identifies your device inside your local network.

If you use a separate modem and router, make sure you are viewing the IP address on the device connected to the ISP. A modem-router gateway may show it on its status page. With a standalone modem in bridge mode, your own router should show the relevant WAN address.

2. Check the public IP seen from the internet

Open an IP lookup page in a browser connected to the same network. WhatIsMyPublicIP.com displays the public IPv4 address currently visible to websites, along with location information. Record that address, then compare it with the router’s WAN IPv4 address.

For a typical connection with a public IPv4 address, the two values should match. They can change over time because many residential plans use dynamic addressing, so compare them during the same session.

3. Interpret the result

If the addresses match and the router’s WAN address is public, you are generally not behind CGNAT for IPv4. You may still have a firewall, port-forwarding rule, or double-NAT issue to solve, but the ISP is not translating your connection behind a shared address.

If the addresses differ, inspect the WAN address. A WAN address in the following ranges is not publicly routable:

  • 100.64.0.0 through 100.127.255.255, the shared-address range reserved specifically for CGNAT
  • 10.0.0.0 through 10.255.255.255
  • 172.16.0.0 through 172.31.255.255
  • 192.168.0.0 through 192.168.255.255

An address in the 100.64.0.0/10 range is a strong indicator of CGNAT. The other private ranges show that another NAT device exists upstream of your router. That device may belong to your ISP, which is effectively CGNAT from your perspective, or it may be an ISP-provided gateway that has not been placed in bridge mode.

If your router has a public-looking WAN address but it does not match the browser result, contact the ISP before assuming CGNAT. Some providers use unusual network designs, public-address pools, or managed equipment that can make a simple comparison less clear.

Confirming CGNAT With a Port Test

A comparison of addresses usually gives the answer, but a port test can confirm why inbound access is failing. First, configure a port-forwarding rule on your router for an application that is actively listening on that port. For example, a game server or web server must be running while you test.

Then test that port from outside your home network. Use a phone on cellular data, a remote system, or an external port-checking tool. Testing from another device on the same Wi-Fi network can produce misleading results because some routers do not support NAT loopback.

If the router WAN IP is public, the forwarding rule is correct, the local firewall allows the application, and the port remains unreachable, investigate ISP filtering or application configuration. If the WAN IP is in the CGNAT range, opening the port in your router alone cannot make it reachable. The ISP’s NAT layer is still in front of it.

A closed-port result by itself does not prove CGNAT. The application may not be listening, the wrong local IP may be in the forwarding rule, your operating system firewall may block it, or the ISP may block that port. Treat the port test as supporting evidence, not the first test.

Can Traceroute Reveal CGNAT?

Traceroute can provide another clue, especially for experienced users. Run a traceroute to a public destination and look at the early hops after your router. If you see addresses in 100.64.0.0/10 or private address ranges, your traffic is passing through non-public ISP infrastructure.

However, traceroute is not definitive. Routers can suppress replies, reply from a different interface, or use addresses that do not reflect the exact translation point. A timeout does not indicate CGNAT, and a private hop does not always explain every connection problem. The router WAN address and public IP comparison remains more useful.

CGNAT vs. Double NAT

CGNAT and double NAT create similar symptoms, but the fix is different. Double NAT occurs when two devices you control are acting as routers. A common setup is an ISP gateway routing traffic to a second Wi-Fi router. Your personal router receives an address such as 192.168.0.x on its WAN interface.

You may be able to fix double NAT by putting the ISP gateway into bridge mode, using IP passthrough, or placing the downstream router in the gateway’s DMZ. The correct choice depends on the equipment and whether you still need the gateway’s Wi-Fi, phone service, or management features.

CGNAT exists within the provider’s network, beyond equipment in your home. Restarting your router, changing its LAN subnet, or adding more port-forwarding rules will not remove it.

What to Do If You Are Behind CGNAT

Start by asking your ISP whether it offers a public IPv4 address. Some providers can remove customers from CGNAT on request. Others offer a public or static IPv4 address as a paid add-on, often aimed at business users, remote workers, and people hosting services.

A static IP is convenient but not always required. A dynamic public IPv4 address can still support port forwarding if you use a dynamic DNS service to track address changes. Ask whether the public address is truly routable and whether inbound ports are filtered.

IPv6 may be another option. If your ISP gives you a globally routable IPv6 prefix, devices can be reachable without IPv4 NAT. That does not mean they are automatically reachable safely. You must configure IPv6 firewall rules carefully, and visitors or services that only support IPv4 will still need another path.

For remote access, an overlay VPN or mesh VPN can avoid the need for inbound port forwarding. For hosting a public service, a cloud server, reverse proxy, or tunnel service may be a better fit. These options add cost, complexity, or dependency on another provider, but they can work when a public IPv4 address is unavailable.

Before changing equipment or paying for an add-on, capture your router WAN address and public IP result, then give both to your ISP’s support team. That small piece of evidence turns a vague “my ports are blocked” report into a clear question about whether your connection is behind CGNAT and what public-address options are available.