Transferring IPv4 Between Related Companies: Key Rules

Moving IPv4 between related companies is common corporate work, and yet it gets misunderstood more often than almost any other network task. Subsidiaries, parents, affiliated entities—when one of them needs to hand an IPv4 block to another, the transaction still has to comply with Regional Internet Registry (RIR) policy. Shared ownership changes nothing. Many IT managers assume intra-family transfers sit outside regulatory oversight. They don’t. In practice, RIRs scrutinize related-company transfers the same way they scrutinize any third-party deal: documented justification, eligible holder status, and—in many regions—demonstrated need for the space.

Why Corporate Restructuring Complicates IPv4 Transfers

Reorganizations leave scars in the registry databases. Mergers, acquisitions, spin-offs, internal reshuffles—all of it frequently leaves IPv4 holdings scattered across legal entities that no longer match how the business actually runs. Picture a multinational group that bought three regional ISPs over a decade. Each acquisition likely came with its own allocations, registered to different legal entities, possibly under different RIRs. Then the group consolidates infrastructure, and suddenly the network engineers are the ones untangling the corporate history.

What makes these transfers tricky? A few things:

• Separate legal entities: RIRs recognize legal entities, not corporate groups. A subsidiary in Germany and its US parent are two distinct registrants, even at 100% common ownership.
• Differing RIR frameworks: ARIN, RIPE NCC, APNIC, LACNIC, and AFRINIC each apply their own transfer policies, needs-based assessments, and fees. A block under RIPE may move fairly freely between organizations within the region; an ARIN transfer requires the recipient to demonstrate need for at least 24 months.
• Legacy holdings: Legacy space acquired before transfer policies existed may carry specific conditions, or demand extra verification steps.
• Tax and accounting treatment: An intra-group transfer can still count as an asset sale for tax purposes—which means valuation requirements and intercompany transfer pricing documentation.

And the risk of getting it wrong is real. The RIR can reverse the change. It can reclaim the addresses. Worse, if WHOIS records no longer match what’s actually happening on the network, routing disruptions follow.

RIR Policies for Transferring IPv4 Between Related Companies

Each registry has its own provisions for related-entity transfers. Read them before you start—after the fact is a bad place to learn them.

ARIN

ARIN’s Number Resource Policy allows transfers between affiliates, and some may qualify for a simplified review. The recipient still has to demonstrate need, but specified transfers to related entities can lean on the donor’s existing justification history. Both parties submit requests regardless. Both pay applicable fees. And both must confirm there are no disputes over the resources.

RIPE NCC

The RIPE region generally skips justification requirements for transfers under the End User Assignment transfer scheme; the recipient must hold (or obtain) an End User Assignment Agreement, typically through a sponsoring LIR. For a group consolidating its holdings, this often means engaging a sponsoring LIR to hold the resources on behalf of the end-user entity.

APNIC

APNIC allows transfers between validated members and non-members alike, but the recipient must meet documented need requirements based on a usage plan—usually covering usage within defined timeframes. Intra-group transfers get no blanket exemption here.

AFRINIC and LACNIC

AFRINIC’s policies run more restrictive. LACNIC requires demonstrated need on the receiving side. If your space sits across these regions, talk to region-specific counsel or an experienced broker before planning any consolidation. It’ll save you months.

Policies shift over time, so verify current requirements directly with the relevant RIR before you commit to a transfer timeline.

Mergers and Acquisitions: Documentation and Successor Rights

In an M&A deal, IPv4 blocks transfer as part of the acquired company’s assets—but only if the transfer is properly registered with the RIR. Successor rights do not pass automatically at closing. The acquirer must formally notify the registry and complete a holder-of-record change. The paperwork typically includes:

1. Proof of the corporate transaction: merger certificates, asset purchase agreements, or share purchase agreements showing the change of control.
2. Resource inventory: a complete list of the target entity’s allocations, assignments, and autonomous system numbers.
3. Updated organizational data: the successor’s legal name, address, and administrative contacts in the registry database.
4. Payment of registry fees: most RIRs charge processing fees for re-registration, even with no market transaction involved.

Here’s the pitfall that catches people: after closing, the buyer discovers the target never properly registered its legacy space. Or that portions of the block were transferred away years ago, with the seller’s records never reflecting it. Diligence teams should verify the block’s status in the RIR database and confirm the seller’s legal authority over the resources before signing anything. Working with a verified marketplace like IP4 Market adds a layer of protection at exactly this stage—every listing undergoes ownership verification, and escrowed transactions make sure registry updates are completed before funds move, which cuts down post-close surprises considerably.

Rebrands and Legal Entity Changes: Updating Your Registration

A name change is not always a transfer. When a company rebrands, or goes through a legal entity change — two subsidiaries merging into one, an LLC converting to a Corporation, a simple name amendment filed with the state — the underlying legal entity usually survives. And so does its registry registration. In those cases the right path is typically a registration update, not an intra-RIR transfer. That saves real time and money.

Why does the distinction matter? Because registries read the paperwork closely. If Delaware filings show that “Acme Analytics LLC” merely amended its name to “Acme Intelligence LLC,” most registries (ARIN, RIPE NCC, APNIC) will accept documentation proving continuity of the legal entity and update the registration data without a formal transfer. But here’s the catch: if the rebrand coincides with an asset sale to a newly incorporated entity — a common tax-driven structure — the registry treats it as a genuine transfer of resources. M&A documentation required. Transfer fees too.

• Gather the paper trail early: certificates of amendment, merger filings, and shareholder resolutions proving entity continuity.
• Notify your RIR proactively: voluntary updates get processed far faster than corrections discovered during audits.
• Update SWIP/RDAP data: stale network registrations trigger abuse complaints routed to dead contacts, and that damages your reputation.

Don’t be tempted to file a rebrand under “low-priority administrative task.” IRRs and downstream providers validate registration data, and mismatches between WHOIS and real-world routing announcements can get you route filtering or RPKI validation failures. I’ve seen it happen to otherwise well-run networks.

Intercompany Transfers: M&A-Free Moves Within Corporate Groups

Sometimes IP blocks need to move between two distinct legal entities under common ownership — from a holding company to an operating subsidiary, say — without any acquisition event. These intercompany transfers still satisfy registry “transfer of resources” definitions. Why? Because the legal registrant changes, even if economic ownership does not.

Each RIR handles this a bit differently. ARIN processes these as standard specified transfers, requiring a signed transfer agreement and proof of corporate relationship — a consolidated organizational chart and board authorization, for instance. RIPE NCC members moving resources between LIR accounts often use internal account merges or the sponsoring LIR process, which can be simpler than a full transfer. APNIC requires documented justification of need for the receiving account.

Practical advice for intra-group moves:

1. Decide on structure first: an internal transfer, a license, or a simple reassignment each carries different registry, tax, and audit implications — involve legal and tax advisors before filing, not after.
2. Document consideration: even between related parties, registries expect a transfer agreement; and tax authorities, who are entirely unrelated, expect arm’s-length pricing.
3. Plan for routing cutover: update IRR objects, RPKI ROAs, and BGP announcements in a coordinated window. Get this wrong and you blackhole production traffic.

Since pricing within a group is less commercially sensitive, many organizations use these transactions to establish a defensible internal valuation — useful reference data if the block is ever sold externally. Working with a marketplace like IP4 Market can help here too: transaction data and comparable sales provide objective benchmarks for intercompany pricing. And if the group later decides to monetize surplus space, verified sellers and escrowed transactions on IP4 Market offer a trusted path to market.

Conclusion: Getting Your Intercompany IPv4 Transfer Right

Transferring IPv4 between related companies is administratively simpler than an arms-length sale. But it is not a rubber-stamp exercise — far from it. The registry’s core concern, that the receiving entity is legitimate, the documentation is consistent, and the resources will actually be used, applies with equal force whether or not money changes hands.

It comes down to preparation. Confirm which legal entity holds the registration. Establish the corporate relationship with primary documents. Obtain the RIR’s pre-approval where offered, and coordinate the technical cutover of WHOIS, IRR, and RPKI data. Treat rebrands as registration updates rather than transfers where continuity of the entity can be proven, and structure intra-group moves with both registry requirements and tax obligations in view.

Handled this way, an intercompany IPv4 transfer typically completes in weeks rather than months, leaves a clean audit trail, and preserves the value of your address holdings. Whether you’re consolidating blocks after a merger, repositioning resources within a group, or eventually taking surplus space to market, a disciplined process — and experienced partners such as IP4 Market when external transactions are involved — will protect both your networks and your investment.