China UnicomFirst-party IPv4 leasing · Continuity provider
Lease IPv4 directly from the provider responsible for continuity.
What does LARUS IPv4 leasing provide?
IPv4 leasing helps organizations add IPv4 capacity without buying address blocks outright. LARUS provides first-party IPv4 leasing from its own address pool and pairs it with continuity controls for renewal, routing validity, rDNS, RPKI/ROA readiness, reputation, abuse workflow, geolocation and support response.
Direct sourceLease from LARUS controlled address
space, not a reseller chain.
Production controlsMap the lease to routing,
renewal, rDNS, reputation, abuse, and response.
4 packagesCapacity Only, Production, Enterprise,
and Critical align controls to failure cost.
Operator adoptionCustomer logos show use by
carriers, platforms, ISPs, and infrastructure teams.
Trusted by operators that buy IPv4 for production continuity.
Customers use LARUS when IPv4 availability, renewal certainty, routing stability, and response process affect production service.
China Unicom
China Telecom
China Mobile International
NetEase
According
PTCL
Nayatel
Unitel
ReadySpace
IN800
Spectra
Pure Fibre
IENTC
Cambo
Thinkdream
SGGS
Telconet
Conversant
First-party structure
First-party IPv4 leasing makes accountability easier to audit.
A transaction-only intermediary optimizes for the handoff. First-party leasing from LARUS keeps pool source, contract accountability, and continuity operations around one provider.
Intermediary handoff
More handoffs
Each intermediary adds dependency, ambiguity, and delay when production operations need a clear response path.
LARUS
Direct accountability
Lease IPv4 from the first-party address source and upgrade continuity controls as the workload becomes more critical.
Continuity Assurance packages
Choose the IPv4 leasing package by operational exposure.
Use current LARUS IPv4 pricing as the base. Add continuity controls when the workload needs rDNS, abuse administration, geolocation priority, support SLA, RPKI term, or renewal certainty.
IPv4 Capacity Only
For non-critical capacity
Current IPv4 pricing Continuity add-on:
+$0.00/IP/mo
- Best-effort operations
- RPKI/ROA to paid-through date
- $40 valid abuse incident fee
- No Guaranteed Renewal
Continuity Production
Default for live workloads
Base + $0.25/IP/mo rDNS, reputation, abuse workflow,
SLA
- rDNS included
- Reputation and blacklist monitoring
- Abuse and geolocation workflow
- 1 business day support SLA
Continuity Enterprise
For audit and procurement
Base + $0.50/IP/mo Priority operating controls
- RPKI/ROA to contract end date
- Priority geolocation correction
- Routine abuse admin fee included
- 4 business hours support SLA
Continuity Critical
When renumbering is unacceptable
Base + $1.00/IP/mo Guaranteed Renewal package
- Guaranteed Renewal
- Named legal / registry ops contact
- P1 1 hour + 24×7 escalation
- Highest-priority geolocation handling
Configure
Enter the number of /24 blocks.
Use current LARUS IPv4 pricing as the base. The continuity add-on shows the incremental cost per IP/month.
Selected
quantity
256 IPs
Continuity is the product
The risk is not getting IPv4. The risk is losing stable use of it.
For an operator, IPv4 failure shows up as renumbering, broken routes, abuse interruption, wrong geolocation, reputation damage, support delay, and renewal uncertainty. LARUS frames the lease around keeping the block usable, not just assigning address space.
- ✓Keep registry-facing complexity upstream with a specialist first-party IP leasing provider.
- ✓Reduce intermediary failure points by leasing IPv4 address space from LARUS' own pool.
- ✓Choose a continuity level based on outage exposure, not only on address count.
Direct holding can feel safer while pushing the fragile layer into your own operating company.
LARUS reframes IPv4 leasing as a continuity structure: first-party address supply, fewer intermediary dependencies, operational controls by plan, and a commercial model built around keeping production IP blocks stable.
Ordinary direct holding
Thin recourse is the weak point.
- Registry-side policy, audit, payment, termination, and revocation processes remain upstream of the operator.
- The operator's practical downside is service disruption, renumbering, reputation loss, churn, and contractual exposure.
- The public contract remedy can be small compared with the operational failure path.
Cloud Innovation judgment
The LARUS continuity position is not ordinary.
The Supreme Court of Mauritius order dated 11 June 2025 ordered rectification of AFRINIC's register of members to add Cloud Innovation Ltd, directed the Registrar of Companies to make the proper entries, and recorded the undertaking to rectify AFRINIC records within 15 days. The published PDF is available for legal review.
- It moves the position beyond a standard external customer relationship.
- It ties continuity to formal member-record status inside an actual RIR.
- For buyers, that changes the risk comparison between ordinary direct holding and first-party leasing from LARUS.
RIR contract risk
The five RIR frameworks show the same downside asymmetry.
Direct holding can move registry-layer contract risk into the buyer's operating company. The public RIR agreements read like service or membership frameworks: policy changes, audit or compliance leverage, suspension or revocation paths, and liability caps that can be far smaller than the cost of renumbering a live network.
ARIN
Policy stack plus limited recovery
Holder rights sit inside ARIN policy and order-compliance machinery; public contract exposure can be capped far below operator-side network loss.
RIPE NCC
Membership procedure risk
Membership terms, amendments by resolution, liability limits, and deregistration cooperation leave the operator inside a procedural framework.
APNIC
Annual renewal dependency
Renewal can accept then-current terms; delegated-resource revocation can require the member to cease using the resources.
AFRINIC
Best-effort control point
Public materials describe a resource-member RSA with best-effort service, limited liability, and revocation pathways on termination.
LACNIC
Adhesion and revocation
The public RSA is an adhesion agreement with annual renewal, guideline amendments, and revocation paths after non-renewal, default, or termination.
Commercial meaning: direct registry proximity is not the
same as safety. It can formalize dependency while leaving the real outage, migration,
customer, and legal cost with the operator.
Why the structure matters
Do not internalize registry-layer fragility without a reason.
The decision is where continuity risk should sit: inside the buyer, inside an intermediary chain, or with a provider built to manage the registry and operations layer.
- ✓Capital stays flexible: add IPv4 capacity without a secondary-market structural reset.
- ✓Operations stay focused: the live service team is not turned into the registry-risk team.
- ✓Continuity stays visible: package selection maps directly to failure exposure.
Plan comparison
Each tier buys down a specific IPv4 failure path.
The comparison table shows exactly what changes when the buyer upgrades: abuse fees, RPKI/ROA term, rDNS, geolocation priority, support SLA, and renewal certainty.
| Feature | Capacity Only | Production | Enterprise | Critical |
|---|---|---|---|---|
| Public price | Current IPv4 pricing | Base + $0.25/IP/mo | Base + $0.50/IP/mo | Base + $1.00/IP/mo |
| Tier availability | Any entered /24 quantity | Any entered /24 quantity | Any entered /24 quantity | Any entered /24 quantity |
| Abuse administration | $40 per valid incident | $40 fee remains; first minor event may be reviewed | Routine fee included for compliant customers | Routine fee included for compliant customers |
| RPKI / ROA validity | Paid-through date | Paid-through date | Contract end date | Contract end date + renewal rollover handling |
| rDNS | Not included | Included | Included + batch handling | Included + named ops handling |
| Geolocation service | Standard queue | Monthly batch queue | Priority correction queue | Highest priority + escalation evidence |
| Support ticket SLA | Best effort | 1 business day | 4 business hours | P1 1 hour + 24×7 escalation |
| Renewal | Subject to availability | 90-day renewal review | Renewal priority / right of first refusal | Guaranteed Renewal |
Routing validity
Production IPv4 leasing needs ROA/RPKI validity that matches the operational term the network depends on.
Reputation workflow
Blacklist, abuse, and geolocation operations are continuity controls, not generic support tickets.
Renewal certainty
For networks that cannot renumber, Critical turns renewal risk into the central commercial variable.
Get production IPv4
Move from IPv4 evaluation to a continuity-backed lease.
Start with block size, deployment profile, ASN context, timing, and the package that matches the cost of failure.
FAQ: IPv4 lease and continuity
Common procurement and technical questions about IPv4 leasing.
What is IPv4 leasing?
IPv4 leasing lets a business use IPv4 address space without purchasing address blocks outright. LARUS supports this with first-party IPv4 leasing from its own address pool plus continuity controls for renewal, routing, rDNS, reputation, abuse workflow, geolocation and response.
How much does IPv4 leasing cost?
IPv4 leasing cost depends on the number of /24 blocks, the billing cycle and the continuity package selected. Use the calculator to estimate the continuity add-on while confirming the current base IPv4 price with LARUS.
Should we lease or buy IPv4 addresses?
Leasing can be faster and less capital intensive when the goal is to add IPv4 capacity for production workloads. Buying may fit long-term ownership strategies, while first-party leasing can reduce intermediary risk and make continuity controls easier to manage.
What is a /24 IPv4 block?
A /24 IPv4 block contains 256 IPv4 addresses. Many teams use /24 blocks as a practical planning unit for routing, deployment, pricing and continuity package selection.
Why can leasing from LARUS be safer than holding addresses directly?
Direct holding can put your operating company inside the RIR contract framework. That means payment, audit, policy, termination, and revocation risk sits with the operator while public registry liability can be limited. LARUS moves that registry-facing risk to a specialist first-party lessor.
What is the five-RIR contract risk?
Across ARIN, RIPE NCC, APNIC, AFRINIC, and LACNIC, public agreements show service or membership frameworks with policy amendments, compliance leverage, suspension or revocation pathways, and liability limits that may be much smaller than production renumbering damage.
Why is the Cloud Innovation judgment relevant to continuity?
The published order does not leave the position at an ordinary external customer relationship. It orders rectification of AFRINIC's register of members to add Cloud Innovation Ltd, directs proper company-record entries, and records the undertaking to rectify AFRINIC records within 15 days.
Why does first-party IPv4 leasing matter?
A broker mainly matches transactions. LARUS leases from its own address pool, reducing intermediary layers and giving customers clearer accountability for continuity, renewal, routing, abuse workflow, and operational response.
Which package should production teams start with?
Continuity Production is the recommended starting point for live workloads where routing, rDNS, reputation, abuse workflow, geolocation, and support response influence availability.
When should we choose Critical?
Choose Critical when the same IPv4 block must renew and renumbering is not acceptable. It adds Guaranteed Renewal, named operations handling, highest priority geolocation, P1 1-hour response, and 24x7 escalation.
