RIPE NCC ran out of IPv4 in 2019. A growing service provider can now get IPv4 only through the waiting list or the transfer market, and both are slow and expensive. IPv6 is the long-term answer, but much of the content subscribers reach is still IPv4-only. CGNAT closes that gap.

How CGNAT works

Carrier-Grade NAT is the address translation a home router does, performed at service provider scale. Instead of a public IP, the subscriber gets an address from the 100.64.0.0/10 shared address space reserved by RFC 6598. The subscriber's CPE already runs NAT for the home network, so traffic is translated twice on its way out. With three address layers, the design is called NAT444:

  1. The subscriber's home network (e.g. 192.168.1.0/24)
  2. The provider's shared address space (100.64.0.0/10)
  3. Public IPv4

A public IP has roughly 64,000 usable ports. CGNAT shares them across subscribers so one address serves dozens of customers.

Why port block allocation matters

With classic NAT, every new connection creates a log entry. On a busy network that means hundreds of thousands of lines per second, all of which must be retained under data-retention rules such as Türkiye's Law 5651. Storage and query costs climb fast.

Port block allocation (PBA) fixes this. CGNAT gives each subscriber a fixed-size block of ports on a public IP, for example 1,008 ports. The subscriber opens as many connections as they like inside that block, and a log line is written only when the block is assigned and released. You end up with a few lines per subscriber instead of one per session.

Deterministic NAT goes one step further: the public IP and port range are calculated from the subscriber's private address. Tracing then needs no NAT logs; only the mapping rule and the subscriber-to-private-IP records are kept.

Application compatibility

A few behaviours keep CGNAT invisible to subscribers:

  • EIM / EIF (Endpoint-Independent Mapping / Filtering): needed by game consoles, VoIP and P2P applications.
  • Hairpinning: lets two subscribers behind the same CGNAT reach each other via public addresses.
  • ALG: translation support for protocols that carry addresses inside packets, such as FTP, SIP and PPTP.

With these behaviours configured correctly, most subscribers never notice they are behind CGNAT. Business customers who need a fixed IP can still get one from a separate public pool.

How to size it

Three figures drive CGNAT sizing:

  • Throughput: total traffic at the evening peak.
  • Concurrent sessions: open connections at peak. A few hundred per subscriber is typical.
  • Subscribers: determine the port block size and how many public IPs you need.

CoreGate CGNAT tiers scale all three together: 10 million concurrent sessions and 16,000 subscribers per 10 Gbps. There are seven tiers, from CGN-10 to CGN-800; as your network grows you move up a tier with a licence upgrade instead of new hardware. When the hardware reaches capacity, you add a node to the cluster.

Summary

CGNAT is the most practical answer to IPv4 exhaustion available today. Port block allocation keeps logging manageable, the right NAT behaviours protect the subscriber experience, and your network keeps growing while you move to IPv6.