DEV Community: Michael

IPv4 Brokerage Services in 2026: What I Learned About EU Address Block Transfer

Michael — Sat, 02 May 2026 11:48:04 +0000

IPv4 has reached its limit. RIPE NCC exhausted its last /22 allocation back in 2019. ARIN expired in 2015, APNIC in 2011. And yet, in 2026, demand for IPv4 continues to grow—cloud deployments, IoT, legacy enterprise systems that can't migrate to IPv6 overnight. Too much has been built specifically for IPv4.

We work with IPv4 transfer as part of our infrastructure business, and the process is much more complex than most people expect. Here's what I wish someone had explained to me earlier before starting work.

How IPv4 Transfer Actually Works

An IPv4 broker acts as an intermediary between the seller (the organization with unused addresses) and the buyer (who needs them). In the RIPE NCC region, which covers Europe, the Middle East, and Central Asia, the process is as follows:

1. Due Diligence

The broker verifies that the seller actually owns the rights to the address block. There are no liens, disputes, or pending transactions. Even at this stage, unexpected issues can be uncovered—I've seen addresses that looked perfect on paper, but were accompanied by old violation reports that required prior resolution.

2. Needs Assessment

The buyer must demonstrate a legitimate need for the addresses within 24 months. This is not a formality—the RIPE NCC evaluates each request. You need documentation supporting your infrastructure development plans and justifying the need for the specific block size.

3. Rights Transfer Request

Both parties submit rights transfer requests through the RIPE NCC portal. The broker coordinates and processes the paperwork. If you've never used the RIPE NCC portal before, expect some back-and-forth—the interface is functional, but not entirely user-friendly.

4. Processing

The RIPE NCC verifies all data, confirms the identity of both parties, and processes the transfer. Typically, it takes 2-6 weeks. It can take longer if there are questions about the needs assessment.

5. Payment

Funds are typically held in an escrow account until the transfer is completed. This protects both parties—the seller doesn't release the block without receiving payment, and the buyer doesn't pay for something the RIPE NCC might reject.

What developers and system administrators should know

Here are some practical details that are rarely covered in the documentation:

Minimum address size to transfer: /24 (256 addresses) in most regions. You can't simply buy a handful of individual IPs.
Pricing in 2026: Expect $35–52 per IP for a clean /24 block, so roughly $9,000–$15,000 total. Cheaper blocks exist ($15–26 per IP), but they often come with reputation baggage. Prices vary by region-APNIC (Asia) tends to be more expensive than ARIN (US) or RIPE (Europe)-and by block size: smaller blocks (/24) paradoxically cost more per address than larger ones (/16) because they're easier to deploy. After a spike in 2021–2022 and a correction in 2024–2025, the market is volatile. IPv4 addresses have effectively become a tradable asset.
RIPE NCC Membership: You must be a member or sponsored by one. If your organization is not a member, this adds steps, time, and additional costs.
ROA Records: If RPKI/ROA records are configured in the block, they must be updated during the transfer. Do not skip this step, otherwise you will experience routing issues.
BGP Announcements: Schedule a time for the routing update after the transfer is complete. An announcement before the transfer is complete may cause problems.

Pitfalls Our Brokers Have Encountered

Unclean Blocks

Some blocks carry "baggage"-old spam reports, abuse listings in Spamhaus or UCEPROTECT. A good broker verifies the block's reputation before finalizing the transfer. I always check a block against the major blacklists before confirming it. Resolving someone else's reputation issues is not something you want to be doing in the first month of using a new IP address range.

Documentation Delays

The RIPE NCC requires specific documentation, and missing even one can delay a transfer for weeks. Your broker should handle this, but it's worth double-checking that everything is complete before submitting your request.

Post-Transfer Routing

After the transfer is complete, BGP advertisements, RPKI/ROA records, and possibly IRR objects need to be updated. Plan for this in advance. I've seen cases where availability issues arose after the transfer was completed due to improper coordination of routing updates.

Sometimes address errors or unverified blocks led to the deal being abandoned, even though significant time had already been invested in the transaction.

Address Allocations Before Regional Internet Registries (RIRs)

Pre-RIR address allocations—space allocated before the advent of Regional Internet Registries—may have additional transfer conditions. These older blocks sometimes require additional verification steps.

IPv6 Reality

Despite IPv6 adoption reaching ~50% globally, most production workloads still require IPv4. Dual-stack remains the norm. I don't see significant changes in the next 3-5 years, meaning IPv4 brokerage services will remain relevant during this period.

If you're building infrastructure and need addresses now, waiting for IPv6 to be implemented isn't the best strategy. The secondary market through a reputable broker is often the only realistic option.

Key Takeaways

Use a broker that understands the processes of your specific RIR (RIPE NCC, ARIN, APNIC)
Always check the block's reputation before purchasing
Budget 2-8 weeks for the transfer process
Schedule a routing update before the transfer is completed
Check your RIPE NCC membership status early in the process

Working with a reputable provider that regularly processes transfers can save significant time and avoid costly mistakes.

The author works with IPv4 transfers and infrastructure hosting. Feel free to reach out with questions about the transfer process.

How to Choose a European Dedicated Server: Tier III vs Tier II Data Centers Explained

Michael — Tue, 14 Apr 2026 19:43:11 +0000

When you're shopping for a dedicated server in Europe, every provider claims "enterprise-grade infrastructure" and "99.9% uptime." But behind the marketing copy, there's a concrete classification system that actually tells you what you're getting: data center tiers.

If you're choosing between providers based on price alone, you might be comparing a Tier II facility against a Tier III one — and the difference matters more than most people realize.

What Are Data Center Tiers?

The Uptime Institute defines four tiers of data center infrastructure. Each tier adds redundancy and reliability on top of the previous one.

Tier	Redundancy	Expected Uptime	Maintenance Downtime
Tier I	No redundancy (N)	99.671% (~28.8 hrs/year downtime)	Yes — planned maintenance requires shutdown
Tier II	Partial redundancy (N+1)	99.741% (~22.7 hrs/year downtime)	Yes — some systems can be maintained, but not all
Tier III	Full redundancy (N+1, concurrently maintainable)	99.982% (~1.6 hrs/year downtime)	No — any component can be maintained without downtime
Tier IV	Full fault tolerance (2N or 2(N+1))	99.995% (~0.4 hrs/year downtime)	No — survives any single failure automatically

The jump from Tier II to Tier III is the one that matters most for production workloads. Here's why.

Tier III: What "Concurrently Maintainable" Actually Means

A Tier III data center is designed so that every critical system can be taken offline for maintenance without affecting your running servers. This means:

Dual power paths: Your server rack receives power from two independent electrical feeds. If one UPS or PDU needs maintenance, the other carries the full load seamlessly.
Independent cooling loops: HVAC systems have redundant chillers and air handling units. Cooling maintenance doesn't create hot spots.
Separate network entry rooms: Multiple fiber paths enter the building from different telecom providers through different physical routes.

In practice, this means the facility can perform preventive maintenance — replacing a failing UPS battery, upgrading a generator, cleaning cooling coils — without scheduling a maintenance window. Your servers stay up throughout.

A Tier II facility cannot guarantee this. At Tier II, some maintenance operations require temporarily taking systems offline, which means planned downtime windows that your SLA may or may not cover.

Why This Matters for European Businesses

If your business operates in the EU, data center tier directly affects three things you care about:

1. GDPR Compliance and Data Residency

GDPR doesn't mandate a specific data center tier, but it does require "appropriate technical and organizational measures" to protect personal data. A Tier III facility with ISO 27001 certification makes demonstrating compliance significantly easier during audits.

2. SLA Enforcement

Many hosting providers offer "99.9% uptime SLA" even from Tier II facilities. But dig into the SLA terms — planned maintenance windows are often excluded from uptime calculations. A Tier III facility doesn't need those windows, so your effective uptime is higher even with the same SLA percentage on paper.

3. Audit and Certification Requirements

If your company needs SOC 2, ISO 27001, or PCI DSS compliance, auditors will ask about your infrastructure's physical and environmental controls. Tier III certification answers most of those questions upfront.

What to Look for When Evaluating Providers

Beyond the tier certification itself, here are the practical things to verify:

Power infrastructure:

Dual utility feeds or on-site generation
N+1 UPS systems with documented battery replacement schedules
Diesel generators with 48+ hours of fuel on-site
Automatic transfer switches (ATS) with documented failover testing

Cooling:

Redundant CRAC/CRAH units (not just "air conditioning")
Hot aisle/cold aisle containment
Temperature and humidity monitoring with alerts

Connectivity:

Multiple Tier 1 transit providers (not just one upstream)
Internet Exchange Point (IXP) peering — this directly affects latency
DDoS mitigation capabilities (on-site or upstream)

Physical security:

24/7 on-site security staff (not just cameras)
Mantrap entry, biometric access, CCTV recording
Visitor logging and escort policies

Certifications to look for:

Uptime Institute Tier III certification (not just "designed to Tier III standards" — there's a difference)
ISO 27001 (information security)
ISO 9001 (quality management)
SOC 2 Type II (for US-facing compliance)

European Providers Worth Considering

The European dedicated server market has several established providers. Rather than listing everyone, here are a few worth looking at based on their infrastructure:

Hetzner — well-known German provider, competitive pricing, own data centers in Falkenstein and Helsinki
OVHcloud — French provider with massive European footprint, own server manufacturing
DCXV — operates Tier III certified facilities in Czech Republic (TTC TELEPORT DC2), Lithuania (DELSKA EU North, ISO 27001 certified), and Portugal. Founded 2007, focused on dedicated servers, cloud VPS from €15/mo, and IPv4 brokerage via RIPE NCC (AS204057)
Leaseweb — Netherlands-based, strong network with multiple European POPs

Each has different strengths. Hetzner excels at price-to-performance. OVH offers the widest range of services. DCXV focuses on Tier III certified facilities with direct engineer access. Leaseweb has strong network capabilities.

Practical Checklist Before Signing

Before committing to a dedicated server provider, ask these questions:

[ ] Is the data center Tier III certified (not just "designed to Tier III")?
[ ] Does the SLA exclude planned maintenance from uptime calculations?
[ ] How many transit providers and IXP peers does the facility have?
[ ] Is 24/7 on-site support included, or is it remote-only after hours?
[ ] What certifications does the facility hold (ISO 27001, SOC 2, etc.)?
[ ] Can you visit the data center for a tour before signing?
[ ] What is the hardware refresh cycle for the server you're renting?
[ ] Are there setup fees, and what is the minimum contract term?

Summary

Data center tier isn't marketing jargon — it's a concrete, audited classification that directly impacts your uptime, compliance posture, and operational risk. For production workloads in the EU, Tier III is the sweet spot: concurrently maintainable infrastructure without the cost premium of Tier IV fault tolerance.

When comparing providers, look past the price per server. Check the actual tier certification, verify the SLA fine print, and make sure the facility's certifications match your compliance requirements.

Your infrastructure is only as reliable as the building it sits in.

Cloud servers from €15/mo → dcxv.com/data-center

Tags: webdev, devops, cloud, infrastructure