CGNAT and double NAT, and whether they affect streaming

What NAT does in the first place

Your home has one public address and many devices. Network Address Translation is what lets them share it: the router rewrites outgoing traffic so everything appears to come from that one address, and remembers enough to send replies back to the right device.

This happens on every home network and is entirely normal. The two terms below describe it happening more than once.

Double NAT

Double NAT means two routers in a chain, each translating. Usually you have a provider-supplied modem-router and have added your own behind it, and the first was never put into a pass-through mode.

The signature is a router whose own internet address is a private one — starting 192.168, 10., or between 172.16 and 172.31. A router reporting a private address on its WAN side is behind another router.

Does it affect streaming?

Almost never. Your player makes outgoing connections, which pass through both layers without difficulty. What double NAT breaks is anything needing incoming connections — hosting a game server, some remote-access tools — none of which apply here.

It does add a small amount of latency and one more device to fail, so it is worth removing where easy. Putting the first router into modem or bridge mode is the usual fix.

Carrier-grade NAT

CGNAT is the same idea one level up: your provider translates too, sharing one public address between many customers. It is increasingly common because addresses ran short years ago.

You can detect it by comparing the address your router shows on its WAN side with the address a "what is my IP" site reports. If they differ, and your router's is private, you are behind CGNAT.

Does it affect streaming?

Again, almost never, for the same reason: outgoing connections work normally.

There is one indirect effect worth knowing. Because you share a public address with other customers, a service that rate-limits or blocks by address may occasionally treat your traffic as part of someone else's pattern. This is uncommon, and the signature is distinctive: a service failing entirely for a period and then working again, unrelated to anything you changed.

How to check, quickly

• Find your router's WAN or internet address in its status page.
• Visit any "what is my IP" site and note what it reports.
• They match, and the address is public — no CGNAT, no double NAT.
• They differ, and your router's is private — you are behind CGNAT, your provider's double NAT, or your own second router.
• Your router's WAN address is private and there is another router upstream — that is your own double NAT to remove.

What actually causes the symptoms these get blamed for

CGNAT tends to be blamed for buffering, dropouts and channels that will not load. It causes none of those.

• Buffering is throughput and steadiness — see the buffering guide.
• Channels that will not load are usually credentials, the channel itself, or the player, worked through in the troubleshooting guide.
• Intermittent dropouts are more often Wi-Fi or a router needing a restart.

The reason this matters is that CGNAT is not something you can change without a conversation with your provider, so believing it is the cause means giving up on problems that are actually fixable.

When it is worth acting

Removing your own double NAT is worthwhile housekeeping — put the provider's box into bridge mode and let one router do the job. It simplifies diagnosis later even if it changes nothing today.

Asking your provider to move you off CGNAT is worth doing only if you have a specific need for incoming connections. For watching television, it is not a problem worth the phone call.

Frequently asked questions

Related articles