InterLIR Global
InterLIR Global
Lease IPv4 addresses from InterLIR Global Marketplace and bring them to any major cloud — AWS, Google Cloud, Azure, IBM Cloud, OVHcloud, Oracle Cloud, Vultr. Reduce your cloud IP costs by up to 93%.
BYOIP guides by cloud provider — AWS, Google Cloud, Azure, IBM Cloud, OVHcloud, Oracle Cloud, Vultr
Open the full BYOIP guide for your infrastructure: setup overview, savings for a /24, calculator presets, and links to official documentation.
BYOIP (Bring Your Own IP) allows a company to use leased or owned IPv4 address ranges within a third-party infrastructure — a cloud provider, hosting platform, or CDN — instead of relying on addresses assigned by that provider.
The process works by verifying the right to use an IP range (allocated by a Regional Internet Registry such as RIPE, ARIN, or APNIC) and authorizing the provider to announce it on the internet via BGP. The addresses themselves don't move — only their routing is updated so traffic is directed through the provider's network to your resources.
This means you maintain full control over your IP reputation, stay portable across providers, and avoid vendor lock-in — all while benefiting from scalable cloud platforms at a fraction of the cost.
Lease a publicly routable IPv4 block from InterLIR Global Marketplace (RIPE, ARIN, or APNIC registered). The minimum block size is /24 (256 IPs).
InterLIR Global configures route objects and RPKI/ROA for your leased range, provides LOA documentation, and sets up WHOIS fields (netname, ORG, admin-c, tech-c) as needed.
Submit the required authorization to your cloud provider. InterLIR Global can add the necessary verification tokens to WHOIS records on your behalf.
Your IPs are announced via BGP by the cloud provider. Assign them to services — load balancers, VMs, email — and use them just like native cloud IPs, at a fraction of the cost.
Maintain your IP reputation history — critical for email delivery, APIs, advertising, and trust-sensitive services.
Switch cloud providers without changing IP addresses. No DNS updates, no firewall rewrites, no downtime.
Your leased addresses remain under your operational control. Move them between providers freely — no permission needed, no IP changes.
Leasing IPv4 from InterLIR Global costs ~€106/mo for a /24, vs. €520–€953/mo when renting IPs directly from cloud providers.
InterLIR Global Marketplace combines the flexibility of IPv4 leasing with the operational control typically associated with dedicated address space. Manage your IP infrastructure the way you need.
InterLIR Global handles all IP-side configuration for your leased ranges: route object setup, RPKI/ROA configuration, LOA documentation, and WHOIS management. We can also add the verification tokens required by cloud providers to your WHOIS records. Cloud-side setup (provisioning within AWS, Azure, Google Cloud, etc.) is performed by the client using the provider's own documentation and tools.
Lease IPv4 addresses from InterLIR Global and bring them to any of the providers below. InterLIR Global handles all IP-side configuration — route objects, RPKI/ROA, LOA, and WHOIS setup.
AWS BYOIP lets you import your own publicly routable IPv4 ranges and use them across core services just like native Elastic IPs — but without the per-IP hourly charges that AWS introduced in February 2024. Once your range is provisioned, it integrates seamlessly into the AWS ecosystem.
Compatible services:
AWS charges €3.10 per IP per month ($3.65) — €794/month for a /24 block. By leasing IPv4 addresses from InterLIR Global and connecting via BYOIP, you pay €106/month instead.
Google Cloud BYOIP lets you import your own IPv4 ranges as a Public Advertised Prefix (PAP), then split them into Public Delegated Prefixes (PDPs) assigned to specific projects, regions, or global resources.
Imported IPs are managed identically to Google-provided addresses. The provisioning process involves ROA validation and DNS verification, and typically takes a few weeks for externally advertised ranges.
Google charges €3.10 per IP per month ($3.65) — €794/month for a /24. With InterLIR Global BYOIP: €106/month.
Azure's Custom IP Address Prefix feature allows you to bring your own IPv4 ranges into your Azure subscription. Microsoft advertises these ranges to the internet on your behalf, while you retain full control over the addresses.
Imported IP ranges are treated as regional resources and can be used to create public IPs assigned to Azure VMs, load balancers, and other services — with consistent addressing and preserved IP reputation. Azure supports global and regional deployment models for flexible multi-region architectures.
Azure Standard SKU charges €3.72 per IP per month ($4.38) — €953/month for a /24. By leasing IPv4 from InterLIR Global and using Custom IP Prefix (BYOIP), you pay €106/month instead.
OVHcloud BYOIP allows you to import your own IPv4 block (typically /24 or larger), which is announced to the internet via BGP and routed to your OVH servers. OVHcloud does not charge for the BYOIP feature itself — you only pay for the infrastructure you use.
This makes it particularly attractive for companies wanting to avoid vendor lock-in or maintain long-term control over their IP addressing. Since your IPs stay the same across migrations, firewall rules, DNS records, and third-party integrations require no changes.
OVHcloud charges €2.03 per IP per month ($2.39) — €520/month for a /24. With InterLIR Global BYOIP: €106/month.
IBM Cloud is an enterprise-grade platform for mission-critical workloads, offering public, private, and hybrid cloud models. It integrates advanced AI, data analytics, and automation capabilities to help enterprises build, manage, and modernize applications.
By leasing IPv4 addresses from InterLIR Global and connecting them via BYOIP instead of renting IPs directly from IBM, you gain the same routing and access to IBM Cloud services while significantly reducing costs.
IBM charges €3.72 per IP per month ($4.38) — €953/month for a /24. With InterLIR Global BYOIP: €106/month.
Oracle Cloud Infrastructure BYOIP lets you import your own IPv4 address ranges into your OCI tenancy. Imported prefixes are advertised via BGP and assigned to VCN resources as reserved public IPs. Oracle requires a minimum prefix size of /24 and the range must be validated against a registered ROA.
BYOIP prefixes in OCI are regionally scoped and can be used across Compute instances, Load Balancers, the Network Load Balancer, and Kubernetes service IPs via OKE. InterLIR Global handles all IP-side preparation: ROA/RPKI, LOA documentation, and WHOIS verification tokens.
OCI reserved public IPs cost $0.01/hour ($7.30/month) per IP when unattached or kept in a reserved pool — $1,869/month for a /24 (256 IPs). With InterLIR Global BYOIP: €106/month.
Vultr supports BYOIP via BGP peering on both Cloud Compute (VPS) and Bare Metal instances. You establish a BGP session with Vultr's network (AS20473 or AS64515) to advertise your prefix globally — with support for anycast routing across all Vultr locations. The BYOIP feature itself carries no extra Vultr charges.
Vultr allows up to 5 prefixes per account (/16–/24 for IPv4, /32–/48 for IPv6). BGP is typically configured using BIRD on your instances. InterLIR Global handles all IP-side preparation: LOA documentation, ROA/RPKI, and WHOIS verification records.
Vultr Reserved IPs cost $0.004/hour ($3.00/month) per IP — $768/month for a /24 (256 IPs). With InterLIR Global BYOIP: €106/month.
Compare the cost of renting IPs from your infrastructure provider vs. leasing IPv4 addresses from InterLIR Global — including annual savings.
Prices are based on current average lease rates. Final cost depends on block availability and lease terms.
Use your own or leased IPv4 space in supported cloud and hosting environments with BYOIP preparation from InterLIR Global. The service handles the IP-side work required for onboarding, including route objects, RPKI/ROA, LOA and WHOIS configuration.
BYOIP allows a business to use its own or leased IPv4 prefix in a compatible cloud or hosting environment instead of relying only on provider-assigned addresses. The setup focuses on routing authorization, RPKI/ROA, LOA and WHOIS preparation so the same public address space can remain usable across infrastructure changes.
Bring your own IP (BYOIP) is useful when you want to keep a consistent public address range across infrastructure changes instead of relying only on provider-assigned IPs. BYOIP IPv4 onboarding and IPv4 BYOIP deployment can support cloud migrations where stable addresses matter. The BYOIP service covers BYOIP cloud preparation, BYOIP provider requirements, BYOIP RPKI support and BYOIP LOA documentation.
We prepare the IPv4 prefix for the target platform and can support:
Cloud-side provisioning remains the client’s responsibility and is completed with the tools of the selected provider.
BYOIP preparation is available for deployment scenarios involving AWS, Google Cloud, Microsoft Azure, OVHcloud, Oracle Cloud Infrastructure, Vultr and IBM Cloud.
Typical use cases include virtual machines, load balancers, VPC or VCN resources, APIs, email infrastructure and other services that require stable public IP addresses.
BYOIP onboarding is completed in the following sequence:
For leased resources, the standard minimum block is /24, which contains 256 IPv4 addresses.
Keeping the same prefix can reduce DNS changes, firewall and allowlist rewrites, and the operational disruption of changing public addresses. It can also help preserve existing IP history for workloads where reputation matters.
If you do not already own a suitable prefix, you can lease IPv4 addresses and use the leased block for BYOIP where the target platform supports that model.
For migration projects, this approach keeps the public prefix independent from the underlying cloud account. Teams can move workloads while preserving stable external addresses, existing allowlists and other network dependencies that would otherwise have to be rebuilt around newly assigned IP space.
BYOIP allows a business to use its own or leased IPv4 range in a compatible cloud or hosting environment.
The standard minimum is /24, or 256 IPv4 addresses.
No. We prepare the IP-side requirements; cloud-side provisioning is performed by the client.
Yes, when the target platform supports the required routing and authorization model.
Keeping the same prefix can preserve address history and reduce disruption during migration.
For BYOIP onboarding, send the target provider, prefix requirements and ownership or lease status to InterLIR Global. The required routing, RPKI/ROA, LOA and WHOIS preparation can then be defined before deployment.