Lease IP Addresses: IPv4 Leasing, Pricing, Deployment and Continuity

Need IPv4 capacity for a live network? LARUS gives ISPs, hosting providers, cloud platforms, data centres and network operators a faster path to the public IPv4 space their customers and infrastructure depend on.

Choose the scale you need, deploy it through a working route and keep the network identity your business has already built. Leasing can add capacity without committing the capital required to buy an IPv4 block outright.

This guide helps you choose the right block, understand deployment, compare the live price and see why first-party supply plus Continuity matters after your addresses enter production.

IPv4 Leasing Guide: Contents

What Does It Mean to Lease IP Addresses?

Need IPv4 capacity without tying up the capital required to buy a block? LARUS leasing gives your network a dependable path to the public IPv4 space your infrastructure and customers need, with one operating partner for delivery and Continuity.

Use leased capacity for cloud infrastructure, hosting, dedicated servers, ISP networks, data centres, telecom services, SaaS platforms and other Internet-facing systems. The decision is simple: choose the scale you need, deploy it through a working route, and keep your network identity ready for the business that depends on it.

Leased IPv4 may support:

• cloud infrastructure;
• web hosting;
• dedicated servers;
• ISP networks;
• data centers;
• telecom services;
• SaaS platforms;
• enterprise applications;
• cybersecurity infrastructure; and
• other Internet-facing services.

For a production network, however, receiving the addresses is only the first step. The addresses must also be routable, correctly authorized, operationally usable and appropriate for the intended workload.

That is why an IPv4 lease should be evaluated across the full lifecycle of the prefix—not only on the day it is delivered.

Why Do Businesses Still Lease IPv4 Addresses?

IPv4 uses a finite 32-bit address space. IANA states that its IPv4 supply has been exhausted, with recovered IPv4 resources handled through post-exhaustion allocation mechanisms.

IANA Number Resource Allocation Data

At the same time, public IPv4 remains embedded in commercial Internet infrastructure.

Cloud platforms, hosting environments, enterprise systems, customer networks, security products and other applications may still depend on IPv4 compatibility even as IPv6 deployment continues.

Businesses that need additional IPv4 generally have several choices:

• make more efficient use of existing IPv4 space;
• acquire address space through the IPv4 market; or
• lease additional IPv4 capacity.

For organizations that need address capacity without making a permanent acquisition, leasing IPv4 addresses can be a practical option.

What will your IPv4 capacity cost?

Choose capacity for the network you are building, then see the live quote for the block, region, term and operating path that fit your launch. IPv4 pricing changes with availability and the service you select, so the useful number is the current quote for your actual requirement.

LARUS keeps the decision practical: compare the capacity you need, the routing and operations around it, and the Continuity level that protects the network identity your customers already know.

See live IPv4 pricing and compare capacity

Do not plan a production network around an old screenshot or a fixed article figure. Start with today's availability and a quote built around your address count and deployment.

What Affects IPv4 Lease Pricing?

IPv4 leasing costs may be influenced by:

• IPv4 block size;
• RIR region;
• lease duration;
• current market availability;
• address history and reputation;
• geolocation requirements;
• routing requirements;
• RPKI / ROA support;
• reverse DNS requirements;
• renewal and continuity requirements;
• support level; and
• quantity.

Comparing IPv4 providers only on a headline price per IP per month can therefore be misleading.

A lower-priced prefix that later needs to be unexpectedly replaced may create a substantially larger operational cost.

Common IPv4 Block Sizes

IPv4 address space is normally expressed using CIDR prefix notation.

Prefix	Number of IPv4 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

The appropriate block size depends on current utilization, anticipated growth, routing architecture and the duration of the requirement.

A company requiring around 1,000 addresses, for example, may consider a /22. A larger hosting or cloud platform may need several blocks or a substantially larger prefix.

Organizations comparing larger blocks can also review:

How to Lease an IPv4 Block

How Does IP Address Leasing Work?

The detailed process varies between providers, but a production deployment normally begins by defining the quantity of IPv4 required, intended use, ASN, routing requirements, deployment region and expected lease duration.

1. Define your IPv4 requirement. Determine the required number of addresses, ASN, region, intended use and expected lease period.
2. Confirm IPv4 availability. The provider identifies an appropriate prefix or group of prefixes.
3. Review address history. Check reputation and previous usage where relevant to the application.
4. Review the lease agreement. Understand pricing, duration, acceptable use, termination and renewal.
5. Complete routing authorization. Coordinate LOA, ASN and BGP requirements.
6. Configure RPKI and operational services. This may include ROAs, reverse DNS and geolocation.
7. Validate before production. Test routing, RPKI, rDNS, reputation and connectivity before migration.

For a more detailed transactional walkthrough:

How to Lease IPv4 Address

What Is an LOA in IPv4 Leasing?

A Letter of Authorization (LOA) is commonly used to demonstrate that an authorized party permits a network to announce an IPv4 prefix.

For example, a transit provider may request evidence that a customer has authorization before accepting a BGP announcement for leased IPv4 address space.

An LOA may identify:

• the IPv4 prefix;
• the authorized ASN;
• the relevant organizations; and
• the scope of the authorization.

Businesses planning to announce leased IPv4 from their own ASN should confirm the routing-authorization process before production deployment.

The Role of the LOA in IPv4 Leasing

What Is RPKI and Why Does It Matter When Leasing IPv4?

Resource Public Key Infrastructure (RPKI) provides a framework for cryptographically verifiable statements relating to Internet number resources and route origins.

A Route Origin Authorization, or ROA, identifies which Autonomous System is authorized to originate a particular IP prefix.

ARIN describes a ROA as a cryptographically signed object containing the authorized origin ASN, prefix and maximum length.

ARIN Route Origin Authorization Documentation

The technical ROA profile is defined in RFC 9582.

RFC 9582 — A Profile for Route Origin Authorizations

Before deployment, make sure your network has a clear route to production:

• which ASN will originate the route;
• which prefixes require authorization;
• the appropriate maximum prefix length;
• who manages ROA changes;
• how routing changes are requested; and
• what happens when the lease ends.

RPKI keeps the route your customers reach aligned with the origin your network intends to announce. Build it into deployment so your IPv4 capacity arrives ready for real traffic.

Can Leased IP Addresses Have Reverse DNS?

Yes. Leased IPv4 addresses can support reverse DNS when the provider and address structure support the required PTR-record management or delegation.

A PTR record maps an IP address back to a hostname and can matter for:

• mail infrastructure;
• server identification;
• logging;
• network troubleshooting;
• security systems; and
• applications that perform reverse lookups.

For a smoother launch, choose the reverse-DNS path that fits your team: provider-managed, delegated to you or coordinated as part of the operating service.

What Is a PTR Record? A Complete Guide

Are Leased IP Addresses “Clean”?

A clean IP address is valuable when your services need trust from mail, security and reputation systems. Because reputation changes over time, the right provider combines address history with active operational support.

A prefix may have been used previously, and different security companies, mail providers, threat-intelligence systems and blocklists can maintain different historical signals.

Match the address history and reputation checks to the workload you are launching, especially for email, hosting, SaaS and security services.

This is particularly relevant to:

• email;
• hosting;
• SaaS platforms;
• cybersecurity services; and
• applications affected by IP-based reputation filtering.

Choose an operating partner with a visible process for:

• abuse reporting;
• investigation;
• customer communication;
• escalation; and
• remediation where appropriate.

The commercial goal is a network that keeps working: known address history, responsible use and an operating team that can act when reputation or abuse questions appear.

How Does Geolocation Work With Leased IPv4?

An IP address does not contain a physical country or city inside the address itself.

Commercial geolocation providers infer location using their own data sources and methodologies.

If an IPv4 block changes user or deployment region, some databases may temporarily retain historical information.

If location matters to the application, make the launch path clear:

• what location the prefix currently shows;
• which geolocation databases matter;
• whether legitimate correction requests are supported; and
• how much time should be allowed for updates.

Different geolocation databases update independently. A provider that understands the process helps your team plan the rollout and get the location signal aligned with the market you serve.

Lease IPv4 vs Buy IPv4: Which Is Better?

Leasing generally suits organizations that prioritize flexible operational capacity and lower upfront capital requirements. Buying may suit organizations that want a longer-term strategic IPv4 holding.

Consideration	Lease IPv4	Buy IPv4
Upfront capital	Lower	Higher
Payment structure	Recurring	Primarily acquisition cost
Temporary requirement	Strong fit	Often less efficient
Scaling flexibility	High	Requires further acquisition
Permanent acquisition	No	Potential long-term holding
Renewal dependency	Yes	Different registry and administrative dependencies
Typical fit	Operational capacity	Strategic long-term requirement

A business should evaluate how long the addresses will be needed, how much capital it wants to commit, how deeply the prefix will become embedded in production and how costly replacement would be.

Leasing vs Buying IPv4 Address

Why the Cheapest IPv4 Lease May Not Have the Lowest Total Cost

Imagine a company leases a /22 and deploys its 1,024 addresses throughout production infrastructure.

Over time, those addresses become connected to:

• DNS;
• customer configurations;
• firewall policies;
• API allowlists;
• PTR records;
• routing;
• geolocation databases;
• monitoring systems; and
• IP reputation.

If that prefix later has to be replaced unexpectedly, the cost is no longer simply the difference between two monthly per-IP rates.

The organization may need to:

1. source replacement IPv4;
2. configure new routing;
3. update RPKI;
4. update reverse DNS;
5. change DNS records;
6. change firewall rules and ACLs;
7. update customer configurations;
8. change partner allowlists;
9. correct geolocation;
10. rebuild reputation; and
11. coordinate a production migration.

Production IPv4 should therefore be evaluated using lifecycle cost, not only monthly lease price.

When IP Addresses Become Part of Network Identity

An IPv4 address begins as a numerical identifier.

After deployment, it can become part of a network's operational identity.

A production prefix may become associated with:

• customer relationships;
• application endpoints;
• DNS;
• security policies;
• reputation databases;
• external integrations;
• routing; and
• business processes.

The longer the same address space remains in production, the more systems may remember or depend on it.

This creates an important distinction between IPv4 capacity and IPv4 continuity.

IPv4 capacity means having enough addresses today.

IPv4 continuity means being able to continue using the operational identity built around those addresses.

For temporary workloads, capacity alone may be sufficient. For long-lived production infrastructure, continuity becomes much more important.

What Should You Check Before You Lease IP Addresses?

Question	Why It Matters
Who controls the underlying IPv4 resource?	Establishes the supply structure
Is the provider first-party or an intermediary?	Shows how many external dependencies exist
Can the prefix be announced from your ASN?	Determines routing usability
Is an LOA available?	May be required by transit or upstream networks
Is RPKI / ROA supported?	Important to routing validity
Is reverse DNS available?	Important for identity-sensitive workloads
What is the IP reputation history?	Can affect production use
How is geolocation handled?	Important for location-sensitive applications
What is the lease term?	Establishes the commercial time horizon
What are the termination conditions?	Defines when use can end
What happens at renewal?	Critical once the prefix is embedded in production
Who handles technical escalation?	Determines response when issues occur
What continuity options exist?	Helps assess long-term operational risk

Why Provider Structure Matters When Leasing IPv4

Not every IPv4 leasing arrangement has the same structure.

Some transactions involve a marketplace connecting independent address holders and customers. Others involve brokers, sublessors or multiple intermediary relationships.

A more direct first-party structure can look like:

First-party IPv4 provider → customer

Intermediaries can provide useful sourcing and transaction services. The issue is not that intermediaries are automatically problematic.

The important question is how many independent relationships must continue working for the customer's production network to remain stable.

Each additional contractual layer can potentially add another renewal decision, communication path, commercial dependency or operational handoff.

For temporary workloads, this may matter less. For IP addresses deeply embedded in revenue-generating infrastructure, provider structure can become much more important.

Why LARUS Uses a First-Party IPv4 Leasing Model

LARUS provides a first-party IPv4 leasing model designed around the operational lifecycle of address space rather than treating every prefix as interchangeable inventory.

The operational considerations can include:

• routing;
• RPKI / ROA;
• reverse DNS;
• IP reputation;
• abuse handling;
• geolocation;
• renewal; and
• continuity.

This approach is particularly relevant to hosting, cloud, ISP, telecom, data-center and enterprise networks where unexpected renumbering can affect customers and production systems.

The objective is not simply to make an IPv4 block available.

The objective is to provide usable IPv4 capacity together with a clearer operational lifecycle around the prefix.

Learn About LARUS IPv4 Leasing & Continuity Assurance

Why IPv4 Lease Renewal Should Be Discussed Before Deployment

Renewal can seem like a future problem when a prefix is first delivered.

At that point, few systems depend on it.

After one or two years of production use, customers may depend on those addresses, partners may have allowlisted them, DNS may point to them, PTR records may be established, security systems may recognize them, geolocation may have stabilized and reputation history may have accumulated.

The cost of switching has increased.

Before deploying a production prefix, ask:

• What is the initial lease term?
• When do renewal discussions occur?
• What notice is provided?
• Is renewal subject to availability?
• Are continuity options available?
• What happens if replacement becomes necessary?

For a network your customers rely on, make Continuity part of the buying decision from day one. It is easier to protect a working network identity before production depends on it.

Who Typically Leases IPv4 Addresses?

Hosting Providers

Hosting companies may lease IPv4 to add address capacity as server and customer demand grows.

Cloud Providers

Cloud infrastructure may require public IPv4 for workloads, gateways and Internet-facing customer services.

Data Centers

Data centers can use leased address space to support customer deployments without permanently acquiring every block.

Why Data Centers Lease IPv4 Address Space

ISPs

Internet service providers may lease IPv4 to supplement existing address capacity where public IPv4 remains necessary.

Telecom Operators

Telecom providers may require additional IPv4 for customer-facing services, network infrastructure and compatibility.

SaaS Providers

SaaS businesses may need stable public addresses for allowlisting, APIs and customer connectivity.

Enterprises

Enterprises may lease IPv4 for migrations, acquisitions, infrastructure expansion, cloud connectivity and other projects.

Cybersecurity Companies

Security providers may require public address capacity for distributed infrastructure, monitoring and other legitimate network applications.

Frequently Asked Questions About Leasing IP Addresses

Can you lease IP addresses?

Yes. Businesses can commercially lease IPv4 address space for a defined period instead of purchasing the block outright. The provider, routing structure, agreement and operational responsibilities vary between arrangements.

How do I lease an IP address?

Start by determining how many addresses you need, how long you need them, your ASN and routing requirements, deployment region and any requirements for RPKI, reverse DNS, reputation or geolocation.

Read the Step-by-Step Guide to Leasing IPv4

How much does it cost to lease an IP address?

IPv4 leasing prices vary with market conditions, region, prefix size, lease duration, address history and service requirements.

Check Current IPv4 Lease Pricing

Can I lease a /24 IPv4 block?

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

How many IPv4 addresses are in a /22?

A /22 contains 1,024 IPv4 addresses.

Can I announce leased IPv4 from my ASN?

Yes, many deployments can announce leased IPv4 from the customer ASN. LARUS helps align the route, LOA, upstream path and RPKI so your network can move into production with confidence.

What is an LOA in IPv4 leasing?

An LOA is commonly used to document authorization for a network or ASN to announce a particular IPv4 prefix.

Learn More About LOAs in IPv4 Leasing

Can leased IP addresses use RPKI?

Yes. The right ROA connects the prefix to the ASN your network intends to originate, keeping the route ready for the networks that need to reach you.

Can leased IP addresses have reverse DNS?

Yes, when reverse DNS management or delegation is supported by the provider.

Learn How PTR Records and Reverse DNS Work

Are leased IP addresses clean?

Reputation changes across external systems. Start with known address history, align it to your workload and choose an operating path that can respond when a reputation question appears.

Can leased IPv4 addresses be geolocated?

Geolocation information can often be updated to reflect legitimate network deployment, but third-party databases control their own methodologies and update schedules.

Is leasing IPv4 cheaper than buying?

Leasing keeps more capital available for the network you are building and makes it easier to scale capacity as demand changes. Compare the live quote with the cost and effort of buying and operating a block yourself.

Should I lease or buy IPv4 addresses?

Lease when you want deployable capacity now, flexible scale and an operating partner. Buy when acquiring and managing the resource itself is the strategic decision. For many live networks, LARUS combines the faster path to capacity with the Continuity choice that protects what customers already use.

Compare Leasing vs Buying IPv4

What happens when an IPv4 lease expires?

Your address plan should account for what happens next. When IPv4 is embedded in production, Continuity protects the routing, allowlists, DNS and customer relationships built around it.

Where can I lease IP addresses?

You can lease through marketplaces, brokers, address holders or a first-party IPv4 provider. Compare the path that gets your capacity live, keeps the route working and gives your business one accountable operating relationship.

Lease IP Addresses for Capacity — Plan for Continuity

Businesses usually start searching for lease IP addresses because they need more capacity.

They may need another /24, a /22 or thousands of addresses for a growing platform.

But after those addresses become part of production, quantity is no longer the only issue.

IPv4 becomes connected to routing, applications, customers, reputation, DNS, security and external systems.

It becomes part of the network's operational identity.

Organizations evaluating an IPv4 lease should therefore ask:

• Can we obtain the capacity we need?
• Can we deploy the addresses correctly?
• Do we understand the provider and resource structure?
• Can we manage the prefix throughout its operational lifecycle?
• Can we maintain continuity for as long as the business depends on it?

LARUS provides first-party IPv4 leasing for organisations that want capacity and an operating relationship built around routing, RPKI/ROA, reverse DNS, reputation, abuse handling, geolocation and renewal.

Learn About LARUS IPv4 Leasing & Continuity Assurance