If your organization is planning to buy, sell, or restructure address space under ARIN’s authority, you need to understand how IPv4 gets transferred into an SPIN or interim account. Get this wrong at the account level and a transaction that should take days can stretch into weeks. ARIN’s Number Resource Policy introduced a streamlined transfer process that has reshaped how service providers and enterprises handle their holdings, and yet plenty of teams still stumble on the account side of things. This article, the first in our series, covers what these account types actually are, why ARIN insists on them, and how to move your IPv4 holdings correctly the first time.
What Is an SPIN or Interim Account in ARIN?
A Service Provider Intermediate Network — SPIN, for short — is a special ARIN account structure that internet service providers historically used to hold and manage address space on behalf of downstream customers. An interim account works differently. It’s a temporary holding account ARIN may create during restructuring events: mergers, acquisitions, transfers of resources between organizations. Both exist for the same underlying reason, though. They preserve the chain of custody for number resources while the final destination is still being worked out.
Where does the distinction actually matter? During transfers, mostly. If a service provider sells address space that was issued under a SPIN, ARIN requires the resources to be accounted for through that structure before they can move to a new resource organization. Interim accounts show up in a different situation: an acquiring company that hasn’t yet established its own ARIN organization ID but needs somewhere to park resources in the meantime. For anyone buying or selling, knowing whether the space you’re transacting sits in a SPIN or interim account directly shapes the documentation ARIN will request — and the timeline you should expect.
Need IPv4 addresses?
Browse clean, RIPE-verified subnets at $0.50/IP/month.
Practical tip: Before initiating any transfer, log into ARIN Online and confirm the account type associated with the resource. If the listing shows a legacy SPIN structure, contact ARIN’s registration services team early. Better to clarify the path forward now than discover it mid-transaction.
Why Does ARIN Require an SPIN or Interim Account for IPv4 Transfers?
ARIN’s core mandate is keeping accurate stewardship records for every IPv4 block in its region. Requiring transfers to pass through a clearly defined account structure serves three purposes:
- Chain of accountability: Each transaction must be traceable from the original recipient to the current holder. Without that, address space can vanish into unregistered hands.
- Policy compliance: Transfers have to meet the criteria in ARIN’s Number Resource Policy Manual, including the requirement that the recipient be eligible for the block size being transferred.
- Fraud prevention: A verified interim account gives ARIN a controlled checkpoint where ownership documentation — merger agreements, purchase contracts — can be reviewed before resources change hands.
Picture a typical scenario. An ISP holding addresses under a SPIN arrangement gets acquired by a larger regional carrier. The carrier hasn’t opened its own ARIN organization record yet. Without an interim account, there would be no legitimate place to register the transferred blocks during the transition — the space would sit administratively orphaned. ARIN’s structure closes that gap, and it protects both parties in the deal.
Step-by-Step: Moving IPv4 Holdings Into an SPIN or Interim Account
Done carefully, the movement of holdings into a transitional account follows a fairly predictable sequence:
- Confirm the source account type. Are the blocks registered under a SPIN, a standard organization ID, or a legacy allocation? Each path carries different documentation requirements, so verify before you do anything else.
- Open the destination account. Submit a request through ARIN Online for a new organization record or an interim structure. You’ll need legal entity documentation — articles of incorporation, acquisition agreements, that sort of thing.
- Compile transfer documentation. Gather the purchase or transfer agreement, proof of eligibility for the block size, and any downstream customer assignments that must be re-registered. This step takes longer than most people expect.
- Submit the transfer request. File through ARIN Online, listing each resource identifier precisely. When a reviewer asks questions — and they often will — respond quickly to avoid processing delays.
- Verify the updated registration. Once approved, check that the whois records reflect the new account and the correct point of contact. Don’t move on to further transactions until you’ve confirmed this.
Working with an experienced marketplace partner can simplify each of these steps. IP4 Market provides a trusted platform for IPv4 transactions, with verified sellers, pre-audited resource documentation, and competitive pricing that reduces the risk of surprises during ARIN review.
Required Documentation and MFTA Considerations
Every ARIN transfer needs a complete documentation package. What exactly goes into that package depends on where the resources are headed: a SPIN or interim account, or directly to another ARIN-registered organization. Either way, both parties should have the following ready:
- A signed, dated purchase agreement or transfer contract that identifies the blocks, the consideration, and who is responsible for what.
- Proof of organizational legitimacy on the recipient’s side — ARIN Point of Contact validation and organization ID confirmation, typically.
- For legacy holders under the 227/1999 transfer restrictions, an RZA (RS-102) submission plus evidence that the transfer doesn’t violate the legacy registry agreement.
- Payment justification details. ARIN charges transfer fees to the recipient and expects the transaction to reflect a legitimate sale or lease-to-transfer arrangement.
At the center of all this sits the Modified Transfer and Acknowledgement Agreement (MFTA). Both organizations sign it — the one transferring and the one receiving — and by signing it the recipient formally acknowledges responsibility for the resources and their registration data. Buyers moving prefixes into a SPIN or interim account should read the MFTA closely before executing it. Once ARIN processes the agreement, there’s no walking back liability: the receiving organization becomes fully responsible for correct WHOIS data, reassignment records, and compliance with ARIN’s Number Resource Policy (NRPM).
Practical tip: Have legal counsel who actually knows number resources review the MFTA before you sign. Clauses covering indemnification for prior misuse, hijacking history, or stale reassignments should be negotiated before the agreement reaches ARIN — not after.
Common Pitfalls, Timelines, and Fees in the ARIN Transfer Process
Even well-prepared transactions hit friction. What goes wrong most often?
- Unvalidated recipient records. If the SPIN or interim account has outdated POC data or an unverified organization profile, ARIN halts processing until everything is corrected. That alone can add two to four weeks.
- Overlapping or contested ranges. Blocks with historical reassignments, RPKI conflicts, or past hijacking reports require extra investigation before ARIN approves anything.
- Mismatched signatures. The MFTA and the purchase agreement must reference identical legal entity names and block lists. Even a small discrepancy triggers a resubmission cycle. It happens more than you’d think.
As for timing: straightforward transactions between verified ARIN organizations usually close within ten business days of submission. Deals involving legacy space or a SPIN or interim account can stretch to three, sometimes six weeks. ARIN charges a recipient-side transfer fee, currently billed per block transferred, and if the buyer sets up new organization infrastructure along the way, additional resource charges may apply.
Working with an experienced intermediary cuts these risks down considerably. IP4 Market pre-screens sellers, verifies block histories, and coordinates documentation before submission — which shortens review cycles and keeps buyers out of expensive resubmission delays.
Conclusion: Transferring IPv4 Holdings With Confidence
Moving IPv4 space into a SPIN or interim account is a well-defined process under ARIN’s rules. But it rewards preparation. Know the difference between interim transfer recipients and SPIN-registered holders. Assemble a clean documentation package. Execute the MFTA correctly. Anticipate ARIN’s review timeline. Do all that, and the closing goes smoothly.
For network engineers and IT managers working through their first acquisition — or ISPs scaling up their address inventory — partnering with a knowledgeable marketplace is often what separates a three-week transfer from a three-month ordeal. IP4 Market offers verified sellers, pre-audited resource documentation, and competitive pricing, so buyers and sellers can complete ARIN transfers efficiently and with some peace of mind.
Need IPv4 space? Lease RIPE-verified /24–/22 subnets at a flat €0.50/IP per month — LOA + RPKI/ROA in minutes, instant company verification, automatic renewals. Browse available subnets →