IPv4 Leasing vs Sub-Leasing: What Network Operators Need to Know

The IPv4 market keeps getting tighter. Organizations that can’t justify buying address blocks outright are turning to rental arrangements instead. Fair enough. But here’s where things get messy: not all rental models work the same way, and the difference between IPv4 leasing and sub-leasing can mean the difference between a clean, stable deployment and a renumbering emergency at 2 a.m.

What Is IPv4 Leasing?

IPv4 leasing is a direct contract between whoever holds an address block (the lessor) and the organization that needs the space (the lessee). Simple enough. The lessor keeps ownership; the lessee gets the right to announce and route the prefixes for the length of the lease.

Need IPv4 addresses?

Browse clean, RIPE-verified subnets at $0.50/IP/month.

Browse Subnets →

How a Typical Lease Works

  1. Lessor and lessee agree on block size (usually /22 to /24), lease duration (12–48 months), and monthly pricing.
  2. RIR (ARIN, RIPE NCC, APNIC, etc.) registration records are updated to reflect the arrangement, or it’s documented via an LOA (Letter of Authorization).
  3. The lessee announces the prefixes via BGP under its own ASN, often with RPKI ROAs created for route validation.
  4. When the term ends, the block goes back—or the lease renews.

Rates? Right now, leased IPv4 space typically runs $0.30 to $0.50 per IP per month, depending on block size, region, and contract length. Bigger, clean /22 or /23 blocks command a premium. Scarcity does that.

What Is IPv4 Sub-Leasing?

Sub-leasing is what happens when a lessee—already renting space from the original owner—re-rents part (or all) of that space to someone else. No direct owner-to-user relationship anymore. Instead you get a chain: owner → primary lessee → sub-lessee.

Common Sub-Leasing Scenarios

  • A hosting provider leases a /21 but only needs a /23, and sub-leases the remainder downstream.
  • An ISP consolidates several leases and redistributes unused capacity to partners.
  • A cloud or colocation provider bundles IP space into its service offerings.
Key point: In sub-leasing, the sub-lessee has no direct relationship with the block owner. All rights flow through the middle party’s contract. Which means your access to the space is only ever as strong as the original lease.

Key Differences at a Glance

Factor Direct IPv4 Leasing IPv4 Sub-Leasing
Parties involved Two: owner (lessor) and user (lessee) Three or more: owner, lessee, sub-lessee
Contractual security Direct rights under the primary agreement Depends on upstream lease terms
Owner consent Not required (the owner is your counterparty) Usually required; often prohibited without written approval
Announcement rights Clear and documented (LOA/ROA) Can be ambiguous; chain of authorization needed
Blacklist exposure Moderate; vetting possible at lease start Higher; you inherit reputation from prior use
Price Market rate, transparent Often marked up by the middle party
Termination risk Defined by contract Cascading—if the head lease ends, sub-leases can collapse

Risks and Compliance Considerations

1. Contractual Chain Risk

The big one. Cascading termination. If the original lease dies—non-payment, breach, or the lessor selling the block—every downstream sub-lease can be voided overnight. Suddenly you’re doing emergency renumbering under pressure.

2. RIR Policy Restrictions

Some Regional Internet Registries scrutinize address utilization and may question arrangements where recorded use doesn’t match actual routing. Sub-lease without proper documentation and you can trigger an RIR audit, or worse, resource revocation. RIPE NCC, for instance, expects sponsoring LIRs to keep accurate end-user assignment records.

3. Reputation and Blacklisting

Sub-leased blocks often carry hidden history. Spam listings on Spamhaus or SORBS. Abusive routing past. Stale RPKI state. Run block history checks before committing—always.

Warning: Never accept sub-leased space without written consent from the original block owner. Without it, you have no enforceable rights if the primary lease fails, and your BGP announcements could be reclaimed by the legitimate holder.

Which Model Should You Choose?

Choose Direct Leasing When:

  • You need reliable, long-term address space for production infrastructure.
  • You want clean blocks with verifiable history and direct contractual recourse.
  • You operate BGP under your own ASN and need RPKI-validated routing.

Sub-Leasing Makes Sense When:

  • You’ve got surplus capacity in an existing lease and want to recover costs.
  • The downstream need is short-term, non-critical, or developmental.
  • You can secure explicit written authorization from the block owner.

Practical Tips Before Signing Any Lease

  1. Verify ownership: Cross-check the block against RIR WHOIS and registry transfer databases.
  2. Check block history: Blacklists, previous announcements, geolocation records. All of it.
  3. Insist on RPKI: Require ROAs for the lease term and confirm they cover your ASN.
  4. Negotiate termination protections: Notice periods (90+ days) and transition assistance clauses.
  5. Document everything: LOAs, consents, utilization reports. They’ll save you in disputes and audits.
Pro tip: Work with a marketplace that vets sellers and lessors. Platforms like IP4 Market verify block ownership, clean history, and seller legitimacy before listing—which cuts your due diligence burden dramatically and offers competitive pricing on both leases and purchases.

Frequently Asked Questions

Is sub-leasing IPv4 addresses legal?

Generally, yes—but only if the original lease agreement permits it, and in many cases with the owner’s written consent. RIR policies also require accurate registration of end-use. Sub-lease in violation of your lease and you can void your own rights, plus expose yourself to legal claims.

Can a sub-leased block be announced under my own ASN?

Technically yes, via BGP with a properly issued LOA and RPKI ROA. The catch: the chain of authorization has to be complete and unbroken. Any gap risks the announcement being flagged or reclaimed.

Is leasing cheaper than buying IPv4 space?

Upfront? Absolutely. Buying costs run around $40–$60 per IP, so a /24 purchase can exceed $10,000. Leasing the same block might run $100–$130 a month. Buying becomes the better deal somewhere around the 6–8 year mark of continuous need.

What happens to my services if the head lease terminates?

If you’re a sub-lessee, you can lose routing rights with little notice. That’s precisely why termination notice clauses and owner consent aren’t optional extras—they’re the whole ballgame. Direct lessees face far less exposure because their contract is with the owner itself.

Final Thoughts

IPv4 leasing and sub-leasing answer different problems. Direct leasing gives you security and clarity for critical infrastructure; sub-leasing is a flexible way to optimize surplus capacity—as long as it’s done transparently and with proper authorization. Whichever route you take, verify ownership, history, and contractual rights before anything goes live. Partnering with a trusted marketplace like IP4 Market means every transaction—purchase, lease, or sub-lease—is backed by verified sellers and industry-grade due diligence.

Need IPv4 space? Lease RIPE-verified /24–/22 subnets at a flat €0.50/IP per month — LOA + RPKI/ROA in minutes, instant company verification, automatic renewals. Browse available subnets →

Share:
IP4

ip4.market Team

Expert content on IPv4 leasing, IP address management, and network infrastructure from the ip4.market team.