IPv4 Subnet Calculator: How to Choose the Right Block Size for Your Project

Choosing the wrong subnet size is one of the most expensive mistakes you can make when leasing IPv4 space - either you overpay for addresses you'll never use, or you scale out of your allocation six months in and start the whole process over. This guide gives you the reference tables, decision logic, and an interactive IPv4 subnet calculator to get it right the first time.

IPv4 Subnetting Basics (CIDR, Prefix Length)

Before reaching for any IPv4 CIDR calculator, it helps to have a firm grip on what you're actually sizing.

CIDR (Classless Inter-Domain Routing) replaced the old class-based system in 1993 and remains the universal notation for IPv4 addressing today. A CIDR block is written as an IP address followed by a slash and a prefix length - for example, 192.168.1.0/24. The prefix length tells you how many bits are reserved for the network portion; the remaining bits define the host space.

Prefix length and usable hosts:

The total number of addresses in a block is always 2^(32 - prefix length). However, two addresses are always reserved in every subnet - the network address and the broadcast address - so the number of usable hosts is 2^(32 - prefix length) - 2. In practice, for larger blocks used in leasing and routing contexts (anything /24 and above), this two-address overhead is operationally negligible, so most operators refer to the total address count when discussing IPv4 block size.

Why does prefix length matter for leasing?

In the RIPE NCC service region (and other RIRs), the minimum routable block size is a /24 - 256 addresses. Anything smaller is typically filtered by BGP peers and won't propagate across the internet. This is the floor you need to plan around. If your project requires fewer than 256 IPs, you still lease a /24 and simply don't use all of it - that's the economic reality of the current IPv4 market.

For a deeper dive into BYOIP and how leased addresses integrate with cloud infrastructure, see our guide on using BYOIP with leased IPv4 on AWS, GCP, and Azure.

Block Size Reference Table (/24 to /16)

Use this subnet size chart as your first reference point. It covers the range most commonly leased in the RIPE region, from a single /24 up to a /16 supernet.

Quick answer to a common question: how many IPs in /24? A /24 contains 256 total addresses and 254 usable host addresses. It's the single most common unit of IPv4 trading and leasing in the RIPE region.

For anything outside this range, our IPv4 pricing calculator can give you real-time cost estimates across block sizes.

How to Choose Block Size by Use Case

No single block size fits every project. Here's how to think through the decision based on what you're actually building.

Hosting: Web Hosting vs. Dedicated Servers

Shared/web hosting operations typically start with one or two /24s and expand incrementally. The rationale is simple: IP reputation is managed per /24 in most blacklisting systems, so keeping your customer segments isolated in separate /24s makes abuse handling and delisting significantly cleaner. A single /24 gives you enough address space to host hundreds of domains while keeping operational overhead low.

Dedicated server providers operate on a different model. Server-to-IP ratios vary, but a provider running 50-100 dedicated servers with multiple IPs per server will quickly outgrow a /24. A /22 (1,024 IPs) or /21 (2,048 IPs) is a more realistic starting point, giving room for customer allocations, management addresses, IPMI interfaces, and future growth without requiring a re-announcement event.

One factor that often gets overlooked: if you plan to lease IPv4 addresses rather than buy, you can scale your block size as your customer base grows - you're not locked into a fixed allocation. This makes leasing particularly attractive for hosting companies in growth phases.

VPN/Proxy: IP Rotation Pools

Proxy and VPN operations have a fundamentally different relationship with IPv4 block size than hosting does. Here, address diversity is the product itself. The larger your pool, the better your rotation coverage, and the longer it takes for downstream platforms to flag your ranges.

For residential-style proxy pools, operators typically look for:

• /23 to /22 for pilot deployments and niche geo-targeting

• /21 to /20 for production-scale rotation serving multiple clients

• /19 and above for commercial proxy networks with high-frequency rotation requirements

IP reputation history matters here more than in almost any other use case. Before committing to a block, verify its abuse history using tools like Spamhaus, IPVoid, or MXToolbox. IPbnb surfaces reputation data for all listed prefixes so you can assess this before signing a lease agreement.

One more consideration for proxy operators: prefix diversity across /24 subnets. Even if you lease a /22, some platforms score subnets at the /24 level. Check whether your provider can offer allocations spread across non-contiguous /24s if that matters for your detection avoidance strategy.

Enterprise: Multi-Site Networks

Enterprise deployments introduce routing complexity that single-use cases don't face. If you're interconnecting multiple office locations, data centers, and cloud VPCs, your IPv4 block size decision intersects with your internal addressing scheme, VPN topology, and summarization strategy.

Practical guidelines for enterprise planning:

• Reserve at least one /24 per physical site for future expansion, even if current headcount doesn't require it

• Use /22 or /21 aggregates when you need to summarize multiple sites into a single BGP announcement - it reduces routing table bloat and simplifies peering agreements

• Account for management, DMZ, and transit networks separately from your user/server address space - these consume more IPs than most network teams initially budget for
  
  

Clean IPv4, ready to deploy

Lease Clean IPv4 Fast With Zero Platform Fees

Start leasing

Cost per IP by Block Size (Lease Pricing)

IPv4 address lease pricing in the RIPE region doesn't scale linearly with block size - larger blocks typically carry a lower per-IP monthly rate, which creates meaningful savings at scale.

Below is a representative pricing structure to illustrate the relationship between IPv4 block size and cost efficiency (actual rates vary by block availability, lease term, and reputation):

Prices are illustrative. For current rates, use the IPv4 pricing calculator or browse available listings on the IPv4 lease marketplace.

The cost efficiency curve flattens significantly above /20. Unless your operational requirements genuinely need the address volume, leasing a /19 or larger for the marginal per-IP savings rarely justifies the commitment. The sweet spot for most growing operations is in the /22 to /21 range - enough addresses to operate professionally, with a per-IP rate meaningfully below /24-level pricing.

Also worth noting: lease term length can affect pricing more than block size at certain tiers. A 12-month commitment on a /24 may cost less per IP than a month-to-month /22. Run both scenarios through the pricing calculator before deciding.

Common Mistakes When Choosing Subnet Size

Even experienced network engineers make avoidable errors when sizing IPv4 blocks. Here are the patterns that come up most often.

1. Sizing for today, not for 18 months out

The most common mistake. A /24 feels right when you have 50 servers, but if you're growing 20% month-over-month, you'll be scrambling for additional space within a year. Add a realistic growth buffer - if you need 200 IPs today, lease a /23, not a /24.

2. Ignoring BGP routability minimums

Sub-/24 blocks simply don't route across most of the internet. If someone sells or leases you a /25 with promises that it's usable for internet-facing services, walk away. The minimum routable block in the RIPE region is /24, full stop.

3. Overlooking prefix reputation before leasing

A /22 with a clean reputation is worth significantly more than a /22 that's been on Spamhaus's SBL for two years. Always check abuse history before signing. This is especially critical for proxy, email, and hosting operators where IP reputation directly affects service quality.

4. Conflating address count with routing flexibility

A /22 is typically announced as a single aggregate prefix, but that doesn't mean it's rigid. Operators can also announce the constituent /24s as more-specific routes alongside the aggregate - for example, to steer traffic across different upstreams or for redundancy. However, not all upstream providers will accept deaggregated routes from within a leased block, and some contractually prohibit it. If split-routing or multi-homing flexibility matters to your architecture, verify what announcement configurations your provider allows before signing. Discuss your routing requirements explicitly rather than assuming the block can be sliced however you need.

5. Not accounting for RIPE's 24-month hold period on transferred space

If you're considering purchasing rather than leasing, addresses transferred under RIPE policy are subject to a 24-month hold period during which they cannot be transferred again. Leasing avoids this constraint entirely, which is one reason many operators prefer it for short-to-medium-term projects.

6. Choosing a /24 when operational overhead arguments point to a larger block

The per-IP savings at /23 vs. /24 are modest, but the operational overhead of managing two separate /24 leases (separate agreements, separate announcements, separate reputation tracking) often outweighs those savings. When in doubt, consolidate.

IPv4 Pricing Calculator

See exactly what you pay. No hidden fees or markup.

Open calculator

FAQ

What is an IPv4 subnet calculator and how does it work?

An IPv4 subnet calculator takes a CIDR notation input (like /24 or /22) and returns the total address count, usable host range, subnet mask, broadcast address, and network address. More advanced tools like IPbnb's calculator also return estimated lease pricing for RIPE-region blocks.

How many IPs are in a /24 subnet?

A /24 contains 256 total IP addresses: one network address, one broadcast address, and 254 usable host addresses. It's the minimum routable block size in the RIPE NCC service region.

What's the difference between a /24 and a /22?

A /24 has 256 addresses. A /22 aggregates four /24s, giving you 1,024 total addresses. A /22 can be announced as a single aggregate BGP prefix, which reduces your routing table footprint and typically comes at a lower per-IP lease cost than four separate /24s. It can also be deaggregated into /24 announcements for traffic engineering purposes, though your upstream provider's policy will determine what's permitted.

Can I lease less than a /24?

You can receive sub-/24 allocations internally (for LAN segmentation, for example), but you cannot announce anything smaller than a /24 to the internet. If you only need 30 external IPs, you still need to lease a full /24.

How do I choose between leasing and buying IPv4 addresses?

Leasing offers flexibility, lower upfront cost, and avoids the RIPE 24-month transfer hold. Buying makes more sense for long-term, stable deployments where you want full control over the resource. For most project-based or growth-stage operations, leasing is the more cost-effective path.

What does "clean IP reputation" mean for a subnet?

A clean subnet has no significant listings on major IP-based blocklists (Spamhaus SBL, SORBS, Barracuda BRBL, etc.) and no history of spam, abuse, or fraudulent activity. This matters most for email sending, proxy operations, and ad verification work where IP trust directly affects deliverability or platform access. Note that tools like SURBL track domain and URI reputation rather than IP reputation, so for subnet due diligence you want to focus specifically on IP-based DNSBL lookup tools such as Spamhaus, MXToolbox, or IPVoid.

How do I read a subnet size chart?

A subnet size chart maps CIDR prefix lengths to total IP counts, usable IP counts, and equivalent /24 block counts. The reference table in this article covers /24 through /16 with corresponding use cases. Start with your required IP count, find the smallest block that covers it, and add a growth buffer of at least 30%.

Need help sizing your block? Explore available prefixes and compare lease rates directly on the IPbnb marketplace, or use our IPv4 pricing calculator to model costs across different block sizes before committing.