Renting IPv4: the short answer
Renting IPv4 addresses gives an organization time-limited use of an identified address block under an agreement with the party authorized to provide it. Before relying on the block, confirm the exact CIDR, the holder's authority, who can announce it, the lease term, routing and abuse responsibilities, renewal terms, and how service will continue if the block must be returned. Paying for a lease does not by itself make a prefix routable, reachable, reputable, or reserved for your use.
This guide focuses on continuity: keeping a production service working through activation, renewal, provider change, and exit. For a fuller explanation of the leasing process, read the IPv4 leasing guide. For a case-specific service path, review managed IPv4 leasing.
What does it mean to rent IPv4 addresses?
A commercial lease or rental normally grants a defined right to use an IPv4 prefix for a defined period. It does not transfer the resource holder's registry position to the customer. The holder, lessor, network operator, and customer may be different organizations; the agreement and operational records must say who owns each action. A DHCP “lease” assigning an address to a device is a different, local network mechanism.
The useful unit is usually a CIDR block, not an unspecified quantity of addresses. Record the prefix and its size, region of use, origin ASN, upstream acceptance requirements, and whether the customer may announce it independently. A single hosted address, a provider-routed block, and a customer-announced block have different dependencies.
When renting can fit
Renting can fit a time-bounded rollout, variable demand, or a need to avoid a large upfront purchase. Buying may fit a long-lived network that needs a registry-recognized resource position and can complete the applicable transfer process. Neither choice guarantees immediate deployment or lower lifetime cost.
Rent IPv4 versus buy IPv4
| Decision factor | Rent | Buy through a registry transfer |
|---|---|---|
| Control and term | Contractual use for an agreed term; renewal and return matter. | Recipient position follows the applicable registry's approved transfer and agreements. |
| Cash flow | Recurring charges plus setup, routing, operations, and possible exit costs. | Purchase and transfer costs plus ongoing registry, routing, and operations costs. |
| Change risk | Holder or provider changes, non-renewal, and renumbering may affect service. | Transfer approval, block history, integration, and future operations remain risks. |
| Best next check | Can the holder authorize the intended use and route for the whole required term? | Can the buyer satisfy the registry's transfer requirements and operate the block? |
Compare both choices over the same period and capacity, including a realistic replacement plan. The IPv4 cost calculator can organize your own inputs; it cannot validate an offer or forecast a market price.
How to rent IPv4 addresses in five steps
- Define the need. Record required usable capacity, acceptable prefix length, geography, intended use, traffic, origin ASN, upstreams, start date, growth, and whether provider-routed or customer-announced space is required. Check whether IPv6, address sharing, or existing allocations cover part of the requirement.
- Verify the resource and authority. Confirm the exact CIDR and registry record, the contracting entity's authority, permitted use and subdelegation, and the party that can provide a Letter of Authorization when required. Check dated reputation and abuse history; no single score proves a prefix is clean.
- Agree the operating model. Name the owners of BGP announcements, upstream filters, IRR route objects, RPKI Route Origin Authorizations (ROAs), reverse DNS, geofeed, abuse contacts, support, and incident response. A ROA identifies an authorized origin ASN and prefix; it is not a lease contract or an end-to-end reachability guarantee.
- Compare the full agreement. Check setup and recurring charges, taxes and fees, term, renewal notice, permitted use, remedies for a route or reputation problem, replacement criteria, support response, termination, and return obligations. Confirm which promises are measurable and which depend on third parties.
- Activate and rehearse exit. Verify route acceptance and RPKI state from relevant networks, DNS and application behavior, monitoring, abuse escalation, and a rollback path. Before production cutover, document how to replace the prefix, update allowlists and DNS, notify customers if needed, and return the resource.
A broker or marketplace can help identify potential supply, but the same verification applies to every offer. Current marketplace listings are a discovery starting point, not proof of availability, suitability, or routing permission.
What is IPv4 continuity risk?
Continuity risk is the chance that a service depending on the rented addresses is interrupted, constrained, or forced to renumber. The useful question is not merely whether a block can be activated today, but which evidence and fallback will still exist at renewal or provider change.
Four continuity risks to assign
- Authority: the holder cannot provide or maintain the required authorization, or the contract does not cover the intended use. Owner: procurement and the resource holder; evidence: registry record, signed agreement, and authorization path.
- Routing: an upstream rejects the prefix or origin, or an IRR or ROA change makes announcements invalid. Owner: network operations and the authorizing party; evidence: accepted routes, valid origin state, and a tested rollback.
- Reputation and abuse: block history or current traffic causes filtering or complaints. Owner: security and abuse teams; evidence: dated checks, monitored reports, contacts, and response times.
- Renewal and exit: the block cannot be renewed on acceptable terms or a replacement cannot be cut over in time. Owner: service owner; evidence: notice dates, replacement options, renumbering inventory, and rehearsal results.
Ten questions to answer before signing
- Which exact CIDR, origin ASN, network, region, and application are in scope?
- Who is the registered holder, and who may authorize this use and announcement?
- Will the provider route the block, or will our network announce it?
- Who creates and maintains the LOA, IRR object, ROA, reverse DNS, and abuse contact?
- What dated reputation evidence exists, and what happens if filtering appears?
- What are the setup, recurring, support, and exit costs over the same period?
- What is the start condition, service acceptance test, and remedy if activation fails?
- When must renewal be decided, and how much notice can either party give?
- Which services, allowlists, and customers must move if the prefix changes?
- Who owns the return procedure and verifies the old route and records are withdrawn?
Five avoidable mistakes
Do not compare quotes without matching prefix size and term; accept a vague “clean IP” promise without dated evidence; treat a LOA, IRR object, and ROA as interchangeable; assume a global route will be accepted just because the block exists; or leave renewal and renumbering until the notice window closes. Each mistake can be prevented by an assigned owner, an evidence record, and a tested fallback.
What does IPv4 rental actually cost?
There is no universal rate. A comparable total includes the quoted block and term, setup, support, routing or transit, registry-related work, monitoring, abuse handling, taxes, contract changes, and possible migration or renumbering. Prefix size, availability, permitted use, and the operating model affect offers. Request a dated written quote for the exact requirement and compare it with a purchase scenario over the same time horizon.
Turn a rental into an operating plan
Renting is useful when its term and control model fit the service. Before relying on it, verify authority, activate with measurable tests, assign recurring responsibilities, and make renewal or replacement a scheduled decision. If the requirement is already defined, review the managed leasing path or share the case details for an offer-specific discussion.
IPv4 rental questions
Is renting IPv4 the same as buying it?
No. A rental grants contractual use for a term. A purchase normally requires a transfer accepted by the applicable regional registry. Both require separate routing and operational work.
Can rented IPv4 be announced from our ASN?
Sometimes. Confirm the holder's permission, the exact prefix, a suitable LOA where required, upstream policy, IRR and RPKI responsibilities, and observed route acceptance before promising a cutover.
Does an RPKI ROA prove that an address block is safe or reachable?
No. A ROA states which ASN may originate a prefix within the configured maximum length. It does not validate the contract, reputation, upstream acceptance, DNS, firewall, or application availability.
What happens when an IPv4 rental ends?
Follow the agreement's return and notice terms. Move dependent services, update DNS and allowlists, withdraw route and authorization records as appropriate, verify traffic has moved, and retain a completion record.
