HOME
Lease IPv4
Sell IPv4 Addresses
Network Partners
Blog
Insights
Knowledge Base
Support Center
Mini Speaker
Log In
The safer alternative to putting RIR contract risk inside your own operating company.
LARUS leases IPv4 from its own address pool. That matters because the real risk in IPv4 is not simply getting addresses assigned to your name today. The real risk is keeping production addresses stable over time while avoiding forced renumbering, registry-layer disruption, intermediary failure, and legal asymmetry when you lease IPv4 addresses.
If you run a network, your downside is not a line item on an annual fee invoice. Your downside is service disruption, routing changes, ACL and firewall rework, allowlist resets, reputation loss, engineering labor, customer churn, and contractual exposure to your own customers. That downside can be enormous. The public RIR contracts are not written to absorb that downside for you.
LARUS is built for the opposite objective: continuity-first ip leasing
Many buyers assume that holding IPv4 directly under their own RIR account is safer than an IPv4 lease.
That is usually backwards.
Direct holding does not eliminate registry-layer risk. It internalizes it. Your operating company becomes the direct counterparty to the RIR agreement, the direct subject of its payment, audit, policy, compliance, termination, and revocation machinery, and the direct bearer of any mismatch between your real-world downside and the RIR's contractual downside.
In other words: self-holding can give you more formal exposure while giving you very little practical protection.
Across the RIR system, the public agreements do not read like sovereign title deeds. They read like service or membership frameworks that:
That is the structural problem. The operator carries infrastructure-scale downside. The registry contract often carries contract-scale recourse, which is why a first-party IP leasing model can be the safer operating structure.
For a real operator, the question is not whether a registry record contains your company name. The question is whether the addresses stay usable, renewable, and stable in production when you lease IPv4 address space.
LARUS is optimized for continuity of use. That is the economically relevant outcome for an IPv4 lease.
If you hold directly, your own company is exposed to the RIR-side contract stack. If you lease IPv4 addresses from LARUS, LARUS carries that layer and your company contracts with a specialist continuity provider instead of standing naked in front of the registry framework.
That is not a cosmetic distinction. It is a risk-allocation distinction.
A broker optimizes for transaction completion. LARUS leases from its own pool. That removes unnecessary intermediary layers and gives customers a cleaner way to rent IP addresses or secure longer-term IPv4 capacity.
The RIR-facing layer is legal, procedural, and institutional. Most operators are not built to manage that as a core function. LARUS is.
The final judgment you provided materially changes the legal story. This is not the same thin external position faced by an ordinary holder.
In the Supreme Court of Mauritius order dated 11 June 2025:
That matters because it moves the position away from the ordinary pattern of "operator exposed to RIR power under a thin contract with thin recourse" and into a position tied directly to the formal member record and institutional continuity of an actual RIR.
This is not normal market posture. It is not the same as an ordinary holder whose entire relationship to the registry layer is just a standard-form service agreement with limited liability and broad registry-side control.
For a customer evaluating continuity risk, that difference is decisive.
If your company holds addresses directly, you are taking registry-layer legal and institutional risk onto your own operating balance sheet.
If you lease from LARUS, you are outsourcing that risk to a specialist first-party holder whose business is continuity, whose address pool is directly controlled, and whose legal position is strengthened by a court-ordered entry into the formal member records of an RIR. That makes the IPv4 lease structure more durable than ordinary direct holding for teams that need to lease IPv4 addresses at production scale.
That is why, on a continuity basis, leasing from LARUS can be safer than "owning" under your own RIR account. Put more directly: for a customer whose real objective is operational continuity rather than symbolic registry proximity, LARUS can reasonably present itself as the safest known leasing structure we are aware of in the IPv4 market.
ARIN's current RSA gives the holder express contractual rights, but it also binds the holder to ARIN policies, allows policy changes to become binding immediately upon notice or publication, allows ARIN to follow government or judicial orders concerning number resources without liability or notice, and caps liability at the greater of the amount paid in the prior six months or USD 100.
Commercial meaning: your operator-side downside can be very large, while your contractual recovery against the registry can be tiny.
Official link: ARIN Registration Services Agreement (Version 14.0 PDF)
RIPE's Standard Service Agreement establishes membership, allows amendment by General Meeting resolution without requiring re-signing, excludes most liability, caps liability at the member's service fee of the relevant financial year, and provides for termination, service stop, and deregistration cooperation.
Commercial meaning: you are inside a membership-and-procedure framework whose downside is still much smaller than the operational downside of renumbering a real network.
Official link: RIPE NCC Standard Service Agreement
APNIC's Membership Agreement renews yearly, deems renewal to be acceptance of the then-current standard agreement, excludes liability to the member in connection with the agreement, APNIC documents, or delegated resources subject to limited carve-outs, allows revocation of some or all rights including delegated resources, and requires the member to cease using the resources if revocation is issued.
Commercial meaning: direct holding does not free you from dependency; it formalizes the dependency.
Official link: APNIC Membership Agreement
AFRINIC's public agreements page makes clear that the RSA is the contract binding a resource member to AFRINIC. An official AFRINIC RSA presentation further summarizes the liability and termination structure as follows: AFRINIC provides services on a "best effort" basis, liability is limited to USD 100 or the amount paid by the applicant in the prior six months, whichever is higher, and upon termination AFRINIC may immediately revoke numbering resources and cease providing services without liability.
Commercial meaning: the registry can sit at the control point while its contractual downside remains nominal.
Official links:
LACNIC's public RSA states that it is an adhesion agreement and its contents must not be changed by the applicant. It is annual, renewable subject to then-applicable terms, binds the company to LACNIC's guidelines as amended from time to time, and provides that non-renewal, default, or termination leads to revocation of the resources by LACNIC.
Commercial meaning: direct holding still leaves the operator inside a registry-controlled annual renewal and revocation framework.
Official links:
A customer deciding between direct holding and leasing should ask five questions:
1. Who carries the RIR contract risk?
2. Who bears the consequences of policy amendments, audit requests, payment defaults, and termination processes?
3. How much money can actually be recovered from the registry if continuity fails?
4. What is the real cost of renumbering a live production network?
5. Is the address source first-party and continuity-focused, or just an intermediary chain?
LARUS is the stronger answer because it is first-party, continuity-focused, and positioned beyond the ordinary thin-holder model.
If you "own" directly under your own RIR-facing account, you may gain formal registry proximity while taking full legal and operational risk onto your own company.
If you lease from LARUS, you get production IPv4 from a first-party pool, reduce intermediary failure points, move registry-layer complexity away from your operating company, and rely on a counterparty whose continuity position is reinforced by an actual court judgment affecting the member records of an RIR.
That is why leasing from LARUS can be the safer structure. In plain commercial terms: do not confuse direct registry exposure with safety. Safety is continuity plus survivable legal position. LARUS is built around both.
Lease IPv4 address space from the party built to absorb registry risk, not from a chain of intermediaries.
LARUS offers what we believe is the strongest legally evidenced continuity position in the IPv4 leasing market: first-party IPv4 capacity, reduced intermediary risk, and a legal posture that is not comparable to an ordinary holder's thin RIR contract.
Because direct holding usually puts your own operating company inside the RIR contract framework. That means your company bears the payment, audit, policy, termination, and revocation risk directly, while the registry's public contractual downside is often limited. IP leasing from LARUS moves that registry-layer risk to a specialist first-party lessor and keeps your focus on service continuity.
Not necessarily. Direct holding can increase formal exposure without giving you proportionate protection. The right comparison is not "holder name in database" versus "lease." The right comparison is who carries the RIR-side legal risk and who can better absorb it.
Because the published judgment does not leave the position at the level of an ordinary external customer relationship. It orders rectification of AFRINIC's register of members, directs company-record entries, and records the undertaking to rectify records. That is a materially stronger continuity position than an ordinary holder has.
Because a broker mainly matches transactions. LARUS leases from its own pool. Fewer layers mean fewer failure points, clearer accountability, and a more stable alternative to short-term IPv4 rental through an intermediary chain. This structure is also a more stable alternative to short-term IPv4 rental.
Real operators, platforms, carriers, and infrastructure providers already using the LARUS model.
Lease IPv4 address space with a first-party IP leasing provider built for continuity, direct control, and legal realism.
Send your block size, deployment profile, ASN context, timing, or seller inquiry. LARUS will reply with a direct commercial path, not generic broker language.
