How Many Public IP Addresses Does an ISP Need? A Practical Guide to Getting Them

Work out how many public IPv4 addresses your ISP needs, when NAT and CGNAT are enough, and how to get addresses in Kenya from an upstream provider or AFRINIC.

November 10, 2026 · 18 min read · Centipid operations

Title card on a sand background, with green line sketches of a router and a network of linked nodes.

How many public IP addresses does an ISP need? Do you need one for every subscriber, or can multiple customers share a few public IP addresses?

The answer depends on your network design, number of subscribers and services offered. Most small and growing ISPs can serve hundreds of customers using private IP addresses and NAT or CGNAT without assigning each subscriber a dedicated public IPv4 address.

However, ISPs must plan their IP address requirements carefully. IPv4 addresses are limited and obtaining additional address space can be costly or difficult, particularly for new operators.

This guide explains how to calculate your public IP requirements, use NAT and CGNAT, and obtain IPv4 addresses in Kenya.

So, What Is a Public IP Address?

A public IP address is an internet-routable address that allows a device or network to communicate with other networks across the internet. ISPs use public IP addresses to provide internet connectivity and host services that need to be accessible from outside their networks.

To understand how many public IP addresses your ISP needs, you should first understand the difference between public and private IP addresses.

Public IP vs Private IP Addresses

A public IP address can be routed across the internet. An upstream provider or an organisation with its own address resources assigns public IP addresses to internet-facing devices, routers and servers.

A private IP address operates within a local or private network. Devices using private addresses cannot communicate directly with public internet hosts without an intermediary such as NAT.

IPv4 defines three private address ranges:

Private IP range Address range
10.0.0.0/8 10.0.0.0 – 10.255.255.255
172.16.0.0/12 172.16.0.0 – 172.31.255.255
192.168.0.0/16 192.168.0.0 – 192.168.255.255

For example, an ISP can assign a subscriber the private IP address 10.10.1.25 while using NAT to allow that customer to access the internet through a public IP address.

This approach allows multiple subscribers to share public IPv4 addresses instead of requiring a separate address for every customer.

Static vs Dynamic Public IP Addresses

Public IP addresses can be either static or dynamic.

  • Static public IP: An address that remains assigned to a customer or network until the provider changes the allocation.
  • Dynamic public IP: An address assigned temporarily or from a provider's address pool. It may change when the customer reconnects or the lease expires.

Businesses hosting servers, VPN endpoints or other internet-facing services often need static public IP addresses. Ordinary home subscribers generally do not need them.

Remember that static and public describe different things. A private IP can be static, while a public IP can be dynamic.

IPv4 vs IPv6

ISPs mainly encounter two versions of IP addressing: IPv4 and IPv6.

  • IPv4 uses 32-bit addresses, providing approximately 4.3 billion possible addresses. Examples include 41.90.100.25 and 197.232.10.5.
  • IPv6 uses 128-bit addresses, providing a much larger address space. An example is 2001:db8:1234::1.

IPv4 addresses have become scarce because internet growth has exceeded the available supply. As a result, ISPs increasingly use NAT and CGNAT to share public IPv4 addresses among subscribers.

IPv6 provides enough address space to assign globally unique addresses to individual devices and networks without relying on IPv4-style address sharing. However, ISPs may still need IPv4 connectivity to reach services and networks that have not fully adopted IPv6.

Many operators therefore use dual-stack networking, which supports IPv4 and IPv6 simultaneously.

For a new ISP, planning for both protocols is important. IPv4 remains necessary for compatibility while IPv6 provides a long-term approach to address availability.

Does Every ISP Customer Need a Public IP Address?

No. Most ISP customers can access the internet using private IP addresses through Network Address Translation (NAT).

NAT allows multiple devices or subscribers to share one or more public IPv4 addresses. The ISP router translates their private addresses into public addresses when they access the internet.

For example, an ISP with 250 subscribers does not automatically need 250 public IPv4 addresses. It can assign private IP addresses to all 250 customers and route their internet traffic through a shared public IP address pool.

However, some customers need dedicated public IP addresses, particularly when they host services or require reliable inbound connections.

Which Customers May Need Dedicated Public IP Addresses?

Consider allocating dedicated public IP addresses to customers who:

  • Host servers: Businesses running web servers, email servers or other services that need direct internet access.
  • Use remote access: Organisations that require direct access to office networks, VPN endpoints or remote infrastructure.
  • Need IP allowlisting: Businesses whose systems only accept connections from approved public IP addresses.
  • Run network infrastructure: Customers managing firewalls, routers or other equipment that requires inbound internet connectivity.
  • Require a stable internet identity: Businesses that need a consistent public source IP for specific applications or third-party integrations.

Not every customer in these categories necessarily needs a dedicated IPv4 address. VPN services, reverse proxies and cloud-based access solutions can provide alternatives.

Can Hotspot and PPPoE Customers Share Public IP Addresses?

Yes. Both hotspot and PPPoE subscribers can use private IP addresses and share public IPv4 addresses through NAT.

For example, an ISP can assign private addresses to hotspot users through its DHCP server. It can also assign private addresses to PPPoE subscribers through its PPPoE server.

The ISP router then translates their traffic into public IP addresses before forwarding it to the upstream provider.

The access method does not determine whether a customer needs a public IP address. What matters is the customer's requirements and the ISP's network design.

How Many Public IP Addresses Does an ISP Actually Need?

There is no fixed number of public IP addresses that every ISP needs.

Your requirements depend on subscriber activity, NAT configuration, customer services and the capacity of your network equipment.

An ISP with 250 subscribers may operate with a small pool of public IPv4 addresses, while another ISP with the same subscriber count may need more because it offers dedicated public IPs to business customers.

Factors That Determine Your Public IP Requirements

Consider these factors when planning your IP address requirements:

  • Number of active subscribers: The total number of registered subscribers does not necessarily determine your public IP requirements. Focus on how many customers use the internet simultaneously, particularly during peak hours.
  • NAT and CGNAT configuration: NAT allows multiple private IP addresses to share public IP addresses. However, each public IP has a limited number of available ports for translating connections. Your NAT equipment must handle the expected number of simultaneous connections.
  • Customer requirements: Some business customers may need dedicated public IP addresses for hosting servers, VPN access and IP-based authentication. Include these requirements when calculating your address needs.
  • Number of simultaneous connections: A subscriber may open hundreds of simultaneous connections through applications, browsers, streaming services and other devices. Your NAT equipment must have enough ports and connection-tracking capacity to handle this traffic.
  • Network infrastructure: Your ISP may also need public IP addresses for internet-facing services and infrastructure. However, not every router, access point or network management device needs a public IP.
  • Future expansion: Consider expected subscriber growth when requesting or purchasing address space. Avoid acquiring a large block that you cannot justify or use efficiently.

Understanding IP Requirements for Different ISP Sizes

The following table shows how different ISP sizes might approach public IP planning.

ISP size Subscribers Suggested addressing approach
Small ISP 50–100 Upstream-assigned public IPs with NAT
Growing ISP 250–500 NAT or CGNAT with a planned public IP pool
Medium ISP 1,000–2,000 Properly sized CGNAT, IPv6 and dedicated customer allocations
Large ISP 5,000+ Scalable CGNAT, IPv6, independent address resources where justified and BGP where required

These are network planning categories, not fixed IP-to-subscriber ratios. Two ISPs with the same number of subscribers can have different public IP requirements depending on their connection patterns and services.

Practical Example: Calculating Public IP Requirements for a 250-Subscriber ISP

Suppose you operate an ISP with 250 subscribers.

Your network records show that approximately 150 subscribers are simultaneously active during peak hours. Out of these, five business customers require dedicated public IPv4 addresses.

For illustration, assume your CGNAT equipment has been tested and can safely support the measured connection and port demand of 100 peak-active subscribers per public IPv4 address.

Your calculation would look like this:

Requirement Public IP addresses
Five business customers requiring dedicated IPs 5
Shared CGNAT pool for 150 peak-active subscribers 2
Public-facing ISP infrastructure service 1
Total 8

The calculation for the shared pool is:

150 active subscribers ÷ 100 subscribers per public IP = 1.5

Round this up to two public IP addresses.

Therefore, this ISP would require eight public IPv4 addresses under the stated assumptions.

The figure of 100 subscribers per public IP is an illustrative assumption, not a universal industry standard. Your actual CGNAT capacity depends on port allocation, connection patterns, equipment performance and configuration.

Before deciding how many public IP addresses to acquire, monitor your peak NAT sessions, port utilisation and subscriber activity. Use these measurements to establish the capacity of each public IP address.

How Much IPv4 Address Space Do You Need?

IPv4 addresses are allocated in blocks using Classless Inter-Domain Routing (CIDR) notation.

You will encounter prefixes such as /29, /28, /27 and /24 when requesting public IP addresses from upstream providers or obtaining address resources.

The prefix determines the size of the address block. A smaller prefix number represents a larger block.

Here is a reference table:

CIDR prefix Total IPv4 addresses Usable host addresses
/32 1 1
/30 4 2
/29 8 6
/28 16 14
/27 32 30
/26 64 62
/25 128 126
/24 256 254
/23 512 510
/22 1,024 1,022

Usable host counts follow conventional IPv4 subnetting, where the network and broadcast addresses are excluded. A /31 is a special case that supports two addresses on point-to-point links.

For example:

  • A /29 gives you eight addresses, with six conventionally usable host addresses.
  • A /28 gives you 16 addresses, with 14 conventionally usable host addresses.
  • A /24 gives you 256 addresses, with 254 conventionally usable host addresses.

When requesting an IP block, clarify whether the quoted size refers to the total addresses or the usable addresses available to you.

Also, do not confuse the size of an IP block with how many subscribers it can serve. A /29 does not mean you can serve only six customers. With NAT, you can serve many more subscribers using a much smaller public IP pool.

Your goal should be to acquire enough public IP addresses to meet your actual network requirements without paying for unnecessary address space.

NAT vs CGNAT: How ISPs Share Public IP Addresses

Network Address Translation (NAT) allows multiple devices using private IP addresses to access the internet through one or more public IP addresses.

For ISPs, NAT helps conserve IPv4 addresses. Instead of assigning every subscriber a public IP, you can assign private addresses and translate their traffic through your network gateway.

Carrier-Grade NAT (CGNAT) takes this approach further by allowing multiple subscribers to share a pool of public IPv4 addresses at the ISP level.

Feature NAT CGNAT
Deployment Usually at a customer router or network gateway Within the ISP network
Private addresses Translates private addresses to public addresses Translates subscriber addresses to a shared public pool
Main purpose Allow multiple devices to share an internet connection Allow many subscribers to share limited IPv4 resources
Typical use Homes, offices and small networks ISPs with large subscriber bases

Why Do ISPs Use CGNAT?

CGNAT helps ISPs serve more customers without acquiring a dedicated public IPv4 address for every subscriber. It can reduce address acquisition costs and extend the available IPv4 pool.

However, sharing public IP addresses also introduces challenges.

  • Port exhaustion: Each public IPv4 address has a limited port space. Heavy connection usage can exhaust the ports available to subscribers, preventing new connections.
  • Inbound connectivity: Customers behind CGNAT generally cannot accept unsolicited inbound connections directly. This can affect remote access, self-hosted servers and some VPN applications.
  • Shared IP reputation: When several subscribers share one public IP address, one customer's activity can affect the reputation of that address. For example, websites may block it because of suspicious activity by another subscriber.
  • Logging and troubleshooting: ISPs must maintain reliable NAT records to identify which subscriber used a particular public IP address and port at a given time. Accurate timestamps and connection details are important when investigating abuse or network problems.

CGNAT is useful for conserving IPv4 addresses, but it requires proper planning, capable equipment and monitoring. ISPs should also consider IPv6 deployment as part of their long-term addressing strategy.

How Can an ISP Get Public IP Addresses in Kenya?

ISPs in Kenya have three main options for obtaining public IPv4 addresses:

  • Getting them from an upstream provider.
  • Applying through AFRINIC.
  • Acquiring address space through an approved transfer.

Get Public IP Addresses from Your Upstream Provider

For a small or growing ISP, requesting public IP addresses from your upstream internet provider is often the simplest option.

When purchasing bandwidth, ask your provider whether they can supply:

  • A dedicated static public IPv4 address.
  • A routed public IP subnet such as a /29 or /28.
  • A larger address block if your network requirements justify it.

Before accepting the allocation, clarify whether the addresses are shared or dedicated, whether the block is static and whether you can retain it when changing upstream providers.

Also ask about the monthly charges, routing arrangements and reverse DNS support.

This option allows you to operate without applying for your own IPv4 allocation from AFRINIC.

Apply for IPv4 Resources Through AFRINIC

The African Network Information Centre (AFRINIC) manages internet number resources for the African region. ISPs that need their own address resources can apply for membership and IPv4 allocation.

Note that AFRINIC does not automatically allocate addresses to every ISP that applies. Applicants must demonstrate a genuine need and meet its resource allocation policies.

AFRINIC's currently published initial IPv4 allocation criteria include:

  • Be an AFRINIC member in good standing or be applying for membership.
  • Have a plan to use at least a /23 within the next eight months.
  • Demonstrate that your network infrastructure exists in Africa.
  • Hold a valid service licence in the country of operation where one is required.

An ISP should therefore prepare its network plan, subscriber projections, addressing requirements and relevant company documentation before applying.

The application process starts through the AFRINIC New Membership Registration Portal (NMRP). AFRINIC evaluates the application before approving membership and any requested resources.

You can review the current requirements on the official AFRINIC website.

Obtain IPv4 Address Space Through an Approved Transfer

Another option is to obtain IPv4 address space from an organisation that holds resources it no longer needs.

AFRINIC permits IPv4 transfers within its service region under its transfer policy. Remember, these transactions require AFRINIC approval.

The receiving organisation must demonstrate its need for the addresses, meet the applicable membership requirements and complete the required transfer documentation.

Do not simply purchase an IP block from a broker and assume that ownership has transferred. Verify that the current holder has legitimate rights to the addresses and that AFRINIC can process and register the transfer.

You should also consider membership fees, transfer charges and ongoing resource management obligations.

For many new ISPs, obtaining addresses from an upstream provider is the more practical starting point. Applying for independent address resources or pursuing a transfer makes more sense when the ISP has sufficient infrastructure and a documented need.

Do You Need an ASN and BGP to Use Public IP Addresses?

No. You can use public IP addresses assigned by your upstream provider without having your own Autonomous System Number (ASN) or BGP setup.

An ASN uniquely identifies an autonomous network on the internet. BGP (Border Gateway Protocol) allows different autonomous networks to exchange routing information.

You may need your own ASN and BGP when:

  • Connecting to multiple upstream providers (multihoming).
  • Announcing your own public IP prefixes.
  • Managing your own internet traffic routing.
  • Establishing direct peering with other networks or Internet Exchange Points (IXPs).

For a small ISP using a single upstream provider's IP addresses, neither is usually necessary.

Get an ASN when your network needs independent routing, not simply because you want public IP addresses.

IPv6: The Long-Term Solution to IPv4 Scarcity

IPv6 provides a long-term solution to IPv4 address scarcity. It uses 128-bit addresses, compared to IPv4's 32-bit format, providing an enormous pool of globally unique addresses.

For ISPs, IPv6 makes it possible to assign individual subscribers and their devices globally unique addresses without relying on IPv4-style NAT.

However, IPv4 remains necessary for accessing services and networks that have not fully adopted IPv6.

ISPs can support both protocols through dual-stack networking, which allows customers to access IPv4 and IPv6 services simultaneously.

When planning your network, consider:

  • Choosing upstream providers that support IPv6.
  • Using routers and network equipment with IPv6 support.
  • Planning IPv6 address allocation for subscribers.
  • Deploying dual-stack connectivity during the transition.

IPv6 adoption helps reduce dependence on scarce IPv4 addresses. It should therefore form part of your long-term network plan.

For more guidance on choosing upstream providers, bandwidth and planning network connectivity, see our detailed Upstream & Backhaul course on Centipid Academy.

Common Public IP Address Planning Mistakes ISPs Should Avoid

Poor IP address planning can increase operating costs and create network problems as your ISP grows.

Avoid these common mistakes:

  • Assigning every subscriber a public IP: Most customers can access the internet through private IP addresses and NAT. Reserve dedicated public IPs for customers who need them.
  • Buying more IP addresses than necessary: Assess your current subscriber demand and future growth before acquiring address space.
  • Ignoring CGNAT capacity: Consider port availability, simultaneous connections and equipment performance when sizing your public IP pool.
  • Failing to keep NAT logs: Maintain accurate connection records to help identify subscribers when investigating abuse or technical incidents.
  • Ignoring IPv6: Include IPv6 in your network expansion plans instead of depending entirely on scarce IPv4 addresses.
  • Confusing an ASN with an IP allocation: An ASN identifies your autonomous network. It does not automatically give you public IP addresses.
  • Failing to plan for business customers: Some customers need dedicated public IPs for VPNs, servers and other services. Account for these requirements when planning your address pool.

Key Takeaways for ISP Operators

An ISP does not need one public IPv4 address for every subscriber. With proper NAT or CGNAT configuration, multiple customers can share a pool of public IP addresses.

Before acquiring address space, assess your subscriber requirements, peak connections, customer needs and network capacity. You can start with addresses from your upstream provider and consider independent IP resources, an ASN and BGP as your network grows.

Also, include IPv6 in your long-term network strategy to reduce dependence on scarce IPv4 addresses.

Frequently Asked Questions

1. How many public IP addresses does a small ISP need?

There is no fixed number. A small ISP can serve many subscribers using private IP addresses and NAT. The actual public IP requirement depends on peak connections, NAT capacity and customers who need dedicated addresses.

2. Does every ISP customer need a public IP address?

No. Most customers can access the internet through private IP addresses using NAT or CGNAT. Dedicated public IPs are mainly necessary for customers requiring specific inbound connectivity or a stable public identity.

3. Can multiple ISP customers share one public IP address?

Yes. NAT and CGNAT allow multiple subscribers to share public IPv4 addresses. However, the ISP must manage available ports and simultaneous connections to avoid exhaustion.

4. What is the difference between a static IP and a public IP?

A public IP address is routable across the internet. A static IP remains unchanged until the provider changes it. A public IP can be either static or dynamic.

5. How much does a public IPv4 address cost in Kenya?

There is no single fixed price. Costs depend on the upstream provider, address block size, allocation arrangement and applicable resource fees. Request quotations from several providers before committing.

6. How can an ISP get public IP addresses in Kenya?

An ISP can request public IP addresses from an upstream provider, apply for resources through AFRINIC or obtain address space through an approved transfer.

7. Can an ISP operate without its own public IP block?

Yes. An ISP can obtain public IP addresses from its upstream provider and use NAT to serve subscribers. It does not need to own an independent IPv4 allocation to provide internet services.

8. Does an ISP need an ASN to get public IP addresses?

No. An ISP can use addresses supplied by an upstream provider without its own ASN. An ASN becomes useful when the ISP needs independent routing and multihoming.

9. What is the difference between NAT and CGNAT?

NAT commonly translates private addresses at a customer or network gateway. CGNAT performs address translation within the ISP network, allowing many subscribers to share a pool of public IPv4 addresses.

10. Can CGNAT affect online gaming and VPN connections?

Yes. CGNAT can affect applications that require inbound connections, certain VPN configurations and some online games. The impact depends on the application and its connection requirements.

11. Can an ISP use IPv6 instead of IPv4?

Yes, where upstream connectivity and customer equipment support IPv6. However, many internet services still require IPv4 connectivity, so ISPs commonly deploy dual-stack networks.

12. How many subscribers can share one public IPv4 address?

There is no universal subscriber-to-IP ratio. The number depends on simultaneous connections, port allocation, application usage and CGNAT equipment capacity. ISPs should use network measurements rather than arbitrary ratios.

See it on your own network