Peer1IX
Internet Exchange
Services

Interconnection

Internet ExchangeMicro PoPsEdge Data Centers

Network Services

Data Center to Data CenterVirtual Connectivity HubData Center to CloudCloud to CloudPeer1ix Cloud RouterPeer1ix Virtual EdgeNAT GatewayPeer1ix PortVirtual Cross Connect

Security Services

DDoS ProtectionPeer1ix FWaaSIPsec Tunnel

Cloud Interconnect

Cloudflare Network Interconnect
Locations
Network toolsAll-in-One Network ReportBGP Looking GlassRPKI ValidatorBGP Security & Hijack CheckIP WHOISAS WHOISBGP Route ExplorerASN InsightsBGP Hijacks & Route LeaksInternet Outage TrackerCountry Internet InsightsTop Domains RankingDNS LookupSubnet CalculatorWhat Is My IP
BlogAboutContact Get connected

Sizing a NAT Gateway: Sessions, Ports and Throughput

· 1 min read · Peer1IX Team

Sizing a NAT Gateway: Sessions, Ports and Throughput

NAT capacity is not just bandwidth. Sessions, ports per subscriber and address pools all need planning.

Four dimensions

Sizing NAT requires looking at throughput, sessions, ports and addresses together.

Throughput

Measure peak traffic that will pass through NAT, excluding traffic that will use IPv6 or stay on-net.

Concurrent sessions

Each subscriber may have hundreds of active connections — streaming, messaging, background updates. Multiply by peak concurrent subscribers to estimate total sessions.

Ports per subscriber

Each public IPv4 address has around 64,000 usable ports. Allocating, for example, 1,000–2,000 ports per subscriber gives a sharing ratio in the dozens. Too few ports cause failures for heavy users; too many waste addresses.

Address pool

Divide subscribers by your chosen sharing ratio to estimate how many public addresses you need.

Headroom

Leave margin for growth and for events — big matches or releases can spike usage.

Peer1IX NAT Gateway scales these dimensions as a managed service. Request a sizing review.

capacity planningNAT sizingsessions