Why /23 and /22 IPv4 Blocks Matter for Growing Networks

Growing networks often outgrow a single /24 before they are ready for a large allocation. /23 and /22 IPv4 blocks help teams add capacity, reduce routing complexity, and plan address use with fewer urgent migrations.

A /23 or /22 IPv4 block is an ip address range that groups 512 or 1,024 IPv4 addresses under one routed prefix. It supports b2b network scaling by giving companies more address capacity for hosting, VPN, SaaS, telecom, CDN, security, and cloud infrastructure.

What is the 22 vs 23 subnet difference?

The 22 vs 23 subnet choice is mainly about size and growth horizon. A /23 contains 512 addresses. A slash 22 contains 1,024 addresses. Both are larger than a /24, which has 256 addresses and is often treated as the practical minimum for global BGP routing.

A /23 can be enough when a company needs moderate growth. It can support two /24 segments, customer pools, NAT pools, dedicated IP services, or separate zones for production and staging. A /22 gives more room for expansion and can reduce the need to request new prefixes soon after deployment.

Why does block size matter for infrastructure planning?

Block size affects routing, IPAM, customer onboarding, DNS, monitoring, and firewall design. A growing network needs enough addresses, but it also needs a structure that engineers can operate without manual errors.

Larger blocks help with infrastructure planning because they allow cleaner segmentation:

• one segment for production services;
• one segment for customer-facing workloads;
• one segment for VPN or remote access;
• one segment for testing, staging, or migration;
• spare space for failover and regional growth.

A weak plan can create fragmentation. Teams may lease several unrelated /24 blocks and then manage separate LOA, ROA, IRR, rDNS, geolocation, and abuse workflows for each prefix. A /23 or /22 can reduce that work when the workload is stable.

When should a company rent a /23 IPv4 block?

A team should rent a /23 IPv4 block when the need is real but ownership is not yet required. Leasing can support a migration, new region, product launch, temporary customer growth, or a controlled test before purchase.

A /23 is useful when:

1. a /24 is already close to full use;
2. the team needs two routable /24 segments;
3. the workload may grow for 6–18 months;
4. the business wants lower commitment than purchase;
5. the network team needs time to validate demand.

For slash 23 routing, check whether the prefix will be announced as one /23 or split into two /24s. Some upstreams and peers accept both models, but route policy must be confirmed before deployment. The contract should define the origin ASN, LOA validity, ROA records, route objects, and termination procedure.

When should a company buy a /22 block?

A company should consider buying a /22 block when IPv4 demand is long term and tied to core infrastructure. Ownership can make sense when the same address space will support customers, compliance zones, VPN gateways, hosting nodes, or telecom services for years.

A /22 can fit corporate sizing when the business needs:

• predictable ip allocation for several teams or products;
• one larger range instead of many unrelated prefixes;
• stable reputation for mail, API, CDN, or partner access;
• direct RIR transfer and registry control;
• lower operational churn after growth.

The purchase decision should include due diligence. Check the seller, RIR status, transfer eligibility, abuse history, geolocation, blacklist data, and route authorization. A clean block is easier to integrate than a cheaper block with hidden reputation problems.

What risks should be checked before scaling?

Growth creates technical and contract risk. More addresses mean more assets to secure, document, and monitor. The team must know who can use each subnet, which systems announce it, and how abuse reports are handled.

Check these points before choosing a /23 or /22:

• real utilization and forecasted demand;
• BGP policy, max-prefix limits, and route filters;
• ROA, IRR, WHOIS/RDAP, LOA, and rDNS readiness;
• IPAM ownership, naming rules, and change control;
• customer allowlists and firewall dependencies;
• abuse desk process and suspension triggers.

How can teams choose the right capacity?

Use a simple rule. Choose /23 when a /24 is too small but growth is still being tested. Choose /22 when the network needs stable capacity for several segments and the business wants fewer future migrations.

The right choice depends on utilization, route policy, contract term, region, budget, and operational risk. Address space should match the workload, not only the forecast. Overbuying wastes budget. Under-sizing causes emergency changes.

FAQ: What do teams ask about /23 and /22 blocks?

Is /23 enough for a growing company?
Yes, if the company needs two /24-sized segments and growth is moderate. It may be too small for multi-region or high-volume hosting.

Can a /22 be announced as smaller blocks?
Often yes, but the team must check upstream filters, ROA design, and route policy before splitting announcements.

Is leasing better than buying for scaling?
Leasing fits testing or flexible growth. Buying fits long-term infrastructure where registry control and stable use are important.

What is the main risk in larger IPv4 allocation?
The main risk is poor governance. Without IPAM, abuse control, and routing documentation, a larger range can create operational errors.

How can InterLIR Global support IPv4 scaling decisions?

If your team needs to compare /23 leasing, /22 purchase, routing documents, reputation checks, or capacity planning, contact InterLIR. The company provides infrastructure for IPv4 leasing, buying, lease-out, and marketplace workflows, so growing networks can match address supply with technical and contractual requirements.

Evgeny Sevastyanov

Support Team Leader