{"id":2449,"date":"2026-11-20T06:49:36","date_gmt":"2026-11-20T06:49:36","guid":{"rendered":"https:\/\/ip4.market\/blog\/?p=2449"},"modified":"2026-11-20T06:49:36","modified_gmt":"2026-11-20T06:49:36","slug":"arin-specified-transfer-vs-ripe-pa-transfers-key-differences","status":"publish","type":"post","link":"https:\/\/ip4.market\/blog\/arin-specified-transfer-vs-ripe-pa-transfers-key-differences\/","title":{"rendered":"ARIN Specified Transfer vs RIPE PA Transfers: Key Differences"},"content":{"rendered":"<p>The <strong>ARIN Specified Transfer<\/strong> process and RIPE PA transfers are two very different animals. And if you&#8217;re about to buy or sell address space, you need to understand the difference before signing anything \u2014 not after. In the ARIN region, a Specified Transfer moves a registered block between two known parties under a documented, policy-compliant process. In the RIPE NCC region, so-called PA transfers typically operate through LIR sponsorship: a sponsoring Local Internet Registry in the receiving member&#8217;s country requests an allocation on the buyer&#8217;s behalf. Each framework comes with its own eligibility rules, documentation demands, fees, and scarcity constraints tied to whatever&#8217;s left in each region&#8217;s pool. For network engineers and IT managers planning an acquisition, picking the wrong framework can delay a deployment by weeks. Sometimes it kills the deal altogether.<\/p>\n<h2>Why Transfer Procedures Differ Between RIRs<\/h2>\n<p>Each Regional Internet Registry runs under its own Number Resource Policy Manual, developed through community processes (PPMs in the RIPE region, ARIN&#8217;s PDP in North America). Those policies reflect different historical allocations, different exhaustion timelines, and \u2014 honestly \u2014 different philosophies about how resources should move. ARIN formalized transfers under NRPM Section 8 with clear recipient and source requirements. RIPE NCC policy, under RIPE-684, allows both intra-region and inter-region transfers, provided the addresses are fully utilized (an 80% utilization threshold is commonly applied before some transfers; 100% is required for receiving under certain policies).<\/p>\n<p>Practically, this means:<\/p>\n<ul>\n<li><strong>Documentation:<\/strong> ARIN wants a clear chain of custody; RIPE leans heavily on the sponsoring LIR&#8217;s relationship with the NCC.<\/li>\n<li><strong>Fee structures:<\/strong> ARIN charges transfer fees per block; RIPE NCC fees are usually paid by the sponsoring LIR as part of new allocation charges.<\/li>\n<li><strong>Waiting lists:<\/strong> ARIN&#8217;s specified and simplified transfer processes interact with a waiting list for returned IPv4 space \u2014 a timing factor buyers have to plan around.<\/li>\n<\/ul>\n<p>One more thing before you initiate anything. Check the target block&#8217;s registry, utilization history, and any routing or hijack history using WHOIS, RPKI status, and BGP data. A block with a clean history moves faster. It also carries less reputational risk \u2014 which buyers tend to underestimate.<\/p>\n<h2>What Is an ARIN Specified Transfer? Requirements and Process<\/h2>\n<p>An ARIN Specified Transfer (NRPM 8.2) is a transfer between a named source organization and a named recipient organization. Both parties must be registered with ARIN through a Point of Contact (POC) and Organization ID. The process generally runs like this:<\/p>\n<ol>\n<li>Both organizations confirm their registration records are accurate and up to date.<\/li>\n<li>The recipient submits a request specifying the source organization and the exact block(s).<\/li>\n<li>ARIN validates that the transfer complies with policy, including minimum block sizes (a \/24 minimum applies to IPv4 transfers under most provisions).<\/li>\n<li>Both parties pay applicable transfer fees.<\/li>\n<li>ARIN updates registration records. Transaction done.<\/li>\n<\/ol>\n<p>A few constraints worth memorizing: recipients may only receive address space up to their demonstrated need over a 24-month period, and transferred resources remain subject to ARIN&#8217;s reassignment and utilization requirements. Inter-region transfers into ARIN are permitted too, but they face equivalent justification. In my experience, an experienced broker or marketplace cuts the friction considerably here. IP4 Market, for instance, connects buyers with verified sellers and reviews the documentation before submission to ARIN \u2014 which helps avoid rejections caused by mismatched POC records or incomplete justification. Small details. Big delays.<\/p>\n<h2>How RIPE PA Transfers Work: LIR Sponsorship and Allocation Rules<\/h2>\n<p>In the RIPE NCC service region, IPv4 space classified as PA (Provider Aggregatable) moves through the End User Assignment mechanism. Here&#8217;s the catch: the RIPE NCC holds direct contracts only with its members \u2014 the LIRs. So an End User cannot hold PA space directly. Instead, a sponsoring LIR in the same country must submit the request on the buyer&#8217;s behalf.<\/p>\n<p>The typical flow looks something like this:<\/p>\n<ul>\n<li>The buyer identifies a target block held by an EU-based LIR.<\/li>\n<li>A sponsoring LIR in the buyer&#8217;s country verifies the buyer&#8217;s &#8220;need&#8221; \u2014 documentation showing infrastructure, a network plan, and usage projections.<\/li>\n<li>After the seller releases the block, the sponsoring LIR submits an allocation request to the RIPE NCC.<\/li>\n<li>The RIPE NCC reviews it and registers the allocation to the sponsoring LIR for the End User&#8217;s use.<\/li>\n<\/ul>\n<div class=\"result-box\">\n<p><strong>Practical tip:<\/strong> The sponsoring LIR relationship is contractual and often recurring (annual sponsorship fees), so factor those ongoing costs into your total cost of ownership. Some buyers eventually become an LIR themselves to cut out the intermediary \u2014 doable, but it means membership fees and admin overhead you can&#8217;t ignore.<\/p>\n<\/div>\n<p>RIPE policy also requires that transferred space be used efficiently, and blocks that fail utilization review may be reclaimed. Worth checking, too: whether the block carries legacy status complications, because legacy resources (non-RIPE-managed space like the early allocations) follow entirely different rules. If what you need is speed and verified inventory, marketplaces such as IP4 Market offer curated RIPE blocks with pre-checked utilization and clean routing history, which makes the LIR sponsorship process considerably smoother.<\/p>\n<h2>Timelines, Costs, and Documentation Compared<\/h2>\n<p>A well-prepared ARIN Specified Transfer usually closes in four to eight weeks. ARIN charges a processing fee (several hundred dollars per block, at present), and the paperwork pile includes the M&#038;A justification, a signed purchase agreement, and evidence of legitimate business need. One thing worth planning for: ARIN cross-checks the recipient&#8217;s existing holdings against utilization data, so expect a round or two of questions. That alone can add a week, sometimes two.<\/p>\n<p>RIPE PA transfers run on a different clock. Once the acquiring LIR and the transferring LIR have signed the sponsorship agreement, RIPE NCC validation typically takes two to four weeks \u2014 though legacy non-RIPE-managed space can drag on much longer. The cost structure is different too. The acquiring LIR pays RIPE&#8217;s sponsorship fee on top of the market price of the addresses, and brokers or marketplaces usually take a commission on top of that. As a rough rule of thumb, budget five to fifteen percent above the per-address price for transaction costs, whether you&#8217;re buying on one side of the Atlantic or the other.<\/p>\n<div class=\"result-box\">\n<p><strong>Practical tip:<\/strong> Get your ARIN utilization data or RIPE LIR account status in order <em>before<\/em> signing a letter of intent. In my experience, incomplete documentation is the single most common reason these deals stall \u2014 in both regions.<\/p>\n<\/div>\n<h2>Common Pitfalls Buyers Face in ARIN Specified Transfer and RIPE Deals<\/h2>\n<p>ARIN buyers often underestimate what &#8220;specified&#8221; actually means. ARIN wants a documented relationship or a specific need tied to the exact block size \u2014 nothing vague. Ask for a \/22 when your justification only supports a \/24, and you&#8217;re inviting rejection or a painful renegotiation. Another mistake I see repeatedly: skipping the routing history check. A block that was once announced by a hijacked or spam-heavy network can sit on blacklists for years after the transfer closes. Nobody warns you until your mail starts bouncing.<\/p>\n<p>On the RIPE side, the classic trap is acquiring addresses held by an LIR with unpaid membership fees or lapsed sponsorship. The transferring LIR has to settle every outstanding RIPE invoice before validation can proceed \u2014 and buyers who skimp on due diligence tend to find this out halfway through the deal. There&#8217;s a second wrinkle: not all RIPE PA blocks are the same. Legacy early-allocation space and standard PA space follow different transfer mechanics, and confusing the two can void an agreement outright.<\/p>\n<ul>\n<li>Verify utilization claims with third-party tools \u2014 authoritative WHOIS data and BGP announcement history, at minimum.<\/li>\n<li>Escrow the payment. Never wire funds directly to a seller you haven&#8217;t verified.<\/li>\n<li>Confirm the block carries no LOAs, leases, or open disputes.<\/li>\n<\/ul>\n<h2>Which Route Is Right for Your IPv4 Purchase? Final Thoughts<\/h2>\n<p>Go the ARIN Specified Transfer route if your organization operates mainly in North America, has a documented business need tied to a merger, an expansion, or an infrastructure rollout, and can live with a six-to-eight-week wait. It&#8217;s a rigorous process. But that rigor buys you unambiguous title under a framework that&#8217;s been tested for years.<\/p>\n<p>Prefer a RIPE PA transfer if you need broader geographic flexibility, want to route space through a sponsoring LIR anywhere in the RIPE service region, or you&#8217;re after legacy blocks that only the European framework can move. Yes, the sponsorship model adds a recurring administrative layer. It also preserves your options down the road \u2014 subnetting, announcements, all of it.<\/p>\n<p>Either way, the deciding factor is the quality of your counterparty. Verified sellers, transparent utilization data, secure escrow \u2014 that&#8217;s what separates a smooth transaction from an expensive dispute. Marketplaces like IP4 Market are built around exactly this: vetted inventory across both ARIN and RIPE regions, pre-transfer due diligence, and competitive pricing, so your team spends its time on deployment instead of paperwork. A well-executed IPv4 acquisition is an asset that appreciates. A careless one is a liability that lingers.<\/p>\n<div class=\"ip4-cta\" style=\"margin:2em 0;padding:1.2em 1.5em;border:1px solid #d8dee9;border-left:4px solid #00b8d4;border-radius:6px;background:#f8fafc\">\n<p style=\"margin:0\"><strong>Need IPv4 space?<\/strong> Lease RIPE-verified \/24&ndash;\/22 subnets at a flat \u20ac0.50\/IP per month &mdash; LOA + RPKI\/ROA in minutes, instant company verification, automatic renewals. <a href=\"https:\/\/panel.ip4.market\/marketplace?utm_source=blog&amp;utm_medium=cta&amp;utm_campaign=post-footer\" rel=\"nofollow\">Browse available subnets &rarr;<\/a><\/p>\n<\/div>\n","protected":false},"excerpt":{"rendered":"<p>The ARIN Specified Transfer process and RIPE PA transfers are two very different animals. And if you&#8217;re about to buy or sell address space, you need to understand the difference&#8230;<\/p>\n","protected":false},"author":1,"featured_media":2451,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[2],"tags":[],"class_list":["post-2449","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-ipv4-market"],"_links":{"self":[{"href":"https:\/\/ip4.market\/blog\/wp-json\/wp\/v2\/posts\/2449","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/ip4.market\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/ip4.market\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/ip4.market\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/ip4.market\/blog\/wp-json\/wp\/v2\/comments?post=2449"}],"version-history":[{"count":1,"href":"https:\/\/ip4.market\/blog\/wp-json\/wp\/v2\/posts\/2449\/revisions"}],"predecessor-version":[{"id":2450,"href":"https:\/\/ip4.market\/blog\/wp-json\/wp\/v2\/posts\/2449\/revisions\/2450"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/ip4.market\/blog\/wp-json\/wp\/v2\/media\/2451"}],"wp:attachment":[{"href":"https:\/\/ip4.market\/blog\/wp-json\/wp\/v2\/media?parent=2449"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/ip4.market\/blog\/wp-json\/wp\/v2\/categories?post=2449"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/ip4.market\/blog\/wp-json\/wp\/v2\/tags?post=2449"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}