ISP and WISP operator tools
IP pool and CGNAT sizing calculator
Plan a PPPoE or hotspot address pool against subscriber growth and peak concurrency.
No signup. Calculations stay in this tab: no submissions, network calls or saved inputs. Works offline after loading while the tab stays open.
Your planning assumptions
Whole subscriber counts: 0–100,000,000. Horizon: 0–1,200 whole months. Concurrency: 0–100%, up to two decimal places. Growth is a fixed number of additions, not a percentage.
Pool estimate
Estimate updated.
- Subscribers at the horizon
- 440
- Addresses needed at peak
- 352
- Recommended pool
- 10.0.0.0/23
- Usable addresses in this model
- 510
- First month beyond this pool’s capacity
- 22 months from today
Planning guidance, not a guarantee. Measure real address use, simultaneous sessions and port demand before sizing a production pool.
How to read the estimate
Projected subscribers = subscribers today + new subscribers per month × months ahead. Peak demand = projected subscribers × concurrency, rounded up. One address per concurrent subscriber; no spare-capacity margin is added.
The smallest block from /30 upward is selected. Usable capacity = 2^(32 − prefix) − 2: the first and last addresses of the aggregate block are excluded. A /24 has 254 usable addresses; 255 requires a /23. This is a planning convention, not a requirement for every PPP pool.
Private examples stay inside 10.0.0.0/8; CGNAT subscriber-side examples stay inside 100.64.0.0/10. The CGNAT block is shared address space, not the public NAT egress pool.
Months to exhaustion is the first whole month from today when projected peak demand exceeds the recommended block above, assuming unchanged growth and concurrency. It is not a measurement of your current router pool. Exactly filling the pool still fits; the next address does not.
The RouterOS line only defines an example address range. Review overlap, routing and reservations before use. Keep router/local PPP addresses outside that range; subtract additional gateway, static and held-lease reservations for DHCP or hotspot use. It does not configure PPP profiles, DHCP, NAT, firewall rules or logging.
CGNAT assumption: 1 public IP for 64 concurrent subscribers
Assume ports 1024–65535 inclusive: 64,512 ports per public IPv4 address per protocol. Dividing by 64 gives 1,008 ports per subscriber for TCP and separately for UDP. Public addresses = peak concurrent subscribers ÷ 64, rounded up. This illustrative fixed allocation is not a RouterOS default or a recommended sharing ratio. Real allocation policy, reserved ports, applications, session limits, logging and redundancy change capacity. No NAT rule is generated.
Technical references: RFC 1918 · RFC 6598 · RouterOS IP Pools
Review your access workflow
ISPAgents MikroTik and access workflows are guided pilots with onboarding and validation. This calculator does not inspect a router or configure pools automatically.