Your IPv4 Block Stays Yours: How Leasing Actually Works

Talking with IPv4 owners about leasing, I keep hearing the same thing in different forms. "I just want to be sure my blocks stay mine." Or: "I don't want to lease because I'm afraid of losing my addresses."

These are reasonable things to say. The question behind them deserves a structural answer, not a sales pitch.

IPv4 leasing risks are among the most common topics when LIRs and enterprises consider monetization for the first time – and most of those conversations mix up two things that operate on completely separate levels: ownership and routing. Understanding how each works, and how each is governed, is what makes the concern resolvable.

That's what this article covers: what your RIR registration actually means, what a lease does and does not transfer, and what tools exist to protect your block throughout its time in a lessee's hands.

What IPv4 Ownership Actually Means

IPv4 addresses are not property in the traditional legal sense – they are resources allocated by Regional Internet Registries (RIRs) under specific policies. In the RIPE region, RIPE NCC maintains the authoritative record of which organization holds each address block. ARIN and APNIC maintain equivalent registries for their respective regions.

When you hold an IPv4 block, you hold a registration: your organization is listed in the WHOIS database as the resource holder. This registration is what conveys the right to use, route, or lease the space. It does not transfer when you lease. It does not change when a lessee announces the block via BGP. The WHOIS record continues to show your organization as the responsible party.

This distinction matters because RIR registration is the root of control. If a dispute arises, the registered holder has standing. If a lessee defaults, the registered holder has the right to revoke routing permissions. The lease itself is built on top of that registration – it does not replace it.

IPv4 address ownership vs leasing therefore comes down to this: ownership is a registry relationship between you and your RIR. Leasing is an operational arrangement between you and a third party. The two layers run in parallel and do not interfere with each other.

What a Lease Transfers – and What It Does Not

A well-structured IPv4 lease grants one thing: routing authority. Specifically, it grants the lessee the right to announce the address block via Border Gateway Protocol (BGP) for the duration of the lease, and to originate traffic from those addresses.

It does not transfer:

• The RIR registration (WHOIS continues to show the lessor)

• The right to sublease without authorization

• Ownership of the address block in any legal or RIR sense

• The ability to hold the block past lease expiry

RIR policy reinforces this. Under RIPE, ARIN, and APNIC frameworks, leasing is classified as a utilization arrangement, not a transfer event. A transfer — which would change the registered holder – requires a separate, formal process involving the RIR directly and, in most cases, payment of a transfer fee and compliance review. A lease bypasses none of those steps because it is not a transfer.

The practical implication: your block cannot be "taken" through a lease. The lessee routes it; they do not own it.

Legal and Technical Protections for Block Owners

IPv4 block security is maintained through a combination of contractual, technical, and policy mechanisms. Understanding all three is useful when evaluating whether a specific lease structure adequately protects your interests.

Letter of Authorization (LOA)

Before a lessee can route your space, they require a Letter of Authorization – a document signed by the registered holder (you) granting them permission to announce the block. The LOA specifies which prefixes are covered, what the permitted use is, and for how long. Without a current, valid LOA, upstream providers and Internet Exchange Points will not accept the lessee's BGP announcements. Withdrawing or expiring the LOA terminates routing authority without any further action from the lessee.

RPKI and Route Origin Authorizations (ROAs)

Resource Public Key Infrastructure (RPKI) allows registered IP holders to cryptographically sign routing announcements. A Route Origin Authorization (ROA) specifies which Autonomous System Number (ASN) is permitted to originate a given prefix. If a lessee's AS number changes, or if a lease ends, you can revoke or update the ROA, which will cause RPKI-validating routers to reject unauthorized announcements.

RPKI lease protection is increasingly relevant: major networks and IXPs now enforce RPKI validation, meaning an unauthorized announcement of your block by a former lessee would fail at scale. This is a structural control, not just a contractual one.

IPv4 owner protection through contract terms

A professionally drafted lease agreement should include: clearly defined lease scope (specific prefixes), the lease term with start and end dates, return conditions and process, lessee obligations regarding acceptable use, the owner's right to inspect or audit utilization, and remedies for breach including early termination rights. Platform-based leases, such as those structured through IPbnb, incorporate these provisions by default into their standard agreements.

Abuse Risk and Reputation Management

IPv4 owner protection extends beyond routing rights into the operational question of what happens if a lessee misuses the space. This is not a trivial concern: blacklisted addresses reduce market value and create operational friction when the block is returned.

Several mechanisms address this directly.

Contractual obligations

A well-structured lease assigns explicit acceptable use obligations to the lessee. Spam, scanning, DDoS amplification, and fraudulent traffic should each be enumerated as prohibited use cases. Breach of these provisions creates a contractual right of termination, separate from any technical reclaim mechanism.

Monitoring during the lease

Owners can and should monitor their leased space for reputation issues throughout the lease term. Tools such as Spamhaus, Cisco Talos, and IPQS provide prefix-level blacklist lookup. IPbnb's platform integrates IP reputation monitoring so owners receive alerts if a block associated with their account appears on major blacklists – allowing intervention before damage compounds.

Remediation responsibility

A professionally structured lease should specify which party is responsible for blacklist removal. Industry practice assigns this obligation to the lessee for blacklistings that occur during their tenancy. The lessor retains the right to take over remediation if the lessee fails to act within a defined window.

IP address leasing safety at the reputation level is therefore a contractual and monitoring question, not simply a technical one. Owners who select lessees through a vetted marketplace and include proper acceptable-use provisions are substantially better protected than those arranging informal leases without written terms.

End-of-Lease Mechanics – Reclaiming Your Block

The end-of-lease process is where ownership rights become most concrete. Understanding the sequence removes ambiguity about what reclaiming the block actually looks like.

Step 1: LOA expiry or revocation

At lease end, the LOA is either allowed to expire (if time-limited) or actively revoked by the owner. Without a valid LOA, the lessee's upstream provider will withdraw the BGP announcement. This typically takes effect within 24 to 72 hours of LOA withdrawal, depending on the upstream provider's update cycle.

Step 2: ROA update

The owner updates or removes the ROA in the RPKI system to reflect that the prior lessee's ASN is no longer authorized. This is completed through the RIR's portal (RIPE NCC's RPKI dashboard, for example) and propagates across the routing table within hours.

Step 3: Routing confirmation

The owner can verify that the block is no longer being announced by the lessee using standard looking glass tools or BGP monitoring services. Once de-announced, the block is effectively dormant – it cannot be routed by anyone without a new LOA from the owner.

Step 4: Block re-evaluation

Before leasing again or returning the block to production use, the owner should run a reputation check across major blacklists. If blacklistings exist from the previous tenancy, the owner can initiate removal through standard delisting processes, referencing the end of the prior lease and their status as the registered holder.

The full sequence – from LOA revocation to confirmed de-announcement – typically completes within two to five business days. Registered holders retain full control of the block throughout and at the conclusion of this process.

Leasing as a Capital Efficiency Decision

Leasing is not a risk event. I want to be direct about that. It is a capital efficiency decision – one that leaves your ownership registration untouched, your routing rights recoverable, and the value of your block working rather than dormant.

The protections described in this article are not aspirational. LOA-scoped routing authority, RPKI enforcement, contractual acceptable-use terms, blacklist monitoring with defined remediation responsibility – this is what a properly structured lease looks like in practice.

IPbnb is built around that structure by default. Owners who lease through the platform get a signed LOA, RPKI-compliant routing setup, standard AUP terms, and active reputation monitoring without having to negotiate each element individually. End-of-lease return follows a defined process. The controls are in the agreement and in the platform – not dependent on lessee goodwill.

If you've been hesitant to lease your IPv4 space, I'd encourage you to request a lease evaluation. The question is no longer whether safe IPv4 leasing is possible. It's whether your specific block is ready to start generating a return.