{"id":1005,"date":"2026-08-22T10:07:45","date_gmt":"2026-08-22T10:07:45","guid":{"rendered":"https:\/\/ip4.market\/blog\/1005-2\/"},"modified":"2026-08-22T10:07:46","modified_gmt":"2026-08-22T10:07:46","slug":"ripe-ncc-transfer-forms-guide","status":"publish","type":"post","link":"https:\/\/ip4.market\/blog\/ripe-ncc-transfer-forms-guide\/","title":{"rendered":"RIPE NCC Transfer Forms: Guide"},"content":{"rendered":"
\nIn this article:<\/strong><\/p>\n
    \n
  1. Understanding the RIPE Transfer Ecosystem<\/a><\/li>\n
  2. Key Forms and Documentation<\/a><\/li>\n
  3. Step-by-Step: Submitting the Request<\/a><\/li>\n
  4. Common Pitfalls and How to Avoid Them<\/a><\/li>\n
  5. Streamlining the Process<\/a><\/li>\n<\/ol>\n<\/div>\n

    Understanding the RIPE Transfer Ecosystem<\/h2>\n

    If you run an ISP within the RIPE NCC region, you know the drill: IPv4 addresses are gold dust. The secondary market isn’t just a backup plan anymore; for many, it’s the only way to expand. But buying these blocks isn’t like picking up server racks on eBay. It is, frankly, a bureaucratic marathon governed by the RIPE NCC. At the heart of it all lie the RIPE NCC transfer forms<\/strong>. Paperwork. The boring stuff that moves the actual numbers from one entity to another.<\/p>\n

    This isn’t a simple cash-and-carry deal. You aren’t buying a physical object; you are reassigning registration rights. RIPE needs to be sure the seller actually owns what they’re offloading and that the buyer isn’t just hoarding. Get these forms wrong, and you’re looking at delays. Not just hours. We’re talking weeks, sometimes months, where your network deployment project is dead in the water.<\/p>\n

    \nInsight:<\/strong> The RIPE NCC distinguishes between “Independent Resources” (holder is a LIR) and “Provider Aggregatable” (PA) space. The transfer forms and requirements differ slightly depending on the status of the resources being moved.\n<\/div>\n

    Key Forms and Documentation<\/h2>\n

    Dealing with RIPE NCC transfer forms<\/strong> means you aren’t handling a single PDF. It’s a bundle. A collection of specific requirements and proofs that you need to manage carefully. It all starts with the transfer request form, which kicks off the ticket in their system.<\/p>\n

    The Transfer Request Form<\/h3>\n

    This is your main vehicle. It asks for the nitty-gritty: who is selling (Source LIR) and who is buying (Receiver LIR). You have to list the exact address blocks, the date you plan to move, and confirm that everyone agrees to RIPE’s standard contract. Miss a digit here, and you start over.<\/p>\n

    The Transfer Contract<\/h3>\n

    Once that first form is in, RIPE generates a Transfer Contract. It’s legally binding. It ties together RIPE NCC, the seller, and you. It covers the terms and makes sure RIPE is indemnified if something goes wrong later. Authorized reps from all sides have to sign it.<\/p>\n

    Proof of Need and Usage<\/h3>\n

    The buyer can’t just say “I might need this later.” You have to prove it. For recent transfers (anything under 24 months old), RIPE wants to see a plan. You need to show how you’ll use this space within a year. Network diagrams, infrastructure plans\u2014bring them out.<\/p>\n

    \n\n\n\n\n\n\n\n\n
    Document Type<\/th>\nRequired From<\/th>\nPurpose<\/th>\n<\/tr>\n<\/thead>\n
    Transfer Request Form<\/td>\nBoth Parties (usually initiated by Receiver)<\/td>\nTo formally open the ticket and declare intent.<\/td>\n<\/tr>\n
    Transfer Contract<\/td>\nRIPE NCC, Seller, Buyer<\/td>\nLegal agreement to update the registry.<\/td>\n<\/tr>\n
    Proof of Payment \/ Invoice<\/td>\nBuyer (optional but recommended)<\/td>\nEvidence of the financial transaction (often required by legacy holders).<\/td>\n<\/tr>\n
    Company Registry Extract<\/td>\nBoth Parties<\/td>\nTo verify legal identity and signatory authority.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n

    Step-by-Step: Submitting the Request<\/h2>\n

    Getting this right requires the buyer and seller to be in sync. Here is the technical workflow for managing the RIPE NCC transfer forms<\/strong> without losing your mind.<\/p>\n

    1. Pre-Validation and Due Diligence<\/h3>\n

    Don’t even think about forms yet. The Buyer must check that the Seller is the current registered holder in the RIPE Database. If the legal name on the contract doesn’t match the name in the database exactly? Immediate rejection.<\/p>\n

    2. Initiating the Request<\/h3>\n

    The Receiver LIR logs into the RIPE NCC LIR Portal. Go to “Transfer Request.” You’ll input the Source LIR details and the specific Inetnum objects. Be accurate. A single wrong digit in the IP range kills the submission.<\/p>\n

    \nWarning:<\/strong> Ensure that the Source LIR is in “good standing” with the RIPE NCC. If the seller has outstanding annual fees, the transfer will be blocked until the debt is settled.\n<\/div>\n

    3. Signing the Contract<\/h3>\n

    RIPE reviews the request and issues the Transfer Contract. It usually arrives via email to the admin contacts of both LIRs. The signatures must match the authorized signatories in the RIPE database. Did your signatory change recently? Update the database first, or the transfer stops dead.<\/p>\n

    4. Confirmation and Update<\/h3>\n

    Once signatures are collected and the proof of need holds up, RIPE updates the database. The inetnum objects move to the Receiver LIR. Done. From the registry’s side, anyway. The physical routing (BGP announcements) is still up to you network operators to handle.<\/p>\n

    Common Pitfalls and How to Avoid Them<\/h2>\n

    The administrative weight of RIPE NCC transfer forms<\/strong> can catch you off guard. Watch out for these recurring issues if you want a smoother process.<\/p>\n