LARUS adds continuity controls to first-party IPv4 leasing

LARUS has expanded its first-party IPv4 leasing service with Continuity Assurance, a framework aimed at enterprise networks that need more than raw address capacity. The new tiers add support for routing, reputation, renewals, and escalation handling for production workloads that depend on stable IPv4 access.

Why it matters: - Enterprise networks often depend on IPv4 blocks that are hard to replace without operational disruption. - LARUS is positioning IPv4 leasing as a continuity service, not just a capacity purchase. - The framework is meant to reduce risks tied to routing, reputation, support, and renewal failures.

What happened: - LARUS enhanced its first-party IPv4 leasing service with Continuity Assurance on July 29, 2026. - The offering is aimed at internet service providers, cloud infrastructure companies, hosting providers, telecommunications operators, data centers, managed service providers, and enterprise networks. - LARUS provides IPv4 address space directly from its controlled first-party address pool. - The company says the model reduces reliance on reseller chains and gives customers a clearer relationship with the address source and the provider responsible for commercial terms, routing coordination, renewals, and operational support.

The details: - Continuity Assurance is built around four service levels: IPv4 Capacity Only, Continuity Production, Continuity Enterprise, and Continuity Critical. - IPv4 Capacity Only is designed for non-critical, price-sensitive, or self-managed deployments. - Continuity Production adds reverse DNS support, IP reputation and blacklist monitoring, abuse and geolocation workflows, and a defined response level. - Continuity Enterprise adds priority operating controls, RPKI and ROA alignment, priority geolocation correction, routine abuse administration, and faster support response. - Continuity Critical is designed for networks where renumbering is not an acceptable outcome. - Continuity Critical includes guaranteed renewal, named operational handling, priority geolocation support, P1 response handling, and 24-hour escalation availability. - Before confirming an allocation, LARUS reviews deployment profile, requested block size, ASN context, routing requirements, intended use, timing, and continuity needs. - The operational process can include requirement assessment, allocation coordination, routing authorization, RPKI and ROA readiness, reverse DNS setup, reputation monitoring, abuse-report handling, geolocation correction, renewal coordination, and package-based escalation. - The exact controls depend on the package selected. - LARUS says the structure lets customers avoid paying for controls they do not need in non-critical environments. - The company also says the framework is meant to provide stronger protection where IPv4 disruption would have a material business impact.

Between the lines: - The launch reflects growing pressure on network operators to manage IPv4 as an operational risk, not just an inventory item. - First-party supply can reduce uncertainty for customers that need a direct line for troubleshooting and renewals. - The four-tier model also suggests LARUS is trying to match service intensity to workload criticality instead of selling a one-size-fits-all lease.

What’s next: - Organizations can provide LARUS with block size, deployment profile, ASN context, intended use, timing, and continuity requirements. - LARUS will assess the request and recommend a leasing structure based on deployment and risk profile. - Customers can review IPv4 availability, pricing, and Continuity Assurance options at larus.net or contact sales@larus.net.

The bottom line: - LARUS is betting that enterprise buyers will pay for IPv4 leasing structures that prioritize renewal certainty, operational support, and lower disruption risk over price alone.