This page outlines the technical, operational and commercial details of LARUS, a direct IPv4 lessor that sells address capacity together with a choice of operational service tiers it calls Continuity plans.
Looking for the best IP providers? LARUS leases from its own pool rather than running a marketplace, and it separates the address capacity from the operational handling and renewal treatment that sit on top of it. The tier you choose decides how rDNS, reputation and geolocation requests are handled, how long RPKI coverage runs and what happens at renewal. Cloud BYOIP is a readiness check, not a documented integration. LARUS names AWS, Google Cloud and OVHcloud in an optional readiness validation, which is not the same as the cloud accepting a given block.
This listing was compiled from LARUS's own published pages. It is editorially researched rather than vendor-confirmed, and the company's descriptions of its own supply model have not been independently audited, so fields it does not publish are marked as not published rather than estimated.
Not published. A registered address and jurisdiction were not verified from corporate records.
Supply Model
Self-described first-party lessor supplying from its own IPv4 pool. That describes the marketed arrangement, not an audit of title or authority over every block.
RIR Standing
Not verified. Offering registry-management services does not by itself establish RIR membership.
ARIN Facilitator Status
No. LARUS does not appear on ARIN's published Qualified Facilitator list (checked 29 September 2026).
Sales Contact
sales@larus.net, info@larus.net, +1 715 449 8968
Service Capabilities
Capability
Details
Offer Type
Lease. LARUS also invites holders to sell address space to it. Buying address space from LARUS is not a published offering, and no lease-out marketplace for third-party holders is documented for this product.
Lease Configurations
Capacity is chosen in /24 blocks with a term and one of four plans: IPv4 Capacity Only, Continuity Production, Continuity Enterprise and Continuity Critical. Each Continuity plan is priced per IP per month on top of the base lease.
Supported RIRs
Not published as a coverage list. Confirm the RIR, transfer status and any regional restrictions of the offered prefix in the quote.
IPv4 / IPv6
IPv4. IPv6 transition services are promoted separately, but no IPv6 leasing catalogue is published.
BYOIP Support
Resource side, with an optional cloud readiness validation that names AWS, Google Cloud and OVHcloud. No other cloud is named, and the check does not replace the cloud's own validation of the block.
Included Management
Routing validity and RPKI ROA are coordinated with LARUS on every plan. Production and higher add rDNS, reputation and geolocation handling. Enterprise adds daily registry follow-up and priority handling.
Portal and API
LARUS describes console and API control of allocations. Endpoint specifications, authentication and supported operations are not published.
Technical Requirements
Requirement
Details
Minimum Prefix Size
/24. The configurator offers 1 to 512 /24 blocks; that range is a form limit rather than a published maximum.
Maximum Prefix Size
Not published.
Provisioning Time
Not published. The order flow ends with coordinating routing and address setup with the LARUS team.
Announcement
Intended for operator deployments on the customer's own network. Agree the origin ASN and routing path for each order.
RPKI / ROA
Coordinated with LARUS. Coverage runs through the paid period on Capacity Only and Production, through the contract term on Enterprise, and through the contract term plus renewal rollover on Critical.
LOA
Not published. Confirm the form, issuer and permitted ASN per order.
IRR / WHOIS
Not published. Customer control over route objects and WHOIS fields, and the turnaround for changes, should be agreed before ordering.
Support Response
Published targets: Production within 24 hours, Enterprise within 4 hours, Critical P1 within 1 hour with 24x7 escalation. Capacity Only is self-operated. These are response targets, not provisioning or resolution times.
Cost and Limitations
Item
Details
Fees / Pricing
Not published as a fixed rate. The price combines the base lease with the chosen Continuity add-on and is shown after configuring quantity and term.
Renewal
Varies by plan. Capacity Only has no stated renewal commitment. Production has a 90-day renewal review, Enterprise a right of first refusal, and Critical an advertised Guaranteed Renewal that depends on renewing on time.
Abuse Fines
Standard fees apply on Capacity Only and Production; waived on Enterprise and Critical. A waived fine is not permission for prohibited use.
Minimum Term
Not published. The term is selected in the configurator.
Billing Cycle
Not published.
Scope Limitation
Cloud readiness is an optional pre-check for three named clouds. Organisations that need documented cloud BYOIP programme support should compare providers whose listing shows it.
Not Published
Contracting entity and jurisdiction, RIR coverage, KYC requirements, deposits, notice periods, early-termination charges, renewal pricing, refunds, LOA process and API documentation. Request them directly.
Related Resources
LARUS website
LARUS leasing and Continuity plan comparison
LARUS infrastructure operations
LARUS data-centre leasing guidance and cloud readiness
BYOIP, or Bring Your Own IP, is a service that allows you to use your own IP addresses with cloud providers and hosting services. This gives you more control over your IP reputation and allows you to maintain your existing IP addresses when switching providers.
BYOIP offers several benefits including maintaining your IP reputation, reducing costs by avoiding IP address purchases, and providing more control over your network infrastructure. It's particularly useful for businesses that need to maintain consistent IP addresses across multiple service providers.
BYOIP is available to organizations that own registered IP address blocks. This typically includes businesses, hosting providers, and organizations that have obtained IP addresses from Regional Internet Registries (RIRs) like ARIN, RIPE, or APNIC.
Yes, you typically need to own or have authority over the IP address blocks you want to use. This usually means having registered IP addresses through a Regional Internet Registry (RIR) or having proper authorization from the IP address owner.
Proof of IP ownership typically includes documentation such as ROA (Route Origin Authorization) records, LOA (Letter of Authorization) documents, or registration records from RIR databases. The specific requirements vary by provider.
Yes, BYOIP is secure when properly implemented. Providers use various verification methods including ROA records, certificates, and registration checks to ensure only authorized IP addresses are used. However, it's important to follow security best practices and maintain proper IP address management.
The setup time varies by provider and depends on factors such as prefix validation, ROA creation, and verification processes. Typically, it can take anywhere from a few hours to several days, depending on the provider's requirements and verification process.
Yes, many providers support BYOIP across multiple geographic regions. However, the specific regions and locations supported vary by provider. Some providers offer global BYOIP support, while others may be limited to specific regions.
When you stop using BYOIP with a provider, your IP addresses are typically returned to your control. The provider will stop advertising your IP prefixes, and you can use them with another provider or return them to your normal routing. It's important to coordinate the transition to avoid service disruptions.
Cookies and analytics
We use optional analytics cookies to understand how BYOIP.info is used. You can accept or reject them. Read our Cookie Policy for details.