Our trusted partners
JCPenneyOasisPilotToyotaSoniqWaveGenesis Digital AssetsFAA
  1. Home
  2. /Enterprise
  3. /Managed IPv4 Infrastructure
  4. /How to Lease a /24

How to Lease a /24 IPv4 Block

A /24 IPv4 block contains 256 total IPv4 addresses. Businesses that need a dedicated /24 can obtain address space through a lease rather than purchasing it permanently, but the addresses still need routing, bandwidth and network infrastructure before they can be used.

By NetWest Online, Inc.Published August 2026

For many organizations, a /24 is the first meaningful dedicated IPv4 allocation.

What Is a /24 IPv4 Block?

A /24 is an IPv4 network containing:

256 total IPv4 addresses

CIDR notation uses the number following the slash to identify the network prefix length.

IPv4 addresses contain 32 bits.

A /24 leaves 8 bits for addressing:

2⁸ = 256

Learn more about IPv4 block sizes.

Why Would a Business Need a /24?

A /24 can support many types of legitimate business infrastructure, including:

  • Application servers
  • SaaS platforms
  • Network monitoring
  • Enterprise hosting
  • Cybersecurity research
  • Web-data infrastructure
  • Dedicated customer environments
  • Private cloud deployments
  • VPN infrastructure
  • IoT systems
  • Network testing
  • Disaster-recovery environments

The appropriate use depends on the technical design and provider acceptable-use requirements.

Can You Lease a /24 Instead of Buying It?

Yes.

Leasing allows a business to use a /24 without permanently purchasing the underlying address resource.

The business typically pays a recurring fee for the right to use the allocation.

Depending on the provider, the service may include only the IPv4 block or may also include:

  • Routing
  • BGP
  • Bandwidth
  • Reverse DNS
  • Colocation
  • Power
  • Monitoring
  • Network engineering

Learn more about IPv4 leasing.

Step 1: Define the Intended Use

Before requesting a /24, be prepared to explain how it will be used.

A responsible network provider may ask:

  • What application will use the addresses?
  • Are the addresses for internal company use?
  • Will third parties have access?
  • Will SMTP or email traffic be generated?
  • What type of servers will use the addresses?
  • What traffic volume is expected?

This review helps protect both the customer and the network operator.

Step 2: Determine Your Bandwidth Requirements

Having 256 IP addresses does not determine bandwidth usage.

One /24 deployment might consume:

50 Mbps

while another could require:

1 Gbps or more.

Provide both:

Average expected bandwidth

and

Peak bandwidth

Also provide estimated monthly data transfer when possible.

Bandwidth can significantly affect total infrastructure cost.

Step 3: Decide Where the Servers Will Operate

The addresses need to terminate somewhere.

Common options include:

Provider Colocation

Customer equipment is installed in the provider's facility.

Dedicated Servers

The provider supplies or hosts server hardware.

Customer Facility

The provider routes the addresses to customer infrastructure where technically feasible.

Managed Infrastructure

The addresses and servers remain within the provider's network environment.

Learn more about IPv4 colocation.

Step 4: Determine Who Will Route the /24

A /24 must be routed to be useful on the public Internet.

Possible designs include:

  • Provider originates the prefix
  • Customer originates the prefix
  • Provider routes addresses internally to customer equipment
  • Customer ASN integrates with provider BGP

For many managed deployments, keeping the prefix originated through the provider’s network can simplify the configuration.

Learn more about BGP.

Step 5: Determine Whether You Need an ASN

Most businesses leasing a /24 do not necessarily need their own ASN.

If the provider originates and routes the addresses, the provider can handle external BGP.

A customer ASN may become relevant when the business needs:

  • Independent routing
  • Multi-homing
  • Provider independence
  • Its own public prefix announcements
  • Advanced routing policies

Learn more about ASNs.

Step 6: Ask About Reverse DNS

Some deployments require custom PTR records.

Ask whether the provider offers:

  • PTR record changes
  • Reverse DNS management
  • Reverse DNS delegation

Learn more about reverse DNS.

If your application depends on rDNS, confirm this before deployment.

Step 7: Understand IP Reputation

The history and behavior associated with the IPv4 block matter.

Ask the provider about:

  • Current reputation
  • Abuse procedures
  • Blocklist monitoring
  • Prior use when known
  • Network acceptable-use policies

Learn more about IP reputation.

A low lease price is not necessarily a good value if the addresses have serious reputation problems.

How Much Does It Cost to Lease a /24?

Pricing varies.

Factors include:

  • Market conditions
  • Address history
  • Geography
  • Provider
  • Contract length
  • Routing
  • Bandwidth
  • Colocation
  • Power
  • Network engineering

An address-only /24 lease will generally be priced differently from a managed /24 deployment that includes bandwidth, routing and server infrastructure.

Learn more about IPv4 leasing cost.

Leasing a /24 From a Marketplace vs. a Network Operator

A marketplace may primarily help a business obtain address resources.

A network operator can potentially provide:

/24 address space

plus

routing

plus

bandwidth

plus

servers

plus

colocation

plus

technical support.

That can reduce the number of separate vendors required for the deployment.

Should You Start With a /24?

For specialized applications, a /24 can be a useful starting allocation.

It is large enough to support meaningful infrastructure but much smaller than a /22 or /21.

Starting with a smaller allocation can help both the customer and provider establish:

  • Technical performance
  • Traffic patterns
  • Abuse history
  • Utilization
  • Reputation
  • Operational compatibility

Expansion can then be evaluated as requirements grow.

What Information Should You Provide When Requesting a /24?

Include:

Company name

Company website

Intended use

Required allocation

Expected bandwidth

Server requirements

Colocation requirements

Power requirements

BGP requirements

ASN information

Reverse DNS requirements

Deployment timeline

The more specific the request, the easier it is for the network provider to design and quote the service.

Can NetWest Provide a /24?

NetWest can evaluate /24 and larger IPv4 requirements for qualified business applications, subject to availability and technical review.

A NetWest deployment can potentially combine:

  • Dedicated IPv4 resources
  • ISP network routing
  • Bandwidth
  • BGP engineering
  • Reverse DNS
  • Server colocation
  • Power
  • Remote hands
  • Network monitoring

Learn more about Managed IPv4 Infrastructure.

Frequently Asked Questions

Need a /24 IPv4 Block?

Tell NetWest what you’re building. We can evaluate the address requirement together with routing, bandwidth, servers and physical infrastructure.

Related IPv4 Resources

Request IPv4 Infrastructure Consultation

Tell us what you need. NetWest will review your IPv4, routing, bandwidth and infrastructure requirements and determine an appropriate deployment.

Contact Information

IPv4 Requirement

Deployment Type

Estimated Bandwidth

Equipment

Application / Intended Use

Qualification Questions

Deployment Timeline

Additional Requirements

Your request is handled as a confidential business inquiry.

NetWest Online

The Permian Basin's premier provider of Internet service and data solutions since 1996.

Contact Us

5000 E. University Blvd #11
Odessa, TX 79762
(432) 550-8766

Department Emails

General Questions
comments@netwest.com
Technical Support
support@netwest.com
Billing Support
Billing@netwest.com

Solutions

Tech Support

Knowledge Center

Legal

Service Areas

© 2026 NetWest Online, Inc. All rights reserved.

Serving the Permian Basin since 1996