IPv4 leasing: the short answer
To rent or lease IPv4 addresses, define the exact CIDR block and intended use, verify the lessor's authority, agree who will announce the route, and put price, term, renewal, abuse handling, and return conditions in writing. A lease grants a time-limited contractual right to use a prefix. It does not transfer the prefix's registry registration or guarantee that every network or application will accept it.
Leasing can fit temporary capacity, a staged migration, or a lower initial capital commitment. Buying can fit a longer planning horizon and a need for control after an approved transfer. In either case, the address block still needs valid authority, routing, DNS, reputation review, monitoring, and an exit plan.
What is IPv4 address leasing?
IPv4 address leasing is a commercial arrangement in which a resource holder or authorized lessor permits another organization to use a specified IPv4 prefix for an agreed period. The contract should identify the exact CIDR, the parties, permitted use, price unit, start and end conditions, and the operating work each party controls.
| Access path | What you receive | What still needs proof |
|---|---|---|
| Provider-assigned address | Use of one or more addresses as part of connectivity or hosting | Portability, routing control, service term, and what happens when the provider changes |
| IPv4 lease | A time-limited contractual right to use an exact prefix | Lessor authority, route authorization, operating responsibilities, renewal, and return |
| IPv4 purchase and transfer | Longer-horizon control after the applicable registry transfer completes | Transfer eligibility, approval, records, routing, reputation, and integration |
| RIR allocation or assignment | Registration under the applicable RIR's current policy | Eligibility, ongoing obligations, routing, and application fit; an RIR is not a leasing marketplace |
A registry or RDAP record is important evidence about registration, but it is not the lease contract and does not identify the current user behind an address. Likewise, a live BGP route does not by itself prove that the announcer has contractual authority to use the prefix.
How to rent or lease IPv4 addresses
- Define the requirement. Record the address count, CIDR size, region, intended workload, origin ASN, upstream network, start date, term, traffic profile, growth margin, and whether several prefixes are acceptable.
- Find candidate supply. Ask for the exact prefixes available for review. A marketplace listing or indicative availability is not a reservation, accepted order, or proof that the block fits the workload.
- Verify the source. Follow the authoritative RIR or RDAP record, identify the registered organization and counterparty, and obtain evidence that the lessor can grant the proposed use and routing authority.
- Validate routing and records. Agree the announcing ASN, upstream acceptance, LOA if required, IRR route object, RPKI ROA, reverse DNS, geofeed or geolocation work, and the order in which changes will be made.
- Assess the exact prefix. Capture dated BGP, RPKI, IRR, DNS, geolocation, reputation, blocklist, and application-specific observations. Define acceptance criteria before treating any vendor score as a verdict.
- Compare complete terms. Normalize the price and include setup, support, minimum term, payment, renewal, incident, replacement, return, and renumbering conditions.
- Test and activate. Use a documented change window, route and reachability checks, application acceptance tests, named owners, and a rollback path. Do not send unauthorized production traffic during diligence.
- Operate and exit deliberately. Monitor the evidence that matters to the workload and retain the renewal dates, withdrawal order, configuration cleanup, replacement capacity, and return record.
If you want a coordinated path through those steps, use managed IPv4 leasing. To inspect public candidate supply, open the IPv4 marketplace.
Choose the block size before comparing offers
A CIDR prefix expresses both the network boundary and the nominal address count. Do not request a /24 only because it is familiar: calculate public endpoints, subnet boundaries, reserve, routing policy, provider filters, and growth first.
| Prefix | Nominal addresses | Planning question |
|---|---|---|
/24 | 256 | Does the workload and upstream routing policy support this exact prefix? |
/23 | 512 | Can one aggregate be used, or are separate routing and operational boundaries required? |
/22 | 1,024 | Are growth, segmentation, and failure domains included in the requirement? |
/21 | 2,048 | Can the team operate, monitor, and eventually renumber this capacity? |
Nominal address count is not the same as assignable application capacity. Network and broadcast treatment, anycast, gateways, reserves, provider architecture, and platform rules can change what is usable. Confirm both the billing count and the deployment design.
What should you check before leasing an IPv4 block?
| Area | Evidence to request | Decision it supports |
|---|---|---|
| Prefix and authority | Exact CIDR, authoritative RIR/RDAP record, counterparty identity, contractual chain, disputes or encumbrances disclosed | Whether the proposed lessor can grant the stated use |
| Routing | Origin ASN, upstream acceptance, LOA where required, IRR route object, ROA prefix and maxLength, activation order | Whether the route can be authorized and accepted as designed |
| Network records | Reverse-DNS control, registry contacts, geofeed or correction process, current route visibility | Whether operational records can be changed and maintained |
| Reputation and fit | Dated source-specific blocklist, mail, fraud, geolocation, reachability, and application observations | Whether the exact prefix meets predefined workload criteria now |
| Operations | Monitoring owner, abuse desk, escalation path, response terms, remediation and bounded replacement conditions | Who acts when routing, reputation, or use changes |
| Commercial lifecycle | Price unit, currency, fees, deposit, term, renewal formula, notice dates, termination, return, withdrawal, and deletion steps | Total cost and continuity through the end of the lease |
Preserve the source and timestamp for every changing result. “Clean IP” is not a durable property: third-party datasets differ, new activity can change a classification, and no provider controls every recipient, network, blocklist, or application.
LOA, IRR, RPKI, ROA, and BGP: what each one does
- Contract: states the commercial right to use the prefix and the parties' obligations. It does not publish routing data to the Internet.
- LOA: is a letter or other evidence used in some operating workflows to show that an ASN is permitted to announce a prefix. Its required form and acceptance depend on the parties and upstreams.
- IRR route object: publishes an IPv4 prefix and origin ASN relationship in an Internet Routing Registry. Operators may use IRR data to build filters, but the object does not force every network to accept a route.
- RPKI ROA: is a cryptographically signed object stating which origin ASN is authorized for a prefix and its maximum length. Route Origin Validation can classify a matching BGP origin, but a ROA is not a lease contract and does not prove that the route is live.
- BGP announcement: is the route propagated by an ASN. Reachability also depends on upstream policy, filtering, propagation, path selection, and correct network configuration.
Record who can create, change, and withdraw each artifact. The party signing the lease may not control the RPKI certificate, IRR maintainer, upstream filter, DNS delegation, or origin ASN, so an unexplained promise of “routing support” is not enough.
How much does it cost to lease IPv4 addresses?
There is no universal current IPv4 lease price. A proposal may be quoted per address per month, for the whole block, annually, or under a negotiated minimum commitment. Record the date, currency, billing count, minimum term, and what operating work is included before comparing numbers.
Base term cost = billed addresses × rate per address per billing period × number of periods. Then add one-time setup, routing and registry work, DNS, support, tax, monitoring, renewal, and exit costs. If a provider quotes a block total, preserve that total rather than inventing a per-address precision it did not offer.
- Prefix and supply: block size, aggregation, RIR region, current inventory, and whether a larger block can be split.
- Term and payment: minimum commitment, prepayment, deposit, renewal option, repricing, and early termination.
- Routing and activation: origin model, upstream work, LOA, IRR, ROA, DNS, geolocation, and change-window support.
- Application fit: dated reputation and acceptance evidence, remediation effort, and any bounded replacement conditions.
- Operations and exit: monitoring, abuse response, support hours, route withdrawal, return, and renumbering assistance.
Use the IPv4 cost calculator to normalize a quoted rate and term. For a deeper cost model, read the IPv4 lease price guide.
Should you lease or buy IPv4 addresses?
| Factor | Leasing may fit when | Buying may fit when |
|---|---|---|
| Planning horizon | Capacity is temporary, uncertain, or expected to change | The requirement is durable and an eligible transfer is practical |
| Capital | A lower initial commitment matters more than recurring rent | The organization can fund acquisition and transfer work |
| Control | Contractual use and defined operating support are sufficient | Longer-horizon registry and operating control is required after transfer |
| Exit | Return and renumbering are acceptable at the end of the term | The organization accepts transfer, integration, and later disposition work |
| Risk | Renewal, source-authority, and availability risks are bounded by the agreement | Market, transfer, capital, and long-term operating risks are acceptable |
Compare both paths over the same horizon. A rough address-only break-even calculation omits transfer fees, financing, support, renewal uncertainty, residual value, and renumbering. Review the complete acquisition path on Buy IPv4 Addresses.
What belongs in an IPv4 lease agreement?
- The exact CIDR, registered resource, permitted workload, prohibited use, locations, origin ASN, and upstream model.
- The price unit, billed count, currency, taxes, setup charges, deposit, payment timing, minimum term, and start condition.
- The parties responsible for LOA, IRR, ROA, BGP, reverse DNS, registry contacts, geolocation, monitoring, and evidence retention.
- Acceptance tests, service scope, maintenance windows, support hours, abuse reporting, escalation, and incident response.
- Representations about authority and condition, with precise remedies rather than an unlimited “clean” or “globally routable” guarantee.
- Renewal notice, repricing, source-authority change, suspension, termination, replacement criteria, route withdrawal, return, and renumbering.
Technical evidence and contract language solve different problems. Preserve both, assign an owner to every dependency, and obtain appropriate legal review for the agreement and intended use.
After activation: operate the leased prefix
Confirm the expected route origin and RPKI state from outside the announcing network, test reachability from representative locations, validate reverse DNS and required application behavior, and save the accepted baseline. Monitor only signals tied to the workload and define who can change or withdraw the route.
Keep renewal and exit dates visible before they become incidents. A safe return normally coordinates customer traffic migration, DNS and allowlist changes, route withdrawal, ROA and IRR updates, reverse-DNS cleanup, configuration and credential removal, evidence retention, and written confirmation between the parties.
IPv4 leasing FAQ
Can you rent an IP address?
Yes. Providers can assign individual addresses with a service, and organizations can lease an IPv4 prefix under a commercial agreement. The agreement must define the exact address scope, authority, routing, term, permitted use, price, operations, renewal, and return.
How do I rent or lease IPv4 addresses?
Define the CIDR and workload, review exact candidate prefixes, verify the RIR record and lessor authority, agree BGP and record changes, assess dated reputation and application evidence, sign complete commercial terms, then test and activate through a controlled change.
How much does it cost to lease IPv4 addresses?
There is no universal current price. Normalize a dated quote by billed address count, period, currency, term, and included services, then add setup, routing, DNS, support, monitoring, renewal, tax, and exit costs.
Does an IPv4 lease transfer ownership?
No. A lease grants a contractual right to use a defined prefix for a period. It does not by itself transfer the registry registration. A purchase follows a separate transfer process under the applicable RIR policy and agreement.
Can I announce leased IPv4 space from my ASN?
Only when the source authority, contract, prefix length, upstream policy, and required routing records support that model. Confirm the LOA process, IRR route object, RPKI ROA, provider filters, activation order, and withdrawal plan before signing.
What is the difference between an LOA and a ROA?
An LOA is documentary authorization used by parties or upstreams in some routing workflows. A ROA is a cryptographically signed RPKI object that identifies an authorized origin ASN, prefix, and maximum length. Neither replaces the lease contract, and neither guarantees global route acceptance.
Can a provider guarantee clean IP addresses?
No provider controls every future reputation source, blocklist, network, recipient, or application. Request dated source-specific evidence, define acceptance criteria, monitor relevant changes, and write bounded remediation or replacement conditions into the agreement.
What happens when an IPv4 lease ends?
The lessee migrates traffic and removes dependent configurations; the responsible parties withdraw BGP authorization, ROAs, IRR objects, reverse DNS, and other records in the agreed order; the prefix is returned or quarantined as specified; and both sides retain a completion record.
