Forem: Artem Kohanevich

IPv4 Leasing Platforms in 2026: An Infrastructure Engineer's Comparison

Artem Kohanevich — Wed, 15 Apr 2026 08:17:50 +0000

If you've ever had to provision a /24 under a deadline, you know the drill. You need clean space, valid ROA, LOA in hand, and geolocation updated before your upstream starts routing. The platform you use to get there matters more than most people admit until something goes wrong.

IPXO is where a lot of teams start. It's automated, it's documented, and it handles the RPKI layer without you having to babysit it. But it's not the only option in 2026 - and depending on your stack and your operational model, it might not be the right one.

This is a practical breakdown of five IPv4 platforms: what they actually do, how their models differ, and when each one makes sense from an infrastructure perspective.

The technical split that matters most

Before comparing platforms, it's worth understanding the structural difference that separates them.

Managed pool model - the platform aggregates IP inventory from multiple owners into a centralized pool. You lease from the pool; the platform handles RPKI, abuse, and documentation. You don't know whose space you're using, and the owner doesn't know who's using their space. IPXO operates this way.

Direct marketplace model - IP owners list their own subnets with defined terms. You see what you're leasing, from whom, under what conditions. RPKI and ROA are still handled, but the relationship is direct. IPbnb operates this way.

The practical difference: in a managed pool, subnet history and ownership chain are opaque. In a direct marketplace, you can verify the listing, the owner's LIR status, and the subnet's reputation before committing. For environments where IP provenance matters - abuse-sensitive workloads, compliance-heavy infrastructure, or anything that's been burned by dirty space before - that transparency has real operational value.

Platform breakdown

IPXO

The established option. Large inventory, multi-RIR coverage (RIPE, ARIN, APNIC), automated RPKI/ROA setup, and abuse handling baked into the platform. The self-service dashboard is functional and the delivery pipeline is reliable.

Technical notes:

ROA creation is automated on delivery
LOA issued within the platform
Abuse complaints routed through IPXO's own abuse desk
5% platform fee on transactions
No buy/sell capability - leasing only

Where it shows its limits: if you're working exclusively in the RIPE NCC space and need subnet-level provenance, the managed pool model gives you less visibility than a direct marketplace. And if you need to monetize your own address space rather than just access inventory, IPXO isn't the right fit.

IPbnb

A direct marketplace built specifically for the RIPE region, covering leasing, buying, selling, and transfers. IP owners list their own subnets; you transact directly with them. The full compliance layer - RPKI/ROA, LOA, ASN registration, IP reputation checks - is handled within the platform.

Technical notes:

ROA and RPKI configuration included on onboarding
Subnet reputation check before listing approval
LOA documentation provided per transaction
Subnets from /24 upward
Onboarding typically within 24 hours of verification
Transparent, listed fee structure

The direct marketplace model means you can verify subnet history before committing. For teams that have dealt with the fallout of leasing space with a bad reputation history, that pre-transaction visibility is worth something concrete.

InterLIR

RIPE NCC-registered marketplace and broker, with ARIN, LACNIC, and APNIC coverage as well. Supports leasing, buying, and selling, with blocks from /24 to /16.

Technical notes:

Incoming blocks scanned against 24+ blacklists at onboarding
Ongoing abuse monitoring post-delivery
ASN registration and sponsoring ORG services available
Useful for operators without their own LIR membership
Delivery typically within 24 hours
Fee structure not publicly listed - requires direct inquiry

The blacklist scanning at onboarding is genuinely useful for teams where IP reputation is a hard requirement. The sponsoring ORG service is a practical option if you're operating without full LIR membership and need someone to handle the RIPE NCC relationship.

IPv4.Global

The original secondary market platform, operated by Hilco Streambank. Covers ARIN and RIPE primarily. Three transaction modes: online auction marketplace, privately negotiated brokered sales, and a leasing hub.

Technical notes:

Auction-based pricing - final cost not known upfront
Private brokered sales available for large blocks (/20 and above)
Leasing hub operates alongside the buy/sell marketplace
Handles transfer paperwork across ARIN and RIPE
Longest track record in the market for completed transfers

The auction mechanism introduces pricing uncertainty that complicates procurement planning - not ideal if you're working against a fixed infrastructure budget. Where it shines is large-block transactions where competitive bidding can recover significantly more value than a fixed listing price.

Prefixx

Boutique broker operating since 2018, covering RIPE, ARIN, APNIC, and LACNIC. No-win-no-fee model, with escrow on all transactions.

Technical notes:

White-Glove service includes geolocation updates, rDNS management, abuse complaint handling
Long-term lease arrangements supported
Not a self-service platform - broker-managed process
Useful for complex transactions or operators without internal NOC capacity to handle the compliance layer

If your team doesn't have the bandwidth to manage geolocation updates, rDNS setup, and abuse handling in-house, having those included as standard in the lease package removes a real operational burden. The trade-off is that you're working through a broker rather than transacting directly.

LogicWeb

Direct IP leasing provider since 2004. Owns and manages its own inventory - over 500,000 addresses. Month-to-month, no contracts, no setup fees.

Technical notes:

Same-day LOA delivery
WHOIS and geolocation updates included
RPKI/ROA setup on non-legacy subnets
No marketplace - inventory is proprietary
No buying or selling capability
Client base includes major VPN providers

The no-contract monthly model is genuinely flexible for short-term provisioning needs or when you're not sure how long you'll need the space. The constraint is inventory ceiling - you're limited to what LogicWeb owns, and there's no path to acquisition if you need to permanently add to your address space.

Quick comparison

Platform	Model	RIPE focus	Buy / Sell	ROA/RPKI	Fee model
IPXO	Managed pool	Multi-RIR	No	Automated	5% platform fee
IPbnb	Direct marketplace	Primary	Yes	Included	Transparent, listed
InterLIR	Marketplace + broker	Yes	Yes	Yes	Not public
IPv4.Global	Auction + broker + leasing	Yes	Yes	Yes	No hidden fees
Prefixx	Broker	Yes	Yes	Via White-Glove	No-win-no-fee
LogicWeb	Direct provider	No	No	On non-legacy	No setup fee

Choosing based on your operational profile

You need clean space fast with a known reputation history - IPbnb or InterLIR. Both run reputation checks before subnets are listed or approved. Direct marketplace visibility lets you verify before committing.

You're provisioning month-to-month with no long-term plan - LogicWeb. No contracts, same-day LOA, flexible exit. Straightforward.

You have a large block to sell and want market pricing - IPv4.Global. The auction mechanism is the most efficient way to find market rate on a /16 or larger.

You need address space but don't have LIR membership - InterLIR. The sponsoring ORG service covers that gap without requiring you to set up your own LIR.

You want to offload compliance overhead entirely - Prefixx. rDNS, geolocation, abuse handling - all managed for you as part of the lease.

You're building on RIPE infrastructure and want full transaction capability - IPbnb. Leasing, buying, selling, and transfers on one platform, with the RPKI and ROA layer handled.

The IPv4 leasing market has matured considerably. The right platform depends less on brand recognition and more on which operational model fits how your infrastructure team actually works.

For a full breakdown including platform-by-platform analysis, pricing model comparison, and a detailed FAQ, read the original article on the IPbnb blog: https://ipbnb.com/blog/top-5-ipxo-alternatives

Stop Treating IPv4 as Technical Debt – Here's What the 2026 Data Actually Shows

Artem Kohanevich — Thu, 12 Mar 2026 11:16:54 +0000

There's a belief that's quietly distorting infrastructure decisions across the industry: that running IPv4 in 2026 means you're behind.

It doesn't. And the data makes a strong case for the opposite view.

Let's go through what's actually happening — not in theory, but in production networks running real workloads today.

First, the Numbers Nobody Leads With

Before diving into comparisons, here's the state of play:

IPv4 share of global internet traffic:     ~60%
Fortune 500 companies IPv4-primary:        76%
Enterprise IPv6 adoption:                  32%
IPv6 migrations that complete successfully: 21%
IPv4 address price (2026):                 $50–65/IP
IPv4 address price (2011):                 $5/IP
Annual IPv4 transfer market volume:        $1.2B

This is not a protocol in decline. This protocol has outperformed predictions of its imminent replacement for fifteen years.

What Makes IPv4 and IPv6 Fundamentally Different

The core distinction is address space. IPv4 uses 32-bit addresses (192.168.1.1) — about 4.3 billion total. IPv6 uses 128-bit addresses (2001:db8::1) — 340 undecillion total, which is a number so large it's practically meaningless to visualize.

IPv4 exhausted its pool at the RIR level years ago. ARIN and RIPE no longer issue fresh allocations. What that created wasn't a crisis — it created a transfer market. Addresses change hands, get leased, get reclaimed and reallocated. The market works.

IPv6 addresses are free from registries. That sounds like a straightforward win. But free allocation and free migration are very different things.

Latency: The Counterintuitive Finding

IPv6 should be faster. The theory is solid: no NAT translation overhead, fixed-length headers that routers process more efficiently, cleaner end-to-end routing without middleboxes. On paper, it wins.

In production, it often doesn't.

Data from LinkedIn Engineering, Akamai, and Cloudflare consistently show IPv4 delivering lower latency — typically 5–15ms — in real-world deployments. A streaming platform that ran a controlled IPv6 test observed a 12% higher buffering rate during peak hours. The culprit: IPv6 BGP path optimization isn't as mature, so traffic routes through suboptimal peering points.

The reason IPv4 outperforms comes down to time. Forty years of routing table tuning, CDN infrastructure built around IPv4 peering agreements, and hardware pipelines optimized for IPv4 packet processing — none of that transfers automatically to IPv6.

For most web applications, 10ms won't move the needle. For gaming backends, financial trading infrastructure, or live video delivery, it can.

Security: Protocol Features vs. Operational Reality

IPv6 ships with IPsec as a built-in capability. That's legitimately useful. But the "IPv6 is more secure" argument usually stops there, which is where it starts to mislead.

Security posture in practice depends on three things: tooling coverage, threat intelligence quality, and how fast your team can respond. On all three, IPv4 has a significant lead in 2026.

Security tool IPv4 support:          98%
Security tool IPv6 support:          68%

IPv4 threat intelligence sources:    80+
IPv6 threat intelligence sources:    8–12

Mean time to resolve IPv4 incident:  ~45 min
Mean time to resolve IPv6 incident:  ~78 min

The MTTR gap — 45 minutes versus 78 minutes — isn't a reflection of IPv6 being insecure. It's a reflection of SIEM rules, IDS signatures, firewall policies, and threat feeds that have been iterated on for decades for IPv4. Your team's troubleshooting instincts are IPv4-native. Your vendors' default detection logic is IPv4-first.

NAT is worth a separate mention. It was designed as a workaround for address scarcity, and IPv6 advocates rightly point out it breaks end-to-end connectivity. But NAT also hides internal topology from external observers, limits exposure of internal hosts, and adds an implicit segmentation layer. IPv6's end-to-end model is architecturally cleaner — it also removes that implicit protection. Neither is wrong. Both require deliberate compensating controls.

Compatibility: Where IPv6 Adoption Actually Stalls

The adoption numbers look reasonable at a global level — around 45–50% by Google's measurement. But break it down by sector and the picture changes:

Mobile networks:          72% IPv6
Hyperscalers (AWS/GCP):   82% IPv6
ISPs:                     67% IPv6
Enterprise:               32% IPv6
SMB:                      17% IPv6
Email infrastructure:     28% IPv6
Industrial IoT:           21% IPv6

The services that haven't moved are the ones with the highest compatibility stakes. Payment processors are mostly IPv4-primary — run IPv6-only and you risk breaking checkout. About 85% of spam filtering and IP reputation systems are built around IPv4 behavior, which creates real deliverability risk for IPv6-originated email. 72% of IoT devices manufactured in 2026 are IPv4-only because adding IPv6 support increases unit cost with no operational payoff for most deployments.

This is why 95% of IPv6 deployments run dual-stack (APNIC). Not because engineers are conservative — because going IPv6-only breaks things that matter.

The Real Cost of IPv6 Migration

Here's a /22 block (1,024 addresses) cost comparison, done honestly:

Lease IPv4

Rate:           $0.40–0.55/IP/month
Monthly cost:   $410–$563
Annual cost:    $4,920–$6,756
5-year total:   $24,600–$33,780

Buy IPv4

Purchase price (today):    $51,200–$66,560
Projected value (2030):    $71,680–$92,160
Sublease idle capacity to offset holding costs

Migrate to IPv6

Infrastructure work:       ~$180,000
Team training:             ~$25,000
Ongoing dual-stack OpEx:   ~$18,000/year
5-year total:              ~$295,000

Note: you still run IPv4 in parallel for compatibility

Leasing IPv4 costs less than migrating to IPv6 for 7–9 years under these numbers. That's not an argument that IPv6 migration is never worth it — it's an explanation for why 64% of organizations report they can't build a business case for it right now.

The opportunity cost is also real. $295,000 over five years is engineering capacity, product features, or infrastructure redundancy that doesn't get built.

Operational Overhead: The 2 AM Factor

Average resolution time for network issues:

IPv4:   ~23 minutes
IPv6:   ~52 minutes

The gap has a straightforward explanation. ping, traceroute, and tcpdump output for 192.168.1.1 is instantly readable. For 2001:0db8:85a3::8a2e:0370:7334, you're reading more carefully and making more errors. IPv4 documentation density — Stack Overflow answers, vendor KB articles, known failure modes — dwarfs IPv6 equivalents. Junior engineers reach IPv4 proficiency in about 3 months; IPv6 takes 6–9 months to reach equivalent comfort.

Dual-stack doubles the management surface: two routing tables, two firewall rule sets, two address schemes. It's workable, but the overhead is real and shows up in team capacity.

IPv6 is the clear choice when:

You're building mobile carrier infrastructure at scale
A government contract explicitly requires it
You're doing greenfield data center buildout with zero legacy constraints
Your IoT deployment exceeds 100K devices and address efficiency matters

Adoption Trajectory: The Honest Timeline

Global IPv6 adoption (2026):         ~45–50%
Annual growth rate (2015–2018):      ~8%
Annual growth rate (2023–2026):      ~2–3%

Projected 80% adoption:              2040–2045
Projected full transition:           2045–2050

The growth curve has flattened. The urgency case for rapid IPv6 migration relies on a trajectory that no longer exists. Full transition is measured in decades, not years. Dual-stack operation is the normal state of internet infrastructure through at least 2040.

Five Persistent Myths

"IPv6 is faster in production" — The theory holds. Production data from multiple independent sources says otherwise. Forty years of optimization isn't overcome by a cleaner protocol spec.

"IPv6 is inherently more secure" — Built-in IPsec is a real feature. It doesn't compensate for immature tooling, limited threat intel, and slower incident response across the security ecosystem.

"IPv4 addresses are unavailable" — RIR exhaustion is real. A $1.2B annual transfer market with 52 million recovered and reallocated addresses since 2020 suggests availability isn't the problem.

"Migration is straightforward" — Only 21% of started IPv6 migrations complete successfully. The failures aren't from lack of effort — they're from unexpected compatibility issues with critical business systems.

"IPv6 dominance is imminent" — Growth has slowed to 2–3% annually. Current projections push 80% adoption to 2040–2045. Infrastructure planning based on five-year IPv6 dominance is planning based on a prediction that has been wrong for fifteen years running.

What Good IP Strategy Looks Like in 2026

Audit actual requirements — Calculate the public IPs your services genuinely need, not theoretical maximums. NAT and CGNAT cover a lot of ground.
Lease for flexibility, buy for long-term baseline — Lease if your growth trajectory is uncertain or you need fewer than 1,024 addresses. Buy if you have a 10+ year horizon and want to treat it as infrastructure capital.
Enable IPv6 on public endpoints — Web, API, and CDN layers are the right place to start. Low risk, reaches mobile users, monitors actual IPv6 traffic share without touching critical internal paths.
Keep IPv4 on critical paths indefinitely — Email, payments, internal services, and anything with a security SLA. Until IPv6 traffic exceeds 90% of your total — which won't happen soon — there's no operational case for removing IPv4 from these paths.
Verify IP reputation before provisioning — Leased or purchased addresses with abuse history will cost more in deliverability and security remediation than you saved acquiring them cheap.

What does your current IPv4/IPv6 split look like in production? Especially curious about teams running dual-stack — what's actually moving over IPv6 versus staying on IPv4.

Read the full IPv4 vs IPv6 analysis on the IPbnb blog

IPv4 Leasing Without Losing Control

Artem Kohanevich — Mon, 09 Mar 2026 09:10:14 +0000

IPv4 leasing often gets dismissed as too risky by the people who actually hold the blocks. The concern usually sounds like this: "What if I can't get it back?"

Here's the short answer: you can. Here's the structural explanation of why.

Ownership lives in the registry. Routing lives in the config.
When you hold an IPv4 block, what you actually hold is an RIR registration — a WHOIS record that names your organization as the resource holder. That record does not update when someone else starts routing your space. BGP announcements change. Your registration does not.

A lease grants routing authority. That's it. The lessee can originate traffic from your addresses for the duration of the agreement. They cannot sublease without authorization, hold the block past expiry, or acquire any RIR standing over the space. RIPE, ARIN, and APNIC classify leasing as a utilization arrangement — not a transfer event.

The two controls that actually matter

LOA (Letter of Authorization) — the document you sign to allow routing. No valid LOA, no routing. Revoke it and the upstream provider pulls the announcement, typically within 24–72 hours. This requires zero cooperation from the lessee.

RPKI / ROA — you cryptographically authorize which ASN can originate your prefix. Revoke the ROA and RPKI-validating routers reject the announcement at the network level, not just contractually. This is the part most owners don't know about — it's a structural control, not just a legal one.
What reclaiming actually looks like

Revoke or expire the LOA

Update the ROA to deauthorize the lessee's ASN
Confirm de-announcement via looking glass
Run blacklist checks before reuse

Full sequence: typically two to five business days.

The bigger picture

IPv4 space is a finite, appreciating asset. Blocks that sit idle are a capital efficiency problem. The protections described above exist precisely because the market has matured around lessor interests — they're not theoretical, they're the operational baseline.

Full breakdown with contract term requirements and reputation management, you'll find here.

The IPv4 Secondary Market Is Mature. The Tooling Hasn't Caught Up

Artem Kohanevich — Thu, 05 Mar 2026 03:21:31 +0000

I've spent my career in infrastructure and cloud. I know what it costs to scale, what it means to plan capacity under pressure, and how much operational complexity lives inside decisions that look simple on paper.

When my co-founders – who have spent years in the IPv4 market as address holders, operators, and investors – described the state of the tooling, it was immediately recognisable. A fragmented market, opaque pricing, incomplete block data, and processes that create friction where there should be clarity.

That's the problem IPbnb is built to solve. Last month, we quietly launched

Why "quietly"?

Because the IPv4 market runs on trust. We didn't want to make noise before the platform was ready to back it up. We ran a beta period, collected real friction data, fixed what needed fixing, and opened for business when we were confident the product met the standard we'd set for ourselves.

What the market actually needs

Most platforms in this space give you a CIDR block and a price. That's not enough information to make a sound allocation decision. You need block history. Routing status. Abuse record indicators. RPKI status. Reputation context.

IPbnb listings include all of it – because that's what we wanted to see on the other side of the transaction.

There's also a market education problem worth naming. Many IPv4 address holders don't realise their blocks are income-generating assets. A lot of operators don't know that leasing is a practical alternative to acquisition. Part of what we're building is the context that helps both sides make better decisions.

The technical reality of IPv4 in 2026

IPv6 adoption is real and ongoing. It's also not replacing IPv4 in most production environments anytime soon. Dual-stack is the operational norm. That sustained coexistence is what keeps the secondary IPv4 market structurally relevant – and it's the market we're building for.

One thing I'm particularly proud of

We kept support human. IPv4 transactions have real complexity – transfer documentation, compliance edge cases, block history questions. When you contact IPbnb, you reach someone with actual market context. That was a deliberate product decision, not an afterthought.

If you're managing IPv4 capacity – leasing, acquiring, or monetising idle space – the catalogue is live.

The IPv4 Leasing Mistakes That Will Cost You Thousands

Artem Kohanevich — Fri, 12 Dec 2025 09:28:20 +0000

Every month, I hear the same story from different infrastructure teams: "We thought IPv4 leasing would be straightforward. It wasn't."

The pattern is predictable. A company needs IP addresses quickly. They find a provider, sign a contract, and start routing traffic. Then reality hits—blacklisted IPs, rejected BGP announcements, surprise fees, or emergency capacity issues.

The frustrating part? Almost all of these problems are preventable.

Here are the five mistakes that cause 90% of IPv4 leasing failures—and exactly how to avoid each one.

Mistake #1: The Reputation Blindspot

Approximately 70% of first-time renters never check IP reputation before signing. They're essentially buying used infrastructure without knowing its history.

What they discover too late:

IPs are on major blacklists (Spamhaus, SORBS, Barracuda)
Addresses flagged for past botnet activity or fraud
Negative trust scores from reputation engines
Historical association with spam campaigns or proxy abuse

The damage: Email delivery blocks, service rejections, weeks of cleanup work.

Your Pre-Lease Audit Checklist

Before signing anything, verify:

Blacklist status — Scan across 80+ DNS-based blacklists and RBLs. Free tools: MXToolbox, Spamhaus checker, IPVoid.

Abuse history — Pull historical reports from Spamhaus SBL/CSS, UCEPROTECT, Cloudmark. Check AbuseIPDB for crowd-sourced intelligence.

Fraud scores — Use IPQS or FraudGuard to assess spam/fraud risk ratings.

Past usage patterns — Was this block previously used for VPN services, web hosting, mobile networks, or residential proxies? Each has different reputation implications.

Neighboring addresses — IP pollution spreads across subnets. Check adjacent ranges for issues that might contaminate yours by association.

What Your Provider Should Guarantee

Don't accept vague promises. Demand specific protections:

Comprehensive reputation report provided automatically (not on request)
Written guarantee that addresses are clean
30-60 day quarantine period for newly assigned blocks
Continuous reputation monitoring throughout lease term

The best providers run proactive monitoring systems that automatically rotate out problematic addresses before they ever reach clients. This eliminates roughly 90% of reputation risks upfront.

Mistake #2: The LOA Gap

A Letter of Authorization (LOA) is the document that proves you have legal right to announce and route specific IP addresses.

Without it, you're dead in the water.

Your ISP will refuse to announce the subnet. Upstream providers will block BGP sessions. Cloud BYOIP programs (AWS, Azure, GCP) won't accept the addresses. Switching upstream networks becomes impossible.

What Makes a Valid LOA

A legitimate LOA must contain:

Legal name of IP holder (exactly as it appears in registry)
Authorized ASN that will announce the prefix
Precise CIDR notation (e.g., 203.0.113.0/24)
Authorization period with clear validity dates

Missing any element? You're sending it back for revision while your infrastructure plans sit on hold.

The Correct Sequence

Request LOA immediately after signing lease (not when you're ready to deploy)
Verify subnet and ASN match your actual configuration
Forward to ISP/cloud provider as soon as received
Wait for route object creation in IRR (Internet Routing Registry)
Only then announce your prefix

Red Flags That Scream "Walk Away"

Provider refuses to issue LOA or makes excuses about delays
LOA validity period shorter than lease term
No clear revocation procedure in contract
Provider insists you pay before receiving LOA

The protection rule is simple: Get the LOA before making your first payment, or get a written guarantee it will be delivered within 24-48 hours of payment.

Mistake #3: The RPKI Blindspot

More than 60% of companies leasing IPv4 never set up RPKI (Resource Public Key Infrastructure). They configure routers, announce prefixes, and assume everything's secure.

It's not.

What You're Actually Risking

Without RPKI, your routes are vulnerable to:

Accidental BGP leaks — Misconfigured routers suddenly announcing your prefixes globally

Malicious hijacking — Bad actors deliberately redirecting your traffic to intercept or manipulate it

Automatic rejection — Growing number of major networks drop BGP prefixes without valid Route Origin Authorizations (ROAs)

This isn't theoretical. Major Tier-1 providers are implementing policies that treat invalid/missing ROAs as rejection signals. No cryptographic verification = no route propagation.

How RPKI Works (Simplified)

RPKI creates a cryptographic binding between:

Your ASN (Autonomous System Number)
The specific IP prefix you're announcing
Maximum prefix length allowed

A Route Origin Authorization (ROA) is the signed object proving this binding.

Example ROA:

ASN: AS64512
Prefix: 192.0.2.0/24
Max Length: 24
Trust Anchor: ARIN

When your BGP announcement goes out, other networks validate it against this ROA. Match = accepted. Mismatch = flagged or dropped.

What Your Provider Should Handle

You shouldn't need to become an RPKI expert. Your provider should offer:

Hosted RPKI services (they manage certificates)
ROA creation within 24 hours of activation
Auto-renewal (certificates expire)
Quick ROA updates when routing configuration changes

If they can't provide this, their infrastructure hasn't caught up with modern routing security standards.

Verification Tools (All Free)

RIPE RPKI Validator — Clear validation status view
NLnetLabs Routinator — Open-source validator you can self-host
BGPStream — Real-time prefix monitoring

Five minutes with any of these tells you whether your routes are protected or vulnerable.

Critical Configuration Details

When setting up ROAs:

Use exact prefix matches (if announcing /24, set maxLength to 24)
Update ROA before making any routing changes
Coordinate ROA revocation when lease ends

RPKI isn't optional anymore. It's basic routing hygiene.

Mistake #4: Block Sizing Math Gone Wrong

Teams consistently fall into two traps:

Over-leasing — Paying for capacity you'll never use. A /22 (1,024 IPs) when you only need 300 wastes $15,000+ annually.

Under-leasing — Hitting capacity constraints within months, then scrambling for emergency expansion with fragmented non-contiguous ranges.

Both are avoidable with proper sizing calculations.

The Working Formula

Required IPs = (Current demand × 1.3-1.5 growth factor) + 10-20% operational overhead

Breaking it down:

Current demand: What you're using right now
Growth factor: Expansion over 12-24 month lease term
Overhead: Routing requirements, redundancy, testing environments

Real-World Examples

Small ISP (500 subscribers):

Current: 500
Growth factor: 1.4× = 700
Overhead: +15% = 805 total
Block size: /22 (1,024 IPs)

VPN Provider (2,000 concurrent users):

Current: 2,000 users
NAT ratio: 5:1 = 400 public IPs needed
Growth factor: 1.2× = 480
Block size: /23 (512 IPs)

Ecommerce Platform (50 servers, 3 PoPs):

Current: 50 servers
Infrastructure overhead: 1.2× = 60
Growth buffer: +20% = 72
Redundancy multiplier: ×3 PoPs = 216 total
Block size: /24 (256 IPs)

Standard CIDR Sizes and Costs

/24 (256 IPs): $500-800/month — Small ISP, SaaS
/23 (512 IPs): $900-1400/month — Medium ISP, VPN
/22 (1,024 IPs): $1,600-2,800/month — Large ISP

Note: /24 is minimum for global BGP announcements.

The Smarter Scaling Strategy

Instead of over-provisioning upfront, use phased approach:

Phase 1 (Months 1-6): Start with /24
Phase 2 (Months 7-12): Expand to /23 if needed
Phase 3 (Year 2+): Move to /22 based on actual utilization

This typically reduces total spend by 25-30% while maintaining flexibility.

Common Sizing Mistakes

Teams miscalculate because they:

Base sizing only on current active users
Forget routing, NAT, and infrastructure overhead
Ignore workload specifics (VPN concurrency, CGNAT strategies, burst patterns)
Skip the contingency buffer

Use actual demand + 20-30% buffer, apply expected growth, round to nearest standard CIDR. Validate with subnet calculator.

Mistake #5: The Contract Skimming Problem

Roughly 80% of companies never fully read their IPv4 leasing contracts. They check price, verify block size, sign, and move on.

Then months later they discover what they actually agreed to. By then, damage is done.

What Actually Matters

Lease duration and renewal:

Initial term (typically 6-36 months)
Renewal structure (opt-in vs. auto-renewal)
Notice period for cancellation (90 days is excessive)
Price adjustment clauses (5-10% annual increases compound)

Termination rights:

Lessor should give 90+ days notice for revocation
Lessee should have 30-60 days termination right
Early termination fees shouldn't exceed 1-2 months' rent

Hidden fees that inflate costs:

Setup: Should be free (typical: $0-500)
LOA: Should be free (typical: $0-200)
RPKI management: Should be included (typical: $0-100/mo)
Early termination: Max 1-2 months (typical: 1-6 months)

A seemingly affordable $800/month lease can become $1,200/month with all extras.

Technical support commitments:

IP replacement if blacklisted (not your fault)
LOA/ROA delivery within 24-48 hours
Response time commitment (4 hours excellent, 24 hours acceptable)
Uptime guarantee (minimum 99.9%)

Vague language like "best effort support" means you're on your own during outages.

Restriction clauses:

Sub-leasing prohibitions (reasonable)
Geographic announcement limitations (may not fit your needs)
Use-case restrictions on traffic types
Broad "abuse" definitions (could enable unfair termination)

The Protection Checklist

Before signing:

Read entire contract (not just pricing page)
Verify auto-renewal terms and notice periods
Check for hidden fees beyond monthly rate
Confirm technical support commitments are specific
Review restriction clauses for operational conflicts
Get legal review for enterprise/multi-year leases

Getting It Right From the Start

These five mistakes—reputation blindness, missing LOA, skipped RPKI, wrong block size, unread contracts—cause most expensive IPv4 leasing failures.

They're not edge cases. They're predictable traps that ambush unprepared teams.

The economics: A $500/month lease can become a $15,000 problem if you sign blind. Four hours of focused prep prevents hundreds of hours firefighting.

Your Pre-Lease Checklist

Before signing any IPv4 lease:

✓ Run comprehensive reputation checks on all IPs
✓ Verify LOA delivery guarantee (or get it before payment)
✓ Confirm provider offers hosted RPKI with ROA auto-renewal
✓ Calculate proper block size using demand + growth + overhead
✓ Read full contract including all fee schedules and restrictions
✓ Verify technical support commitments are specific and measurable

The Right Provider Makes All the Difference

What used to take weeks of manual work can fit into a single work session when your provider handles:

Pre-vetted blocks with reputation guarantees
Automated LOA issuance
Built-in RPKI management
Clear, human-readable contracts
Proper sizing consultation

Evaluating IPv4 leasing providers? ipbnb.com was built specifically to eliminate these common failure points—pre-vetted blocks, automated LOA/RPKI, transparent contracts, and proper sizing guidance.

What mistakes have you encountered in IPv4 leasing? How did you solve them? Share your experience in the comments.

bgp ##cloudcomputing

Your IPv4 Addresses Are Probably Worth More Than You Think

Artem Kohanevich — Wed, 03 Dec 2025 11:19:08 +0000

I keep hearing the same thing from infrastructure teams: "We completed our cloud migration years ago, but our old IPv4 allocations are just sitting there."

Here's what most don't realize: those "old allocations" could be generating $30,000 to $300,000+ annually in passive revenue.

Let me show you the math.

The Market Reality Check

Current IPv4 leasing rates sit around $0.38-0.45 per IP per month. That translates to $4.56-5.40 per IP annually.

For a /24 block (256 addresses):

256 IPs × $0.40/month = $102 monthly
Annual revenue: ~$1,200

For a /20 block (4,096 addresses):

4,096 IPs × $0.40/month = $1,638 monthly
Annual revenue: ~$19,650

For a /16 block (65,536 addresses):

65,536 IPs × $0.40/month = $26,214 monthly
Annual revenue: ~$314,000

These aren't theoretical numbers. Universities, ISPs, and enterprises are already doing this.

Who Actually Owns These "Forgotten" IPs?

You might be surprised how many organizations are sitting on unused IPv4 space:

Legacy allocations from the 1990s-2000s — Before RIRs enforced strict justification policies, many organizations received far more addresses than they actually needed.

Post-merger redundancy — Company acquisitions often leave overlapping address space that becomes redundant after network consolidation.

Cloud migration leftovers — Moving workloads to AWS/Azure/GCP means those on-prem server IPs are no longer needed.

Over-provisioning from growth periods — Rapid expansion often led to "better safe than sorry" IP allocations that never got fully utilized.

Finding Your Unused Blocks

Start with your RIR portal:

ARIN (North America)
RIPE NCC (Europe/Middle East)
APNIC (Asia-Pacific)
LACNIC (Latin America)
AFRINIC (Africa)

Look for:

Ranges that haven't seen BGP announcements in years
Subnets with no active WHOIS contact updates
Allocations that predate your current infrastructure

Pro tip: Run a WHOIS lookup on your registered ranges. If you see allocation dates from 15+ years ago, there's a good chance portions are unused.

The Reputation Factor

Not all IPv4 blocks are equal. Reputation matters enormously.

Clean blocks (no abuse history, no blacklists):

Lease at premium rates
High utilization (80-90%)
Minimal vacancy periods

Compromised blocks (spam history, blacklisted):

Heavily discounted or temporarily unleaseable
Requires cleanup (time + money)
Lower utilization until reputation recovers

Before monetizing, check your block's reputation:

Query major blacklist databases (Spamhaus, Barracuda, SORBS)
Review abuse desk history
Check mail server reputation scores

If your block is clean, you're in excellent position. If it's compromised, factor cleanup costs into your monetization strategy.

Block Size Economics

Different block sizes behave differently in the market:

/24 blocks (256 IPs) — Most liquid, easiest to lease, quick deployment. Perfect for most tenants. Annual revenue: ~$1,200.

/22 blocks (1,024 IPs) — Good balance between volume and manageability. Still very liquid. Annual revenue: ~$4,900.

/20 blocks (4,096 IPs) — Enterprise-scale, steady demand from data centers and cloud providers. Annual revenue: ~$19,650.

/16 blocks (65,536 IPs) — Largest allocations, narrower buyer pool, often lower per-IP rates due to bulk discounting. Annual revenue: $250,000-350,000.

Smaller blocks lease faster but generate less total revenue. Larger blocks generate substantial income but may have longer vacancy periods between tenants.

Regional Rate Differences

Geography affects pricing significantly:

APNIC (Asia-Pacific): Highest rates, sometimes exceeding $0.60/IP monthly. Strong demand from expanding cloud infrastructure in Singapore, Japan, Australia.

RIPE (Europe): Mid-range rates around $0.40-0.45/IP monthly. Mature leasing market with established platforms.

ARIN (North America): Similar to RIPE, $0.38-0.45/IP monthly. More restrictive policies but strong demand.

AFRINIC (Africa): Lowest rates but emerging market. Less developed infrastructure = less demand currently.

If you own blocks in multiple regions, APAC allocations should be your first priority for monetization.

Lease vs. Sell: The 10-Year Timeline

At current market rates:

Selling a /22 block (1,024 IPs):

Sale price: ~$25/IP = $25,600 one-time
Timeline: Immediate liquidity
Ownership: Gone permanently

Leasing the same /22 block:

Annual revenue: ~$4,900
10-year total: ~$49,000
Ownership: Retained (can still sell later)

Leasing typically breaks even with selling around year 5-6, then continues generating income indefinitely.

The strategic advantage? You keep the asset. If IPv4 prices rebound, you can sell later at appreciated values while having collected lease income the entire time.

The Technical Setup (Easier Than You Think)

Most people overestimate the complexity. Modern platforms automate almost everything:

Traditional manual approach:

Issue LOAs (Letters of Authorization) for each tenant
Update WHOIS records manually
Configure RPKI validation
Monitor routing announcements
Handle abuse complaints
Manage contract renewals

Platform-automated approach:

Tenant screening: Automated
Routing authorization: One-click
RPKI validation: Built-in
Abuse monitoring: AI-driven 24/7
Billing & payments: Escrow-secured
Contract management: Standardized templates

The operational overhead is minimal when using established platforms. You're not running a NOC team—you're listing an asset on a marketplace.

RIR Compliance Reality

Each Regional Internet Registry has different policies:

RIPE NCC: Most flexible for leasing. Assignments and sub-allocations broadly accepted. Minimal bureaucracy.

ARIN: More restrictive. Leasing must be framed as "customer assignments" tied to network services. Requires justified-need documentation.

APNIC: Moderate restrictions. Leasing possible with proper justification and accurate WHOIS reporting.

Most platforms handle compliance automatically, but understanding your RIR's stance helps set realistic expectations.

The Risks (And How They're Mitigated)

Reputation damage — A bad tenant can blacklist your entire block. Solution: Thorough tenant screening, automated abuse detection, 24/7 monitoring.

Payment issues — Missed payments disrupt cash flow. Solution: Escrow systems, prepaid terms, automated billing.

Technical complexity — LOAs, DNS delegation, RPKI setup. Solution: Platform automation handles 95%+ of technical work.

RIR compliance — Policy violations risk penalties. Solution: Platforms maintain compliance automatically with all five RIRs.

With proper platform selection, these risks become negligible operational details rather than deal-breakers.

The Starting Point

If you're considering IPv4 monetization, here's the practical first step:

Week 1: Audit (2-3 hours)

Log into your RIR portal
Document all registered blocks
Identify unused/underutilized ranges
Check reputation status

Week 2: Calculate (1-2 hours)

Use block size to estimate annual revenue
Compare lease vs. sell scenarios
Factor in your specific region's rates

Week 3: Platform Research (2-3 hours)

Compare major platforms (IPXO, IPbnb, etc.)
Review fee structures (typically 12-17%)
Check automation capabilities

Week 4: Tax/Legal Consultation (2-4 hours)

Understand lease income tax treatment
Review compliance requirements
Get professional advice before signing contracts

Total time investment: ~10 hours to understand your full monetization potential.

The Bottom Line

IPv4 monetization isn't speculative—it's a mature market generating over $105 million annually and growing 15-20% per year.

Your unused blocks aren't dead infrastructure. They're working capital capable of generating passive income indefinitely.

The market exists. The demand is proven. The platforms are mature.

The only question is: how long will you leave that revenue on the table?

Exploring IPv4 monetization? Check out platforms like ipbnb.com that handle tenant screening, routing automation, reputation monitoring, and RIR compliance—making leasing operationally simple.

Have you monetized your IPv4 holdings? What's been your experience with leasing vs. selling? Share your insights in the comments.

IPv4 Monetization: Why Your Break-Even Math Is Probably Wrong

Artem Kohanevich — Thu, 27 Nov 2025 19:01:28 +0000

If you own IPv4 addresses sitting idle, you're leaving money on the table. The question is: which table?

I've been analyzing IPv4 monetization strategies for network operators and infrastructure companies. The math seems straightforward at first glance, but the variables matter more than most people realize.

Here's what the spreadsheets don't tell you.

The Cogent Case Study

Cogent Communications operates 11.4 million IPv4 addresses generating roughly $35-40 million annually through leasing.

Quick napkin math: that works out to about $3.29 per IP per year, or roughly $0.27 per IP per month.

At current market rates (around $18-20 per IP for large blocks), that represents a 5.5-6 year payback compared to selling immediately.

But here's the strategic advantage most people overlook: Cogent keeps ownership. They can still sell later if their strategy changes. They're collecting rent on an asset they can eventually liquidate.

The Fundamental Question

For any IPv4 block, your decision comes down to comparing two paths:

Option 1: Sell Now

You get immediate liquidity. One transaction, clean exit, capital in hand. Simple and straightforward.

Option 2: Lease Then Sell

You collect monthly income over time, then sell the block later. Total value equals all the lease payments you collect, plus whatever you can sell the block for down the road.

The challenge? Future cash flows aren't worth as much as money today. A dollar next year isn't worth a dollar this year—you need to discount future income to compare fairly.

Real Platform Performance Data

Here's what matters in practice based on 2025 market benchmarks:

High utilization scenario (90% leased, $0.45 per IP monthly):

Break-even against selling happens around year 4-5

Medium utilization scenario (80% leased, $0.40 per IP monthly):

Break-even extends to 5-6 years

Moderate utilization scenario (70% leased, $0.40 per IP monthly):

Break-even stretches to 6-7 years

Low utilization scenario (50% leased, $0.30 per IP monthly):

Break-even exceeds 10 years

Notice the pattern? A 20-point drop in utilization can extend your payback period by 3-5 years. That's the sensitivity most financial models completely miss.

Why Utilization Varies So Much

Not all IPv4 blocks are created equal. Utilization depends on several factors:

Block reputation — Clean history with no blacklists attracts more tenants. Blocks with past abuse issues sit vacant more often.

Geographic routing — Certain regions have higher demand. RIPE blocks often lease faster than ARIN blocks, for example.

Block size — Smaller allocations (/24, /23) are easier to lease consistently than large /16 blocks.

Seasonal patterns — Some industries create demand spikes during specific periods, affecting utilization rates.

Most owners assume they'll hit market averages (around 80%). In reality, individual block performance varies from 50% to 90%.

Regional Policy Constraints Nobody Talks About

Your Regional Internet Registry matters more than most people realize:

RIPE NCC (Europe): 24-month holding period before you can resell

ARIN (North America): 12-month restriction on transfers

APNIC (Asia-Pacific): Some address pools require 5-year holds before transfer

LACNIC (Latin America): Typically 12 months between transfers

Here's why this matters for monetization: if you're locked into holding anyway, leasing generates revenue during the mandatory waiting period. Selling might not even be an option for years.

The Hidden Costs Everyone Forgets

Most break-even calculations only look at gross revenue. Real-world operations include costs that erode returns:

Reputation management — Budget 2-5% of revenue for abuse cleanup and blacklist removal. Even with good tenant screening, occasional problems happen.

KYC and tenant verification — Screening new renters takes time or money. For high-churn blocks, this becomes a material cost.

Platform fees — Most marketplaces charge 12-17% commission depending on volume and contract terms.

Administrative overhead — Routing checks, monitoring systems, contract management, and general administration all consume resources.

For smaller blocks (anything under a /20), these fixed costs matter more per IP. A /24 block generating $1,500 monthly might have $200-300 in hidden costs you weren't planning for.

When Selling Actually Wins

Leasing isn't always optimal. Strategic selling makes more sense when:

You need immediate capital — M&A activity, restructuring, debt paydown, or funding growth initiatives often require cash now, not cash flow later.

Your block reputation is compromised — If cleanup costs exceed what you'd earn from leasing, better to sell at a discount and exit cleanly.

You're exiting IPv4 entirely — If your organization is pivoting away from infrastructure that needs IPv4, holding makes no sense.

Utilization projections fall below 60% — At very low utilization rates, the math simply doesn't work for leasing.

Administrative capacity is limited — Small teams without bandwidth for ongoing tenant management should consider selling rather than adding operational complexity.

The Portfolio Approach

Most sophisticated operators don't choose one strategy—they segment their holdings:

Core operational blocks — Lease these for recurring revenue while maintaining flexibility

Excess capacity from acquisitions — Lease short-term during evaluation periods

Legacy blocks with reputation issues — Sell these for one-time exits

Strategic reserve — Hold some unlisted as insurance against future needs

This isn't indecision—it's strategic asset allocation.

Market Timing Risk

Here's a sobering reality: IPv4 sale prices dropped roughly 40% year-over-year from 2024 to 2025 for large blocks.

If you sold at the peak, you captured maximum value. If you sold in mid-2025, you left 40% on the table. Timing matters enormously for one-time asset sales.

Leasing smooths out this timing risk. You're not betting on catching the market peak—you're collecting recurring income regardless of short-term price swings.

Tax Considerations

This varies by jurisdiction, but it's worth checking: recurring lease income often has different tax treatment than capital gains from asset sales.

In some regions, spreading income over multiple years through leasing can be more tax-efficient than taking a large one-time payment. In others, capital gains treatment is more favorable.

Run the numbers with your specific tax situation before deciding.

The Reassessment Frequency

Whatever strategy you choose, it shouldn't be permanent.

Reassess every 6-12 months based on actual performance:

Are you hitting projected utilization rates?
Have market sale prices moved significantly?
Has your capital situation changed?
Are hidden costs higher than expected?
Do current lease rates still justify the strategy?

The infrastructure teams winning this aren't the ones who picked the "right" initial strategy—they're the ones who adapt as conditions evolve.

The Real Decision Framework

Stop asking "should we buy or lease?" and start asking:

What's our time horizon with realistic buffers?
How does our actual utilization compare to projections?
What are our all-in costs including hidden expenses?
How much does timing risk matter to our strategy?
What's our administrative capacity for ongoing management?

There's no universal answer. Your optimal strategy depends on block size, reputation, regional policies, utilization projections, capital needs versus cash flow preference, and operating overhead capacity.

The Bottom Line

The infrastructure teams that win aren't the ones who picked "buy vs. lease" or "sell vs. lease" based on conventional wisdom.

They're the ones who built models, tracked actual performance, ran sensitivity analysis, and reassessed regularly.

And they understood one fundamental truth: doing nothing is also a decision—usually the most expensive one.

Working on IPv4 monetization strategy? I've been involved with ipbnb.com's approach to marketplace solutions for both IP owners and renters. They handle the screening, routing, and reputation monitoring that makes leasing operationally viable.

What monetization model are you using for your IPv4 holdings? Have your utilization rates matched projections? Share your experience in the comments.

The IPv4 Decision Matrix: A Framework for Infrastructure Teams

Artem Kohanevich — Wed, 19 Nov 2025 10:25:37 +0000

Every infrastructure team eventually hits the same wall: you need more IPv4 addresses, and you need them yesterday.

I've seen teams burn weeks debating whether to buy or lease. The problem? They're asking the wrong question. It's not about which option is "better"—it's about which option fits your specific situation.

Here's a practical framework I use to cut through the noise.

The Three Variables That Actually Matter

Forget the marketing fluff. Your decision comes down to three numbers:

Time horizon (in months)
Capital availability (cash on hand vs. monthly budget)
Flexibility requirements (scale up/down probability)

Let me show you how to use these.

Quick Math: The Break-Even Formula

Break-even (months) = Purchase Price per IP / Monthly Lease Rate

With current 2026 market rates:

Purchase: ~$28-30 per IP
Lease: ~$0.38-0.45 per IP/month

Plugging in median values:

$29 / $0.42 = ~69 months ≈ 5.7 years

But here's what most people miss: opportunity cost.

That $7,500 you'd spend on a /24 block? If invested elsewhere at 10% annual return, the effective break-even extends to 9-10 years.

The Decision Matrix

Here's the framework I recommend:

Lease When:

Project duration < 3 years
Cash flow matters more than asset ownership
You're testing new markets or scaling unpredictably
Speed to deployment is critical (days vs. weeks)
You need regional IPs without registry bureaucracy

Buy When:

Infrastructure is stable for 7+ years
IP reputation is business-critical (email deliverability, hosting)
Regulatory compliance requires ownership documentation
You view IPv4 as a strategic asset (limited supply, potential appreciation)

Hybrid Approach:

Most mature teams do both:

Own core blocks for stable infrastructure
Lease additional capacity for spikes, launches, or experiments

Real-World Scenario

A SaaS company I worked with needed 1,024 IPs (a /22 block) for a sudden user surge.

Option A: Buy

Cost: ~$26,000-30,000 upfront
Timeline: 3-6 weeks (transfers, registry updates)
Internal approval: Another 2-3 weeks

Option B: Lease

Cost: ~$410/month
Timeline: 48 hours
Result: Online in 2 days, saved $25K+ in immediate capital

After 6 months, when the project stabilized, they had real usage data to decide if ownership made sense. That's the power of leasing as a validation tool.

Technical Considerations

Beyond cost, consider:

Routing Security (RPKI)

Modern networks increasingly require cryptographic proof of IP authorization. Ensure your provider supports RPKI, not just legacy LOAs.

IP Reputation

A blacklisted block costs more than the addresses themselves. Whether leasing or buying, verify the block's history and monitor it actively.

Registry Policies

RIPE NCC requires 24-month holding periods before resale. ARIN has different transfer rules. Know your region's regulations.

The Bottom Line

Stop thinking "buy vs. lease" and start thinking "when to buy, when to lease, and how to combine both."

The infrastructure teams that win aren't the ones who picked the "right" option—they're the ones who matched their strategy to their actual business needs.

Building out your IPv4 strategy? I've been working with ipbnb.com on marketplace solutions for both IP owners and renters. Worth checking out if you're evaluating options.

What's your approach? Do you own, lease, or mix both? Drop your experience in the comments.