Summary

  • A 2021 request asked ARIN to let an organization block incoming detailed reassignments and reallocations made against its Org ID. ARIN implemented the control in January 2026.
  • ARIN first planned to turn incoming records off by default. A November 2024 count of 255,535 Org IDs with multiple incoming records changed its mind: the released switch starts on, and the recipient must close it.

A name can be borrowed without taking its address

The 2021 suggestion came from an anonymous operator with a precise complaint. Someone else could make an address block appear under its Org ID in Whois, borrowing the organization's reputation. The operator wanted a lock, even if only ARIN's help desk could set it. ARIN agreed the improvement had merit in September 2021. Its closeout, dated 24 August 2026, says the function had been deployed earlier that year.

That five-year queue matters because a registry record is a public assertion. An incoming detailed reassignment or reallocation links a holder's block to a receiving organization. Readers of the directory may see the recipient's name and mistake the association for endorsement. At ARIN 57 in April 2026, John Sweeting described the case of a block reassigned to a large cable provider so a Whois lookup would appear to implicate that provider. Reese Radcliffe added an awkward detail: some cases were confused customers who thought an upstream provider should be recorded as the recipient. The registry had a fraud problem and a comprehension problem wearing the same database shape.

The 60.7% reversal

ARIN's 6 November 2024 announcement proposed a per-Org ID control with incoming reallocations disabled by default. Existing recipients would have to opt in. Two weeks later, ARIN changed the default. Its count found that 255,535 of 421,022 Org IDs, or 60.7%, had more than one reallocation or detailed reassignment. Requiring that large population to switch reception back on would interrupt ordinary record keeping. The new plan kept reception on and made closing it a deliberate act by the recipient.

The current ARIN guide confirms that this is the January 2026 product, not a proposal left in a meeting folder. All Org IDs accept incoming records by default. An Admin or Tech Point of Contact can change the setting in ARIN Online. The REST Org Payload exposes acceptReassignments; a Reg-RWS attempt to reassign or reallocate to a closed Org ID returns HTTP 403. A recipient can reopen the setting for a wanted record and close it again.

ARIN has published no count of Org IDs that actually closed the switch or of attempted records rejected after release. Those figures would tell us how much protection the design delivers in use. The default tells us where ARIN placed the first move: with the organization whose name is at stake, after the door has already been left open.