IP Leasing Contract: Key Clauses and RIR Policy Rules

An IP leasing contract lets a network use an address block that stays registered to the lessor, for a fee and a fixed term. In the RIPE region the lessor is usually an LIR. The leased block is registered as a PA assignment or sub-allocation from its allocation, and the IPv4 policy makes a contract mandatory for PA space (ripe-826, section 7.0: "clear contractual arrangements are mandatory for PA space"). The registration itself is not property (ripe-812, article 10.2), so the contract is the lessee's only protection. This page describes the usual terms as of September 2026 and is not legal advice: have a lawyer in your jurisdiction review any agreement before you sign.

Understanding the Legal Framework

The Nature of IP Address Rights

In the RIPE region, registering an address block does not create property. The RIPE NCC Standard Service Agreement (ripe-812, article 10.2) states that the registration of Internet number resources "does not constitute property" and "does not confer upon the Member or the third party any rights of ownership". The IPv6 policy says the same in its principles: address space is not to be considered property (ripe-738, section 4.1). What a holder has is a right to the registration, subject to RIPE policies, and that right can be transferred under the transfer policy (ripe-807).

That right has value, and courts treat it as an asset. On 16 December 2019 Dutch bailiffs served the RIPE NCC with a court order seizing the right to registration of a member's IPv4 addresses to recover a debt. The RIPE NCC blocked transfers of the block and, once it had been auctioned, registered it to the buyer (RIPE Labs, October 2020). The conditions under which the RIPE NCC executes such orders are in ripe-815, section 4.1.

For a lease this means three things. The lessor keeps the registration. The lessee gets a contractual licence to use the addresses for the term and acquires no right against the registry. Whether the lessee can rely on the block for the whole term depends on the contract and on the lessor staying in good standing with its RIR.

RIR Policy Frameworks

Each RIR publishes its own rules. None of them regulates the lease contract itself; what they regulate is who may be registered as the user of a block and on what conditions (the word "lease" does not appear in ripe-826, ripe-738, ARIN's NRPM or APNIC-127). In the RIPE NCC region the IPv4 policy is ripe-826, transfers are governed by ripe-807, and the full list is on the RIPE policies index. ARIN publishes its Number Resource Policy Manual (version 2025.1, 3 March 2026).

RIPE NCC (Europe, Middle East, Central Asia). A lease is registered as an assignment: the lessor LIR creates an inetnum with status ASSIGNED PA, or SUB-ALLOCATED PA when the lessee will assign to its own customers, inside its allocation, and ripe-826 section 7.0 makes a contract mandatory for PA space. Transfers of the registration itself need no needs justification since proposal 2013-03, accepted on 4 February 2014; inbound transfers from needs-based regions still require a plan to use 50% of the space within five years (ripe-807 section 3.2). ripe-807 also allows non-permanent transfers, where the original holder takes responsibility back when the resource returns (section 2.1), but a temporary transfer moves the registration and a lease does not. IPv4 and 16-bit ASNs received by transfer cannot be transferred again for 24 months (ripe-807 section 2.2.1).

ARIN (North America). The NRPM contains no leasing rule. ARIN's stated position is that leasing "can be done if the addresses have been legitimately obtained and subsequently become unused", that a lease "does not grant permanent registration rights for the addresses to the lessee", and that "address space leased without providing Internet services cannot be used for justification" on the waiting list or in transfers (ARIN blog, 23 February 2023). A source cannot transfer IPv4 out if it received IPv4 from ARIN in the previous 12 months (NRPM 8.3), and recipients still pass a needs test: blocks larger than a /24 need 50% use within 24 months (NRPM 8.5.5).

APNIC (Asia-Pacific). APNIC-127 section 3.1.3 (version of 20 February 2025) ties delegations to connectivity: "LIRs must only delegate addresses to customers who will be using those addresses in relation to network connectivity services provided by the LIR", and LIRs are expected to contract that "the end-user will hold the addresses only for so long as the end-user remains a customer of that LIR". A proposal to state that leasing is not acceptable, prop-148, did not reach consensus at APNIC 56 and was abandoned on 14 September 2023. A lease without a connectivity service therefore has no policy basis in the region, and leases there are bundled with a service the LIR provides.

LACNIC (Latin America and Caribbean). LACNIC's Policy Manual prohibited sub-assigning IPv4 to third parties outside the recipient's own infrastructure, so leasing LACNIC space was not recognised use. Proposal LAC-2025-5, ratified on 24 March 2026, adds section 2.3.2.19, a regulated exception: the space must be used inside the LACNIC region, the recipient must hold an ASN and IPv6 space from LACNIC, the block is at least a /24, the recipient must show 25% use now and a plan for 50% within a year, and every sub-assignment is recorded in the LACNIC WHOIS with the recipient's ASN. Blocks received by transfer or from LACNIC's recovered pool cannot be sub-assigned this way for three years after receipt, and final responsibility for the addresses stays with the LACNIC member. Transfers between LACNIC and other RIRs cover IPv4 only.

AFRINIC (Africa). The Consolidated Policy Manual (version 1.6, 17 November 2020) section 5.4.6.2 reads: "AFRINIC resources are for AFRINIC service region and any use outside the region should be solely in support of connectivity back to the AFRINIC region." A lessee outside Africa therefore has no policy basis for using AFRINIC space. No transfer to or from AFRINIC is possible: the other RIRs list it as having no compatible transfer policy.

PA, PI and what can be leased in the RIPE region

Of the space the RIPE NCC allocates and assigns, only PA can be leased out; legacy resources sit outside these policies (ripe-639, section 1.2). An LIR's allocation is PA: it assigns or sub-allocates from it to downstream networks, and if the downstream network changes provider "the address space assigned or sub-allocated by the previous service provider must be returned and the network renumbered" (ripe-826 section 7.0). The policy also prescribes the warning every PA End User must receive: "Assignment of this IP space is valid as long as the criteria for the original assignment are met and only for the duration of the service agreement between yourself and us." For sub-allocations, section 5.3 recommends contracts that bind the downstream operator to RIPE policies.

PI space is different. The End User contract required by ripe-637 forbids sub-assignment of the resource, and the IPv6 policy states that "the PI assignment cannot be further sub-assigned to other organisations" (ripe-738 section 7). Under ripe-637 the resources also return by default when the holder is unreachable or the annual fee goes unpaid. A holder that leases out a PI block breaches its End User contract; leased RIPE NCC-issued addresses are always the lessor's PA space. The two types are compared in PI vs PA Resources: Key Differences.

Governing Law and Jurisdiction

An IP lease agreement names its governing law and forum. Lessors usually pick their own jurisdiction, lessees prefer a forum where they can enforce locally, and international deals sometimes settle on a neutral seat. The RIPE NCC's own agreements with its members are governed by the laws of the Netherlands (ripe-812, article 11.1): the lease can choose another law, the registration behind it cannot.

Three sets of rules sit outside the contract. Sanctions: the RIPE NCC checks every signing party and authorised representative of its members and of sponsored End Users against Dutch and EU sanctions lists before registration and again on administrative changes (ripe-863, section 3.1), and EU sanctions regulations bind an EU-based lessor directly in its own contracts. Data protection: when the lessee's contacts published in the RIPE Database are natural persons, EU data protection law applies to that data. Tax: VAT, reverse charge and withholding are covered in Tax Implications of IP Resource Leasing.

Key Contract Clauses

Parties and Identification

Clear identification of contracting parties:

Lessor Identification:

Full legal name and entity type
Registered business address
Tax identification numbers
RIR membership details and member ID
Contact information for notices

Lessee Identification:

Full legal name and entity type
Registered business address
Tax identification numbers
ASN (Autonomous System Number) if applicable
Contact information for notices

Authorized Representatives:

Names and titles of signing authorities
Proof of authority to bind the organization
Contact details for agreement administration

IP Address Specifications

Precise definition of leased resources:

Address Block Details:

inetnum:        192.0.2.0 - 192.0.2.255
netname:        LESSEE-NET
status:         ASSIGNED PA
org:            ORG-LESSEE1-RIPE
mnt-by:         LESSOR-MNT

192.0.2.0/24 is the RFC 5737 documentation range; the status line is what tells the registry, and a court, that the block is a PA assignment out of the lessor's allocation.

Documentation to attach:

CIDR notation and exact address ranges
RIR registry and registration details
WHOIS database information
Historical usage information
Current blacklist status
Geolocation database entries

Lease Term and Duration

Clearly defined temporal scope:

Term Definition:

Start Date: Specific date lease commences (often upon payment)
End Date: Specific date lease terminates
Initial Term: Primary lease period (e.g., 12 months)
Total Term: Including any automatic renewals

Renewal Provisions:

Automatic Renewal: Whether lease auto-renews unless terminated
Renewal Terms: Duration of renewal periods
Notice Requirements: Advance notice needed to prevent renewal (typically 30-90 days)
Price Adjustments: How pricing changes upon renewal

Early Termination:

Termination for Cause: Conditions permitting immediate termination
Termination for Convenience: Whether either party can terminate early and under what conditions
Notice Periods: Required advance notice (typically 30-90 days)
Early Termination Penalties: Fees for breaking lease early
Refund Provisions: Whether prepaid amounts are refunded

Example Clause:

Term: This Agreement commences on January 1, 2026, and continues for
an initial term of twelve (12) months, ending on December 31, 2026.
The Agreement shall automatically renew for successive twelve (12)
month periods unless either party provides written notice of
non-renewal at least sixty (60) days prior to the end of the
then-current term.

Payment Terms

Financial provisions:

Pricing Structure:

Per-IP pricing or total block pricing
Payment frequency (monthly, quarterly, annually)
Pricing for initial term vs. renewals
Volume discounts if applicable
Currency and exchange rate provisions

Payment Mechanics:

Accepted payment methods
Payment due dates
Invoicing procedures
Late payment penalties and grace periods
Interest on overdue amounts

Price Adjustment Mechanisms:

Fixed pricing for term duration
Annual escalation clauses (e.g., CPI-indexed)
Market-based adjustment provisions
Caps on price increases

Example Payment Clause:

Pricing: Lessee shall pay Lessor $0.35 per IP address per month,
totaling $89.60 monthly for the 256 address /24 block. Payment is
due on the first day of each month. Late payments incur 1.5% monthly
interest. Prices are fixed for the initial term and may increase up
to 5% annually upon renewal.

For reference, lease deals on the IPXO platform averaged $0.35 per IP per month over the six months to September 2026 (platform data, 25 September 2026).

Usage Rights and Restrictions

Define permitted and prohibited uses:

Permitted Uses:

General internet connectivity and services
Specific business purposes (hosting, ISP services, enterprise networking)
Geographic usage areas
BGP announcement rights
DNS configuration rights

Prohibited Uses:

Spam transmission or bulk unsolicited email
Malware distribution or hosting
Illegal content or activities
DDoS attacks or participation in botnets
Cryptocurrency mining (if restricted)
Adult content (if restricted)
Activities violating RIR policies

Sublease and Transfer Restrictions:

Prohibition or permission of subleasing to third parties
Requirements for lessor approval if subleasing permitted
Restrictions on assigning lease agreement to another party
Conditions under which transfers are allowed
In the RIPE region an ASSIGNED PA block cannot be assigned on by the lessee; a lessee that serves its own customers needs a SUB-ALLOCATED PA registration from the lessor (ripe-826 sections 5.3 and 7.0)

Acceptable Use Policy Reference:

Usage Restrictions: Lessee shall use the leased IP addresses solely
for lawful business purposes in accordance with Lessor's Acceptable
Use Policy (attached as Exhibit A) and applicable RIR policies.
Lessee shall not: (a) transmit spam or unsolicited bulk email;
(b) distribute malware; (c) engage in illegal activities; (d) violate
intellectual property rights; or (e) sublease addresses without
Lessor's prior written consent.

Responsibilities and Obligations

Define what each party must do:

Lessor Obligations:

Maintain proper RIR registration of addresses
Deliver addresses that are not blacklisted at lease start
Provide Letter of Authorization (LOA) for BGP announcements
Create a ROA authorising the lessee's ASN and a route object for the prefix, and withdraw both when the lease ends (an announcement without a ROA is RPKI "not found"; a leftover ROA for the previous lessee makes the new one "invalid"); check the result with the RPKI checker
Update RIR databases with lessee information
Keep its LIR account in good standing: when a member is closed, the RIPE NCC deregisters its Internet number resources (ripe-858), and a PA assignment cannot outlive the allocation it sits in
Provide technical support as specified
Handle RIR communications and compliance
Respond to abuse reports in coordination with lessee

Lessee Obligations:

Pay all fees promptly
Use addresses in compliance with agreement and RIR policies
Maintain address reputation and prevent abuse
Respond promptly to abuse complaints
Configure proper reverse DNS
Implement security best practices
Provide usage information if required
Return addresses properly upon termination
Maintain insurance if required

Mutual Obligations:

Forward abuse reports and registry correspondence within the agreed time
Cooperate on RIR compliance matters
Maintain confidentiality of agreement terms
Provide timely notice of material issues

Reputation and Blacklist Provisions

Blacklist status decides whether the addresses are usable for hosting and web traffic.

Initial Reputation Guarantee:

Lessor represents addresses are not blacklisted at lease start
Specific blacklists checked (Spamhaus, Barracuda and similar; SORBS closed in June 2024)
Historical usage disclosure requirements
Clean reputation certification

Ongoing Reputation Responsibilities:

Lessee's Duty: Maintain clean reputation through proper use
Monitoring: Who conducts ongoing blacklist monitoring
Abuse Response: Procedures for handling abuse complaints
Security Measures: Required security implementations

Blacklist Remediation:

Pre-existing Blacklisting: Lessor's obligation to provide clean addresses or replacements
Blacklisting from Lessee's Use: Lessee's obligation to delist or accept replacement
Replacement Procedures: Process and timeline for obtaining replacement addresses
Delisting Assistance: Support lessor provides for delisting efforts

Example Blacklist Clause:

Reputation: Lessor represents that the leased IP addresses are not
listed on major blacklists (including but not limited to Spamhaus
ZEN and Barracuda) as of the lease commencement date. If
addresses become blacklisted due to prior usage, Lessor shall provide
replacement addresses within 48 hours. If blacklisting results from
Lessee's activities, Lessee shall undertake delisting efforts, and
Lessor may provide replacement addresses at Lessee's expense.

RIR Compliance and Registration

Registration Requirements:

Lessor maintains primary registration with RIR
Lessor updates RIR database to reflect lessee as user/operator
Lessee contact information added to WHOIS
Proper assignment notation in RIR database
Lease relationship documented in RIR records (where permitted)

Policy Compliance:

Both parties agree to comply with applicable RIR policies
Lessee acknowledges RIR policies may affect lease
Procedure for adapting to RIR policy changes
Representation that lessor is in good standing with RIR

Third-Party Beneficiary Considerations:

RIRs are not parties to lease agreements
RIRs may have enforcement rights under their policies
Lessees subject to RIR policies even without direct membership

Example RIR Compliance Clause:

RIR Compliance: Both parties shall comply with all applicable policies
of the RIPE NCC. Lessor shall maintain its LIR account in good
standing, register the addresses to Lessee as an ASSIGNED PA inetnum,
and publish a ROA authorising Lessee's AS number for the leased prefix
within the term and revoke it on termination. Lessee acknowledges the
ripe-826 warning: the assignment is valid only for the duration of
this Agreement. In the event of RIR policy changes materially
affecting this Agreement, parties shall negotiate in good faith to
adapt terms accordingly or may terminate the Agreement with 30 days'
notice.

Liability and Indemnification

Managing legal risk:

Limitation of Liability:

Caps on total liability (e.g., fees paid in prior 12 months)
Exclusion of consequential, indirect, and incidental damages
Carve-outs for unlimited liability (fraud, willful misconduct, indemnification obligations)

Lessor Liability Limitations:

Limitation: Except for breach of confidentiality, indemnification
obligations, or willful misconduct, Lessor's total liability shall
not exceed the fees paid by Lessee in the twelve (12) months preceding
the claim. Lessor shall not be liable for indirect, consequential, or
incidental damages including lost profits.

Indemnification Provisions:

Lessee Indemnifies Lessor:

For claims arising from lessee's use of addresses
For abuse, illegal activity, or policy violations by lessee
For third-party claims related to lessee's services
For breaches of usage restrictions

Lessor Indemnifies Lessee:

For claims that lessor lacks rights to lease the addresses
For pre-existing legal issues with the addresses
For lessor's breach of RIR policies
For lessor's misrepresentations about address status

Mutual Indemnification Procedures:

Prompt notice of claims
Control of defense
Cooperation requirements
Settlement approval rights

Service Levels and Support

Define expected service quality:

Technical Support:

Support availability (business hours, 24/7, etc.)
Response time commitments
Support channels (email, phone, ticket system)
Escalation procedures

Service Level Agreements (SLAs):

Uptime commitments for routing/connectivity
Maximum downtime per month
Credits or remedies for SLA breaches
Exclusions from SLA (force majeure, lessee-caused issues)

BGP and Routing Support:

Assistance with BGP configuration
Letter of Authorization (LOA) provision
Routing troubleshooting
Route propagation monitoring

Dispute Resolution

Procedures for handling conflicts:

Negotiation and Escalation:

Good faith negotiation as first step
Escalation to senior management
Defined timelines (e.g., 30 days for negotiation)

Mediation:

Non-binding mediation before arbitration/litigation
Selection of mediator
Cost sharing
Mediation location/procedure

Arbitration vs. Litigation:

Arbitration Advantages: Private, and usually faster
Litigation Advantages: Appeal rights, public precedent, full discovery
Many agreements specify binding arbitration (e.g., AAA, JAMS)

Example Dispute Resolution Clause:

Disputes: Any dispute shall first be addressed through good faith
negotiation between senior executives. If not resolved within 30 days,
disputes shall be submitted to binding arbitration under the rules of
the American Arbitration Association, conducted in New York, New York.
Each party shall bear its own costs, with arbitrator fees split equally.

The clause above is a US template. For a lease between EU companies, replace the AAA and New York with the courts of the lessor's seat or a European arbitration body.

Termination and Transition

End-of-lease procedures:

Termination Events:

Expiration of term
Breach of material terms
Bankruptcy or insolvency
Force majeure events
Mutual agreement

Notice Requirements:

Written notice required for termination
Delivery methods (email, certified mail)
Effective date of termination

Transition Procedures:

Lessee ceases BGP announcements by specified date
RIR database updates coordinated
DNS changes implemented
Final accounting and payment
Return of any lessor property or information

Post-Termination Obligations:

Continuing confidentiality obligations
Survival of indemnification provisions
Final payment obligations
Cooperation with transition

Special Considerations

APNIC Region Leasing

Given APNIC's connectivity rule, a lease in the region needs its own structure:

Connectivity Service Model:

Structure lease with bundled connectivity services
Use the addresses for "network connectivity services"
Document the service relationship thoroughly
Avoid pure investment/leasing characterization

Risk Disclosure:

Lessees should understand APNIC's stricter policies
APNIC-127 section 3.1.3 gives the delegation no basis once the connectivity service ends: build the exit into the contract
Additional compliance documentation may be required

Multi-Region Leasing

Leasing addresses registered in different RIR regions:

Complexity Factors:

Different RIR policies apply
Multiple legal jurisdictions potentially involved
Varying geolocation accuracy
Different enforcement environments

Contract Provisions:

Specify which RIR region's addresses
Address different compliance requirements
Account for regional pricing differences
Consider separate agreements per region vs. unified agreement

IPv6 leases

An IPv6 lease is a PA assignment like its IPv4 counterpart, with two differences. The lessor LIR assigns a /48 or larger from its own allocation (ripe-738 sections 2.6 and 5.4), so the block returns to the lessor when the lease ends and cannot follow the lessee to another provider; the assignment is "not to be sub-assigned to other parties" (section 2.6). Blacklist clauses matter less. ROA and reverse DNS clauses matter more: the RPKI certificate and the reverse zone of the allocation belong to the lessor, so ROA creation and reverse delegation are lessor obligations. When the block must stay registered to the lessee's organisation, the alternative is an IPv6 PI assignment (/48 minimum, ripe-738 section 7.1) under a sponsoring LIR contract. The operational side is in IPv6 Leasing Benefits for ISPs.

Lease-to-Own Arrangements

Combining leasing with purchase option:

Key Terms:

Purchase option price (fixed or formula-based)
Percentage of lease payments credited toward purchase
Exercise period for purchase option
Transfer procedures upon exercise
Acceleration of payments if purchased early

Example Provision:

Purchase Option: Lessee may purchase the leased IP addresses at any
time during the lease term at a price of $24 per IP address, with 50%
of rent paid in the 12 months preceding purchase credited toward the
purchase price. Upon exercise, parties shall execute an IPv4 Transfer
Agreement and complete the applicable RIR transfer process.

For scale, /22 to /24 blocks sold for about $23.50 per address in August 2026 according to broker IPv4.Global (monthly averages, prices at agreement date, online and private sales mixed); the full comparison is in IPv4 Leasing vs Purchasing (2026): Cost Analysis and Break-Even. In the RIPE region the purchase is a transfer under ripe-807: the RIPE NCC charges nothing and completes most transfers within one or two business days, an allocation can only be transferred to a RIPE NCC member (section 2.0), and the buyer cannot transfer the block again for 24 months (section 2.2.1).

Best Practices

For Lessees

Due Diligence:

Verify lessor's RIR membership status
Check lessor's reputation and references
Thoroughly inspect address reputation across multiple blacklists
Review historical usage if available
Verify proper RIR registration
Have legal counsel review agreement

Negotiation Priorities:

Address replacement provisions for blacklisting
Reasonable usage restrictions
Price protection for renewals
Flexible termination provisions
Adequate support commitments

Documentation:

Maintain complete records of agreement and amendments
Document all communications with lessor
Keep blacklist check results
Preserve abuse reports and responses
Track payment history

For Lessors

Protect Your Assets:

Maintain clear registration and allocation documentation
Keep RIR registration current
Document address history and usage
Monitor for compliance with lease terms
Include provisions protecting RIR relationship

Risk Management:

Thorough lessee vetting and approval process
Strong usage restrictions and monitoring
Quick termination rights for severe breaches
Insurance requirements for large leases
Indemnification provisions protecting against lessee misuse

Operational Practices:

Standardized lease agreement template
Clear procedures for lease administration
Regular monitoring of leased address usage
Prompt response to abuse reports
Systematic documentation of all leases

Common Pitfalls to Avoid

Inadequate Address Verification

Leasing a block without checking its history is the most expensive mistake a lessee can make. Addresses on a major blacklist are unusable for hosting or web traffic, and delisting or replacement takes time the lessee's customers will not wait for. Before signing, check the block against the main blacklists, look up its registration and routing history, verify the geolocation databases, and test that it is routable from the lessee's ASN.

Unclear Usage Restrictions

Vague wording on permitted use produces disputes over whether a given activity is allowed, and terminations that one side calls a breach and the other a surprise. Define prohibited activities in specific terms, give examples, and attach a written acceptable use policy as an exhibit. Anything left grey at signing is settled by an addendum, not by e-mail.

Insufficient Termination Protection

A lessee whose block can be withdrawn on short notice carries the migration risk alone: renumbering, emergency address sourcing, lost customers. Negotiate a minimum notice of 60 to 90 days, cure periods for non-material breaches and transition assistance, and keep an alternative address source ready in any case.

Ignoring RIR Policy Changes

Registry policy changes bind the lessor whether or not the contract mentions them: LACNIC's sub-assignment exception of March 2026 and the RIPE Database's removal of password authentication on 4 March 2026 (which changes how the lessee's objects get updated) are recent examples. A contract that says nothing about policy changes leaves both parties arguing about who bears the cost. Write in a renegotiation or termination right for material policy changes, require the lessor to stay compliant, and follow the registry's announcements (RIPE NCC news for the RIPE region, the equivalent channels at ARIN, APNIC, LACNIC and AFRINIC).

Inadequate Liability Protection

Without a liability cap and an indemnity, each party is exposed to the other's conduct: the lessor to the lessee's abuse, the lessee to the lessor's defective title. Cap liability at a multiple of the fees, exclude consequential damages, allocate third-party claims through mutual indemnities, and have counsel review the result.

How Via-Registry leases addresses

We lease IPv6 from our own RIPE NCC allocations: a /48 costs €40 per year and a /44 €80 per year (as of September 2026), larger sizes on request. This is provider-aggregatable (PA) space leased from our allocation, so it returns to the pool when the lease ends, the same PA rule that ripe-826 section 7.0 sets out for IPv4. You need an ASN to announce it. For an ASN you already hold, the block is provisioned automatically after payment: inet6num, then route6 object and ROA, and the LOA is generated in the dashboard. If the block must stay registered to your organisation when you change provider, IPv6 PI is the portable option.

See leased IPv6 prices or send an IPv4 lease request.

Frequently asked questions

Is IP address leasing legal?

No RIR regulates the lease contract itself; each regulates who may be registered as the user of a block and on what conditions. In the RIPE region the leased block is registered as a PA assignment under a contract (ripe-826 section 7.0). ARIN allows leasing of legitimately obtained space but counts leased-out space as unused, APNIC ties delegations to a connectivity service, LACNIC allows IPv4 sub-assignment only under section 2.3.2.19 since March 2026, and AFRINIC requires use inside its region. What no registry allows is leasing out PI space.

Can I lease out my PI addresses?

No. The End User contract every PI holder signs under ripe-637 forbids sub-assignment, and the IPv6 policy says the PI assignment cannot be further sub-assigned to other organisations (ripe-738 section 7). Leased RIPE NCC-issued space is always the lessor's PA space. A PI holder that no longer needs its block keeps it under a sponsoring LIR, transfers it under ripe-807 or returns it.

Who is responsible for abuse from leased IP addresses?

Operationally the lessee, contractually whatever the lease says, and towards the registry the lessor. The lessor stays the registered holder and its organisation object must carry a validated abuse-c: contact (ripe-705), so abuse reports reach the lessor first. A lease worth signing obliges the lessee to answer abuse complaints within a set time and lets the lessor suspend the announcement for serious abuse.

Do I own the IP addresses I lease or buy?

In neither case. The RIPE NCC Standard Service Agreement states that registration "does not constitute property" and confers no rights of ownership (ripe-812, article 10.2). A buyer acquires the right to the registration, which is transferable under ripe-807 and can be seized by a Dutch court order; a lessee acquires a contractual right to use the block for the term. Both depend on the registration staying valid under RIPE policies.

Summary

A lease contract has to do what the registry never will for the lessee: fix the term, the price and the exit. In the RIPE region, check that the space is the lessor's PA (PI cannot be leased), that the contract carries the ripe-826 warning, and who creates and revokes the ROA. Outside it, read the registry's own rule first: ARIN treats leased-out space as unused, APNIC ties delegations to connectivity, LACNIC allows IPv4 sub-assignment only under section 2.3.2.19, and AFRINIC requires in-region use. For the commercial side, see How IP Leasing Works: A Practical Guide for Network Operators.