InterLIR IP Leasing Overview
This page outlines the technical, operational and commercial details of InterLIR, a Berlin-based IPv4 marketplace where holders lease out and sell address space and business customers lease or buy it.
Looking for the best IP providers? InterLIR is a marketplace rather than a single-inventory lessor: prices and minimum terms are set per offer by the supplying holder, and the platform publishes its own commission schedule separately. It documents the registry side of cloud BYOIP for AWS, Google Cloud, Microsoft Azure and OVHcloud. The cloud-side import itself stays with the customer. InterLIR prepares the route objects, ROA, LOA and WHOIS fields for the leased range, and the customer completes the target cloud's own onboarding.
This listing was compiled from InterLIR's own published pages and from the RIPE NCC member list. It is editorially researched rather than vendor-confirmed, so fields the company does not publish are marked as not published rather than estimated.
Provider Details
The registry membership below was checked against the RIPE NCC's published member list rather than taken from the company's own summary.
| Field | Information |
|---|---|
| Provider Name | InterLIR GmbH |
| Website | interlir.com |
| HQ Country | Germany (Josef-Orlopp-Straße 54, 10365 Berlin). Commercial register HRB 228589 B, Amtsgericht Charlottenburg. |
| Other Entity | The site also lists InterLIR LLC in Dover, Delaware. Check which entity is the counterparty on a given order rather than treating the two as interchangeable. |
| RIR Standing | RIPE NCC member, listed as InterLIR GmbH in the RIPE NCC member list. That is company membership; it does not establish inventory in every region or the status of a particular block. |
| ARIN Facilitator Status | No. InterLIR does not appear on ARIN's published Qualified Facilitator list (checked 29 September 2026). |
| Sales Contact | +49 177 2335293, plus the contact links and customer portal on the website |
| Public Docs | BYOIP assignment guide and a marketplace FAQ |
Service Capabilities
| Capability | Details |
|---|---|
| Offer Type | Buy, sell, lease and lease out. All four are marketplace transaction types. |
| Supply Model | Marketplace. Suppliers must establish ownership of, or authority over, the resources they list. Prices and minimum terms come from the individual offer. |
| Supported RIRs | The BYOIP page describes leased ranges registered with RIPE NCC, ARIN or APNIC. Broader terms refer to all five registries, which is not a promise of inventory or transfer eligibility in each. |
| IPv4 / IPv6 | IPv4 leasing. The price list includes IPv6 /48 registration and IPv6 support services, but an IPv6 leasing inventory is not published. |
| BYOIP Support | Registry side. InterLIR configures route objects, RPKI ROA, LOA documentation and WHOIS fields for a leased range, and can add the verification token a cloud asks for. Provisioning inside the cloud is done by the customer. |
| Included Management | Custom netname and organisation, admin-c and tech-c control, geolocation configuration and reverse DNS on selected subnets. |
| Registry Services | Separately priced LIR registration and support, PI and ASN support, transfers and paid blocklist delisting requests. These are distinct services, not part of an IPv4 lease. |
Technical Requirements
| Requirement | Details |
|---|---|
| Minimum Prefix Size | /24. The FAQ states /25 leasing is not available. |
| Maximum Prefix Size | Not published. Larger blocks depend on what suppliers list. The FAQ describes a limit of 20 blocks per contract. |
| Provisioning Time | The BYOIP guide estimates about 24 hours for the WHOIS update after an assignment is approved. That is not an end-to-end lease or cloud import time. |
| Announcement | Depends on the deployment. A range originated by a cloud and a range announced from the customer's own AS need different authorisations, so confirm the origin in the assignment. |
| RPKI / ROA / LOA | Configured by InterLIR for the leased range. Confirm the permitted origin ASN and who maintains the objects for each block. |
| Reverse DNS | Available after an approved assignment, where the supplier has enabled rDNS for the block. |
| Geolocation | Requested through InterLIR. External geolocation databases decide when to reflect a change. |
| Portability | Depends on the supplier contract, the permitted origin and the receiving platform's approval. Continued use after the lease ends is not implied. |
Step-by-Step Process
InterLIR requests business and transaction information. A fixed KYC document list is not published.
check the supplier's minimum term before activating the order.
raise it from the order and enter the cloud verification token in the DESCR field exactly as the cloud issued it.
InterLIR approves the assignment and updates the registry records.
complete the target cloud's own validation and configuration.
Cost and Limitations
| Item | Details |
|---|---|
| Lease Price | Set per offer. Different public pages show different /24 figures, so there is no single rate to quote. Use the price on the order. |
| Lessee Platform Fee | 0%. Rent for the leased addresses is still payable; the zero figure covers only the marketplace commission. |
| Lease-Out Commission | 15% of the leased-address value, for suppliers whose resources are managed through the platform tools. |
| Sale Commission | Percentage of the block price: /24 10%, /23 7%, /22 5%, /21 to /19 4%, /18 to /17 3%, /16 or larger 2.5%. |
| Registry Services | IPv6 /48 registration €100, LIR registration €600, LIR support €150 per month. Separate services, not an IPv4 lease bundle. |
| Minimum Term | Set by the supplier. Minimums of three months or longer can apply. |
| Billing Cycle | Monthly, on the order anniversary. |
| Cancellation | Must respect the minimum term and be requested at least 24 hours before renewal, using the documented cancellation request rather than account deletion. |
| Taxes | The terms add applicable turnover tax. Confirm on the invoice. |
| Not Published | Deposits, setup fees, refund terms, support hours as a contractual commitment and a public customer API. Request them directly. |
Cloud BYOIP Compatibility
This records which clouds InterLIR documents registry-side support for. It is not a cloud partnership or a tested integration, and each block still has to pass the cloud's own validation.
| Platform | Status |
|---|---|
| AWS, Google Cloud, Microsoft Azure, OVHcloud | Documented. Named on the BYOIP service page and in the assignment guide, subject to each cloud's prefix requirements. |
| IBM Cloud | Conditional. InterLIR's own page notes that IBM Cloud does not support public BGP-advertised BYOIP in the same way, and uses deployment-specific patterns instead. |
| Oracle Cloud, Vultr | Conditional. Linked as onboarding options in the guide; confirm block and product eligibility. |
| Cloudflare | Not published. |