IP Address Leasing for Data Centers: Costs, Renter Assignment, and RIPE Rules
Your racks are ready, your renters are waiting, and the one thing you cannot buy off the shelf is a routable IPv4 block. Here is how leasing fills that gap - and what the registry expects from you in return.
Artem Kohanevich
Co-Founder & CEO at IPbnb
Last updated
Table of Contents
item
A new hall comes online in six weeks. The power is contracted, the cross-connects are mapped, the first three cabinets are already sold. Then someone opens the IPAM spreadsheet and finds 40 free addresses against 300 committed ones.
This is the quiet bottleneck in data center expansion in 2026. Every other input scales with money and lead time. IPv4 does not. You cannot order 512 addresses from your registry the way you order transceivers, and the RIPE waiting list moves on a timescale that has nothing to do with your build schedule.
IP address leasing is how most facilities close that gap. It is a straightforward arrangement - an owner of an IPv4 block grants you the right to announce and use it for a fixed term, for a monthly fee - but the operational details matter more for a data center than for almost any other kind of business. You are not just consuming addresses. You are passing them down to renters, and that changes what the registry expects of you.
This guide covers what it costs, what the alternatives cost, how to hand leased space to your own renters without breaking registry policy, and what to look for in a lease agreement.
Why data centers run out of IPv4
RIPE NCC allocated its last freely available IPv4 space in November 2019. Since then a new LIR can receive exactly one /24 - 256 addresses - from the waiting list, and only if it has never held a RIPE allocation before.
The wait currently runs 12 to 24 months, and the supply refilling that queue comes almost entirely from deregistrations and closed businesses. As we covered in our guide to RIPE NCC membership costs, the route also costs €1,000 to sign up plus €1,800 annually, which means roughly €4,600 before the block arrives. For one /24.
For a facility adding capacity rack by rack, this is not a supply line. It is a lottery ticket.
Meanwhile demand keeps climbing. AI and GPU workloads are driving a wave of new colocation capacity, and every customer-facing service in those cabinets still needs a public IPv4 address to be reachable. IPv6 deployment continues, but no data center can tell a customer their service will be unreachable from the parts of the internet that have not caught up yet.
What IP address leasing is
IP address leasing is a contractual arrangement in which the owner of an IPv4 block gives a renter the right to use and announce that block for an agreed period, usually monthly or annually, while the block stays registered to the owner.
Three things come with a properly structured lease:
A Letter of Authorisation (LOA), which your upstream providers will require before they accept your announcement of the block.
A ROA - a Route Origin Authorisation published by the owner in the RPKI, naming the ASN that is permitted to originate the block. Without it, modern filtering will drop your routes.
Registry records that reflect actual use, maintained by the owner or their sponsoring LIR.
The block does not become yours. You do not need to be an LIR, you do not need to be on any waiting list, and you can hand it back when the contract ends. That last point is the real advantage for a data center: address demand grows in steps that are difficult to forecast, and a lease lets you match address capacity to committed capacity instead of to a five-year guess.
If you plan to announce the space yourself rather than through an upstream, our guide to routing paths for leased IPv4 walks through the four options and the ROA rules for each.
What it costs
Buy for the address space you are confident you will still be using in five years. Lease for growth you have not yet fully sold. Most facilities end up with both, and our buy vs lease comparison goes through the decision in more detail. You can model your own numbers in the IPv4 pricing calculator.
Passing leased space to your renters
This is where data centers differ from every other kind of IPv4 renter, and where most of the avoidable mistakes happen.
A hosting company leasing a /24 for its own servers has one relationship to manage. A colocation provider is a distribution layer: you take address space from an owner and hand portions of it to renters who operate their own equipment. Registry policy has opinions about that.
Start with the contract. Not every lease permits onward distribution. Some agreements explicitly prohibit sub-leasing, and discovering that after you have already assigned space to three cabinet customers is an expensive conversation. Before you sign, confirm in writing that the agreement allows you to assign portions of the block to your own renters, and on what terms.
Then the registry records. RIPE is direct on this point: only allocations and assignments registered in the RIPE Database are considered valid, and registering the object is the final step that makes an assignment real. ARIN applies a comparable rule through SWIP, where any reassignment of a /29 or larger must be registered with the customer name.
In a lease, the block is registered to the owner, not to you. That means the records describing your renters have to be created under the owner's maintainer, or through their sponsoring LIR. Practically, you need three things agreed before the first renter is provisioned:
Who creates the objects - you, via delegated maintainer access, or the owner on request.
How fast - a 48-hour turnaround on a record is fine; a two-week one will hold up provisioning.
What contact data appears - in particular the
abuse-c, which determines where complaints about your renters' traffic actually land.
And the exit path. RIPE policy on provider aggregatable space is blunt about what happens when a downstream customer changes provider: the space must be returned and the network renumbered. Build that into your own renter agreements from day one. A customer who assumes the addresses move with them when they leave your facility is a customer you will argue with later.
Reputation is shared, and that is the real risk
A /24 is one block. If one renter in it runs an operation that gets the range listed on a major blocklist, the consequences do not stay in that renter's cabinet. Mail delivery degrades for everyone else in the block. The listing may follow the range for months.
For a data center, this is not a theoretical concern - it is the single most common reason leased space goes bad. Three practices contain it:
Check the block before you take it. Registry records, routing history, and blocklist status are all public. Our guide on how to check who owns an IP address covers the WHOIS and RDAP process, and the same checks reveal whether a range has a past you would rather not inherit.
Segment by risk profile. Do not put a mail-heavy renter and a general hosting renter in the same /24 if you can avoid it. Separate blocks contain separate problems.
Write acceptable use into the renter agreement, with teeth. You need the contractual right to suspend a renter quickly, because the owner's lease agreement almost certainly gives them the right to act against you on the same timescale.
Ask the owner directly how they handle abuse reports, how quickly they respond, and whether they will work with you on delisting rather than simply terminating the lease. A good answer here is worth more than five cents an address.
Renters running hybrid, and BYOIP
Some renters in your facility will also run workloads in public cloud, and will want the same addresses in both places. That is what BYOIP is for - bringing your own address range into AWS, Azure, Google Cloud, or OVHcloud instead of paying per-address cloud fees.
Leased space qualifies, provided the owner publishes the right ROA. AWS charges $3.65 per month for each public IPv4 address it provides, and ranges brought in under BYOIP are exempt - which for a /24 is a meaningful monthly difference. The BYOIP overview and our per-provider guides cover the requirements and provisioning steps for each platform.
It is worth knowing this even if you never do it yourself. A renter who asks whether their leased range can follow them into a hybrid deployment is asking a question you can answer, and that answer is a reason to stay in your facility rather than move.
What to look for in a lease provider
Once the commercial terms are comparable, the differences that matter to a data center are operational:
RIR compliance and clean registration. The owner should be a verifiable, properly registered party. If you cannot establish who actually holds the block, do not lease it. Ranges with untraceable ownership are the raw material for IPv4 hijacking.
LOA and ROA handling. Both should come as standard, promptly, without escalation.
Onward assignment terms. Stated plainly in the contract, as above.
Term flexibility. You want to add a /24 when a customer signs, not at the annual renewal date.
Registry record turnaround. Ask for a committed timescale.
Abuse process. Ask what happens on the first complaint, not the tenth.
Reputation guarantee. Ask what recourse you have if a block arrives already listed.
IPbnb works with data centers and colocation providers on exactly this profile of requirement - short lead times, incremental block sizes, and clean space that can be documented down to the renter.
Frequently asked questions
Can a data center lease IP addresses to its own customers?
Usually yes, but only if the lease agreement with the owner permits onward assignment. Confirm this in writing before provisioning anyone, and agree how registry records for those customers will be created and maintained.
How many IPv4 addresses does a data center need?
It depends entirely on the service mix. A colocation floor selling dedicated servers might budget a handful of addresses per cabinet; a facility hosting customer-facing web services will need considerably more. The practical approach is to lease in /24 increments against committed capacity rather than forecast one large block up front.
Do data centers own their IP addresses?
Some do, some lease, most do both. Owned space typically covers stable, long-term infrastructure, while leased space absorbs growth. Ownership requires either an RIR allocation or a purchase on the transfer market, both of which are slower and more capital-intensive than leasing.
What happens if one customer gets the shared block blacklisted?
Everyone in that range is affected, which is why risk segmentation and a fast suspension clause in your renter agreements matter. Delisting is possible but can take weeks, and repeated incidents can put your lease itself at risk.
Can leased IPv4 be used with cloud BYOIP?
Yes, on AWS, Azure, Google Cloud, and OVHcloud, provided the owner publishes a ROA authorising the relevant provider. The range must usually be a /24 or larger.
