How to Lease IPv4 Addresses in 8 Steps

Leasing IPv4 addresses gives businesses access to public IPv4 address space for a defined period without requiring a permanent IPv4 acquisition.

Organizations commonly lease IPv4 for hosting, cloud infrastructure, ISP networks, SaaS platforms, data centers, APIs, enterprise systems and other Internet-facing workloads.

But learning how to lease IPv4 addresses safely involves more than finding an available block and paying a monthly fee.

Before deploying leased IPv4 into production, a business should understand:

• how many IPv4 addresses it needs;
• which block size is appropriate;
• who controls the underlying resource;
• whether the addresses are dedicated;
• how BGP routing will work;
• whether an LOA is required;
• who manages RPKI and the ROA;
• whether reverse DNS is available;
• what reputation the addresses have;
• how geolocation and abuse reports are handled; and
• what happens when the lease renews or ends.

This article focuses specifically on the step-by-step process of leasing and deploying IPv4.

For a broader guide covering pricing, provider selection, leasing models, lease-vs-buy considerations and long-term continuity, read our complete guide to leasing IP addresses .

How to Lease IPv4 Addresses: Key Takeaways

• Start with the workload, not simply the number of addresses you think you need.
• Determine the correct IPv4 block size and allow for reasonable growth.
• Understand whether the lease is shared, dedicated, brokered or first-party.
• Check the IPv4 block before production deployment.
• Review lease duration, termination, renewal and permitted-use terms carefully.
• Confirm BGP, ASN, LOA and RPKI requirements before announcing the prefix.
• Establish reverse DNS, geolocation and abuse-handling responsibilities.
• Test routing and operational services before migrating production traffic.
• Monitor the prefix throughout the lease.
• Discuss renewal well before expiration if customers or systems depend on the addresses.

What Does It Mean to Lease IPv4 Addresses?

To lease IPv4 addresses means obtaining contractual use of IPv4 address space for an agreed period without permanently acquiring the underlying resource.

The customer uses the addresses according to the lease agreement while the underlying resource relationship remains with the provider or resource holder.

Businesses commonly lease public IPv4 for:

• dedicated servers;
• cloud workloads;
• hosting;
• SaaS infrastructure;
• data centers;
• ISP subscriber networks;
• public APIs;
• enterprise gateways;
• AI and GPU cloud infrastructure; and
• network services.

Different IPv4 leases can have different commercial and operational structures.

For a comparison of shared, dedicated, brokered and first-party models, see Types of IP Leasing Models .

For broader commercial information about lease IP addresses, including pricing, provider selection and continuity, see the Lease IP Addresses guide .

Step 1: Define Why You Need the IP Addresses

Start with the workload.

Before contacting a provider, determine exactly what the IPv4 addresses will support.

• What will the addresses be used for?
• Is the workload production or development?
• Is the requirement temporary or long term?
• Will customers depend on specific IP addresses?
• Will the prefix be announced from your own ASN?
• Does the workload require reverse DNS?
• Does geolocation matter?
• Will the addresses be used for email?
• Are third-party allowlists involved?
• How difficult would renumbering be later?

A temporary test environment and a production API platform do not necessarily require the same leasing structure.

A short-lived development workload may tolerate easy renumbering. A customer-facing platform may eventually have the same IPv4 addresses embedded in:

• DNS;
• APIs;
• customer allowlists;
• partner systems;
• security policies;
• firewalls; and
• monitoring.

The more systems that will depend on the prefix, the more important provider structure, renewal terms and continuity become.

Step 2: Determine How Many IPv4 Addresses You Need

IPv4 resources are commonly expressed using CIDR notation.

IPv4 Block	Number of Addresses
/24	256
/23	512
/22	1,024
/21	2,048
/20	4,096
/19	8,192
/18	16,384
/17	32,768
/16	65,536

Do not size an IPv4 lease only for today's exact consumption.

Consider:

• current utilization;
• expected customer growth;
• reserved capacity;
• infrastructure segmentation;
• future locations;
• service expansion; and
• expected growth during the lease term.

For example, if a network is already close to consuming 200 addresses, leasing exactly one /24 may leave limited room for growth.

At the same time, unnecessarily leasing a much larger block can increase cost. The objective is to match address capacity to realistic operational demand.

If you are specifically evaluating larger prefixes, see How to Lease an IPv4 Block .

Step 3: Choose the Right IPv4 Leasing Structure

Before choosing a provider, understand what type of IPv4 leasing arrangement is being offered.

Common structures include:

• shared IP leasing;
• dedicated IPv4 leasing;
• brokered IPv4 leasing; and
• first-party IPv4 leasing.

Shared IPv4

Shared addressing may involve multiple customers or services using the same addressing environment.

It can suit some temporary or low-risk workloads, but may provide less control over reputation, reverse DNS and network identity.

Dedicated IPv4

Dedicated leasing gives one customer exclusive use of an IPv4 address or block during the agreed lease period.

Production networks often prefer dedicated address space when they need stronger control over routing, reputation and infrastructure configuration.

Brokered IPv4 Leasing

A broker helps connect organizations that need IPv4 with organizations making address space available.

Businesses should understand which party ultimately handles:

• routing changes;
• ROA updates;
• reverse DNS;
• geolocation;
• reputation;
• abuse handling; and
• renewal.

First-Party IPv4 Leasing

A first-party provider supplies IPv4 through a more direct relationship between the customer and the provider responsible for the address supply.

Dedicated describes whether the customer has exclusive use.

First-party describes the relationship between the customer and the provider responsible for supplying the IPv4.

For the full comparison, read Types of IP Leasing Models .

Step 4: Check the IPv4 Block Before Leasing

Do not assume that an available IPv4 block is automatically ready for your production workload.

Check Current BGP Routing

Determine whether the prefix is currently visible in BGP.

Check:

• whether it is being announced;
• which ASN is originating it;
• whether previous routing information is consistent with the expected history; and
• whether an existing route needs to be withdrawn before deployment.

Check IP Reputation

Relevant checks may include:

• spam-related reputation;
• abuse history;
• security reputation;
• relevant blocklists; and
• application-specific reputation services.

Reputation is use-case dependent. An address suitable for ordinary web hosting may still carry historical signals relevant to an email or security service.

Check WHOIS and RDAP Information

Review relevant public registry information to understand the address resource and associated records.

The Internet Numbers Registry System and the roles of IANA and the Regional Internet Registries are described in RFC 7020 .

You can also review IANA's official IPv4 Address Space Registry .

Check Existing RPKI Status

Determine whether a Route Origin Authorization already exists for the prefix.

If a ROA exists, check:

• the authorized ASN;
• the prefix;
• maximum prefix length; and
• whether the current ROA matches the planned deployment.

Check Geolocation History

An IPv4 block may still appear in third-party geolocation databases as belonging to a previous country, city or network.

If geography matters to the service, review important geolocation databases before deployment.

Step 5: Agree on Commercial and Continuity Terms

Once the IPv4 block and provider structure are suitable, review the lease agreement carefully.

Address Space

• the IPv4 prefix or quantity;
• whether the addresses are dedicated;
• any substitution conditions; and
• the intended deployment arrangement.

Lease Period

• start date;
• initial term;
• minimum commitment;
• renewal process; and
• notice period.

Pricing

• monthly or annual price;
• billing cycle;
• setup charges;
• deposits where applicable; and
• optional operational-service charges.

For current broader pricing information, see Global IPv4 Pricing & Market Statistics .

Permitted Use

Understand what workloads are permitted and which activities could breach acceptable-use terms.

Routing

The lease or technical documentation should explain:

• whether the customer may announce the prefix;
• which ASN is authorized;
• who supplies the LOA;
• how routing changes are requested; and
• how RPKI changes are coordinated.

Abuse Handling

• who receives abuse reports;
• how the customer is notified;
• response expectations;
• escalation procedures; and
• circumstances that may lead to restriction or suspension.

Termination

Ask:

• How much notice is provided?
• When must announcements stop?
• When must the addresses be removed from production?
• What happens to ROAs and reverse DNS?
• Is migration assistance available?

Renewal

Renewal matters more as the same IP addresses become embedded in production systems.

For more detail on contractual terms, read What Is an IP Leasing Contract?

Step 6: Confirm BGP, ASN, LOA and RPKI Requirements

Technical authorization should be settled before production deployment.

Do You Need Your Own ASN to Lease IPv4?

No.

A business does not always need its own Autonomous System Number merely to lease IPv4.

In some arrangements, the provider or network partner handles routing.

Organizations operating their own BGP network may instead want to announce leased IPv4 from their own ASN.

What Is an LOA?

A Letter of Authorization can be used to demonstrate that a network has permission to announce a particular IP prefix.

An LOA may identify:

• the IPv4 prefix;
• the authorized ASN;
• the relevant organizations; and
• the authorization being granted.

Who Creates the ROA?

If RPKI is used, the Route Origin Authorization should accurately reflect the legitimate routing configuration.

A ROA commonly contains:

• the IPv4 prefix;
• the authorized origin ASN; and
• a maximum permitted prefix length.

RFC 9582 defines the technical profile for Route Origin Authorizations: RFC 9582 — A Profile for Route Origin Authorizations .

Before deployment, ask:

• Who controls the ROA?
• Which ASN will be authorized?
• What maximum prefix length is appropriate?
• How quickly can the ROA be updated?
• What happens if the origin ASN changes?
• What happens to the ROA when the lease ends?

For further technical background, see:

• What Is RPKI?
• What Is Route Origin Authorization (ROA)?

Step 7: Configure Reverse DNS, Geolocation and Abuse Contacts

Reverse DNS

Reverse DNS maps an IP address to a hostname using a PTR record.

It can matter for:

• mail infrastructure;
• hosting;
• server identification;
• logging;
• troubleshooting; and
• applications that perform reverse lookups.

Before deployment, ask:

• Can PTR records be changed?
• Who manages them?
• Can reverse DNS be delegated?
• How are updates requested?
• What is the expected response time?

For more detail, see What Is a PTR Record? A Complete Guide .

Geolocation

Commercial geolocation databases may show outdated information after an IPv4 block changes network or deployment location.

If geography matters:

• identify important databases;
• review the current location;
• submit legitimate correction requests where appropriate; and
• allow time for third-party updates.

Abuse Contacts

Confirm:

• where complaints are sent;
• who contacts your organization;
• required response times;
• escalation procedures; and
• how inaccurate reports are handled.

Step 8: Deploy, Monitor and Plan for Renewal

Do not move critical workloads onto the prefix immediately after the commercial agreement is signed.

Before Production Deployment

Check:

• BGP visibility;
• origin ASN;
• RPKI validity;
• route propagation;
• reverse DNS;
• reputation;
• geolocation;
• connectivity;
• firewall configuration; and
• application-specific requirements.

Monitor the IPv4 Block

After deployment, continue monitoring:

• BGP announcements;
• origin ASN;
• RPKI state;
• reverse DNS;
• reputation;
• geolocation;
• abuse incidents; and
• lease expiration.

Plan Renewal Early

Over time, the same IPv4 addresses may become embedded in:

• customer allowlists;
• partner systems;
• APIs;
• DNS;
• firewalls;
• VPN configurations;
• security controls;
• monitoring; and
• internal documentation.

If the workload is production-critical, discuss renewal well before the expiration date.

Can You Lease a /24 IPv4 Block?

Yes.

IPv4 providers may offer /24 blocks subject to inventory, technical requirements and commercial terms.

A /24 contains 256 IPv4 addresses.

It is a common size for:

• hosting deployments;
• enterprise infrastructure;
• smaller routed networks;
• data-center environments;
• SaaS infrastructure; and
• other production services.

What Does IPv4 Leasing Cost?

IPv4 lease pricing changes over time and can vary according to:

• block size;
• region;
• lease term;
• market supply;
• address history;
• provider structure; and
• included operational services.

Because pricing is a broader commercial topic rather than the main purpose of this how-to guide, use current market information rather than relying on a static historical number.

Global IPv4 Pricing & Market Statistics

For the broader discussion of IPv4 leasing costs, provider selection and commercial considerations, read the complete Lease IP Addresses guide .

IPv4 Leasing Pre-Deployment Checklist

• Required IPv4 block size
• Current utilization
• Expected growth
• Workload and intended use
• Dedicated or shared use
• Resource source
• Provider structure
• Lease duration
• Billing terms
• Renewal terms
• Termination notice
• Origin ASN
• BGP authorization
• LOA requirements
• RPKI / ROA
• Maximum prefix length
• IRR requirements where applicable
• Reverse DNS
• PTR management
• IP reputation
• Relevant blocklists
• Geolocation
• Abuse handling
• Technical support
• Escalation process
• Deployment testing
• Renewal planning
• Renumbering risk

What happens if we need these exact IP addresses for longer than originally planned?

Frequently Asked Questions About How to Lease IPv4 Addresses

How do I lease IPv4 addresses?

Start by defining your required address quantity, workload, expected lease duration and routing requirements. Then choose the appropriate leasing structure, review the IPv4 block, agree on contract terms, configure BGP, LOA and RPKI where necessary, set up reverse DNS and related operational services, validate the block and monitor it throughout the lease.

What information should I prepare before contacting an IPv4 provider?

• required block size;
• intended use;
• expected lease duration;
• deployment country or region;
• ASN, if applicable;
• routing requirements;
• reverse DNS requirements;
• expected start date; and
• reputation, geolocation or renewal requirements.

Do I need an ASN to lease IPv4?

No. An ASN is not always required merely to lease IPv4. It becomes particularly relevant when your organization wants to originate the leased prefix through its own BGP routing.

Can I announce leased IPv4 from my own ASN?

Depending on the provider and agreement, yes. The arrangement may require routing authorization, an LOA, an appropriate ROA, RPKI coordination and potentially IRR-related configuration.

What is an LOA when leasing IP addresses?

A Letter of Authorization can provide evidence that an organization or ASN has permission to announce a particular IPv4 prefix.

Who manages the ROA for leased IPv4?

This depends on the provider structure. Before leasing, identify who controls the ROA, which ASN will be authorized, what maximum prefix length applies and how quickly changes can be made.

What Is Route Origin Authorization (ROA)?

Should I check IPv4 reputation before leasing?

Yes, particularly for workloads where reputation can affect service quality, deliverability or security filtering.

Can I set PTR records on leased IPv4 addresses?

That depends on the provider arrangement. If reverse DNS is important to your service, confirm whether PTR records can be updated or whether reverse DNS can be delegated before signing the lease.

When should I check geolocation?

Check geolocation before production deployment if geographic classification matters to your customers or application.

What should I test before deploying leased IPv4?

At minimum, test:

• routing;
• origin ASN;
• RPKI validity;
• reverse DNS;
• reputation;
• geolocation;
• connectivity; and
• workload-specific configuration.

When should I start discussing IPv4 lease renewal?

For production workloads, start well before the expiration date. The more customers and systems depend on the addresses, the more important early renewal planning becomes.

Can I lease a /24 IPv4 block?

Yes, subject to provider availability and commercial requirements. A /24 contains 256 IPv4 addresses.

Where can I learn more about IPv4 leasing pricing and provider selection?

This article is intentionally focused on how to lease IPv4 addresses step by step.

For broader information covering pricing, provider structures, leasing models, commercial considerations and continuity, read the Lease IP Addresses: IPv4 Leasing Guide .

Conclusion

Learning how to lease IPv4 addresses should begin with a simple objective:

Get the IPv4 capacity your network needs and deploy it correctly.

Before putting leased IPv4 into production, understand:

• why the addresses are needed;
• how many addresses are required;
• which leasing structure is being used;
• who controls the resource;
• what the IPv4 history looks like;
• how routing will be authorized;
• whether an LOA is required;
• who manages RPKI;
• whether reverse DNS is supported;
• how reputation and geolocation are handled;
• how abuse incidents are escalated; and
• what happens at renewal.

For temporary infrastructure, simple address capacity may be sufficient.

For customer-facing production systems, the same IPv4 block can gradually become part of the network's operational identity.

This article focuses on the procedural side of IPv4 leasing. For pricing, provider comparison, lease-vs-buy considerations and the broader commercial decision, read our complete guide to lease IP addresses .

Ready to Lease IPv4 Addresses?

If your business has already defined its IPv4 requirements and is ready to discuss production deployment, LARUS provides first-party IPv4 leasing with operational support around routing, RPKI/ROA, reverse DNS, reputation, geolocation, abuse handling and renewal continuity.

Explore LARUS IPv4 Leasing & Continuity Assurance

Contact LARUS