Summary

  • Section 12.2(d) of ARIN's Number Resource Policy Manual permits a review "at any other time without having to establish cause unless a full review has been completed in the preceding 24 months" — one of four triggers that needs no reason at all.
  • Section 12.6's minimum of six months is time "to effect a return", not time to contest a finding, and the fraud and policy-violation exceptions remove even that minimum.
  • The written delinquency notices and the only plain right to respond — a 60-day cure for breaches other than the listed immediate-termination ones — live in the Registration Services Agreement, not the policy manual.
  • Section 12 requires no publication of an individual revocation decision, and ARIN's own stated reason for withholding revocation-time block lists is anti-abuse: publishing them would let a spammer wash address space by not paying.

A registry's power to hand out addresses is the one everybody watches. The power to take them back is the one written down in the manual nobody reads. ARIN's Number Resource Policy Manual gives reclamation a section of its own — section 12, Resource Review — and it opens with a claim broad enough to reach any holder in the database: ARIN may review the current usage of any resources maintained in its database, and the organisation must cooperate with reasonable related documentation requests (NRPM, section 12).

Section 12.2 then lists the four ways a review starts. Three of them require a reason: a new resource request, a belief that resources were obtained fraudulently or contrary to policy, a belief that reassignment or reallocation rules are not being followed. The fourth does not. ARIN may review "at any other time without having to establish cause unless a full review has been completed in the preceding 24 months." Read that twice. The cooling period is the only limit on the cause-free limb, and it is measured from the last completed full review — so a holder that has never been fully reviewed carries no protection from it whatever. The PDF rendering of the same manual, labelled Version 2026.1 and dated 3 March 2026, carries identical section 12 text (NRPM PDF).

Once a review finds material noncompliance, section 12.4 requires the holder to be asked, or required, to return resources as needed to bring it into or reasonably close to compliance. Section 12.5 supplies the edge: "If the organization does not voluntarily return resources as requested, ARIN may revoke any resources issued by ARIN as required to bring the organization into overall compliance."

Then comes the sentence that decides how much time a holder actually has. Section 12.6: "Except in cases of fraud, or violations of policy, an organization shall be given a minimum of six months to effect a return." Six months to effect a return. Not six months to contest the finding, not six months to produce the paperwork that would overturn it. The clock protects the renumbering project. And the fraud and policy-violation exceptions remove the minimum entirely — the two grounds most likely to be alleged in a hard case are precisely the two where no minimum applies.

ARIN will negotiate a longer term where it believes the organisation is working in good faith and needs more time to renumber, which is a discretion exercised by the registry, not a right held by the holder.

Section 12.3 is where a reader expects a notice duty and does not get one: "At the conclusion of a review in which ARIN has solicited information from the resource holder, ARIN shall communicate to the resource holder that the review has been concluded and what, if any, further actions are required." The duty attaches to the conclusion. The manual specifies no written form, no delivery method and no advance interval between that communication and a revocation.

ARIN's internal procedures may supply those things; this article read section 12 and the documents named here, not those procedures, and draws no conclusion about what they contain.

So the notices a holder could actually argue inside live in a different instrument. ARIN's Registration Services Agreement, Version 14.0 dated 15 August 2025, handles nonpayment with a sequence the policy manual never describes: an invoice at least 30 days before the due date, a delinquency notice, and a final delinquency notice after a further 30 days, with reasonable efforts to reach the holder by telephone. Section 4(c) then authorises ARIN to stop providing services if payment has not arrived within 30 days of that final notice, and to terminate the agreement and revoke the included number resources if any invoice remains unpaid six months after payment was due (RSA).

Section 13(b) is where the only plain right to respond appears. ARIN may suspend services without notice for breaches of sections 2(c), 2(d), 4 or 7, and may terminate immediately on written notice for nonpayment or material breach of 2(c), 2(d) or 7. For any other breach the holder gets 60 days after ARIN's written notice to cure. Notices of termination must be in writing, delivered by hand, by certified or registered mail with return receipt, or by reputable overnight courier.

Section 13(e) adds that, apart from specified routes, termination immediately revokes the included resources and ends services, with fees through the termination date still payable.

Two instruments, two clocks, and only one of them gives a holder a period in which to argue. The policy clock measures a duty to perform. The contract clock measures a right to respond — and that right, the 60-day cure, is available for breaches other than the ones ARIN has reserved to itself for immediate action.

Section 12.7 adds a detail that reads like an accounting rule and behaves like pressure: while a return or revocation is pending, ARIN keeps providing services, but maintenance fees for that period are calculated as though the return or revocation were already complete. A holder pays the post-revocation price during the interval in which it is still contesting the outcome.

Section 12.8 and 12.9 keep the perimeter honest in the other direction: section 12 creates no additional authority to revoke legacy address space, though legacy utilisation counts toward overall compliance, and noncompliance with a policy timeframe cannot be measured until that timeframe has elapsed, with covered blocks assumed compliant until then.

Two states, two dates. ARIN's operational page on revocation, returns and reinstatement states: "Services Stop: If full payment is not received when the invoice is 120 days past due, ARIN stops providing services and removes the resources and the associated record(s) from ARIN's public directory services (Whois/RDAP)." At 180 days past due ARIN terminates the agreement, revokes the included resources and returns them to available inventory; reinstatement is available only if the resources have not been reissued, and then only by reapplying, qualifying under current policy, paying past-due and additional fees, and executing the current agreement (revocation and returns). The register entry therefore disappears a step before the revocation it announces. That is why a registry record and a routing announcement can diverge without anyone behaving improperly — and it is an observation about instruments: no routing measurement was made for this article, and none is claimed.

The operational schedule and the contract do not use the same words for the same interval. 180 days past due is not textually six months after payment was due, and the contract permits stopping services earlier than the page's 120-day point. ARIN's request guide names a different set again — addresses or ASNs may be revoked for nonpayment, voluntarily returned, or reclaimed "in instances of confirmed fraudulent activity or abandonment of resources" (request guide). Abandonment is not a section 12 ground; section 12 speaks of material noncompliance, fraud and policy violations. Three descriptions of one regime, each coherent in its own instrument, none identical to the others. The general guidance page on returns and revocation keeps to process and states none of these notice or response rules (return and revocation process).

Now the question that decides whether any of this is checkable from outside. Section 12 imposes no requirement to publish an individual revocation decision, the identity of the holder, or the reasons for revoking a particular holder's resources. On its own, an absence of that kind is thin evidence of anything. What ARIN publishes instead is more telling. WhoWas, its historical registration data product, records a REGISTRATION REMOVED action when a registration leaves Whois, and its readme explains that ASNs and NETs typically leave the database because they are returned by the registrant, revoked by ARIN for nonpayment, or reclaimed for fraud (WhoWas readme). Those are buckets, not findings. A removal event tells you a registration left; it does not tell you which of the three happened, on what evidence, or who decided.

In 2010 a community member asked ARIN to post removed or revoked resources to NANOG weekly. The response, dated 12 August 2010, declined on the ground that "Removed prefixes are published on a daily basis in the "ARIN Issued" RSS feed" — removals at prefix level, not determinations, and that record says nothing about whether the feed still exists or what it carries today (ACSP Suggestion 2010.9).

Then the sentence that turns an apparent oversight into a priced design decision. On 14 September 2009, ARIN's then chief executive John Curran, posting to the arin-ppml list, explained why the registry did not publish a list of blocks at the time of revocation in addition to the list at reissuance: "this is also why we don't want to publish a list of blocks at the time of revocation (in addition to the one at reissuance) since if RBL's were to remove these blocks on revocation, it would only provide spammers incentive to "wash" their address space by non-payment & then cure" (arin-ppml, 14 September 2009). That is a real threat and a real cost, stated by the registry itself in its own words at the time.

What this adds to what we already carry. Our archive holds 124 articles on ARIN, and a search for "ARIN" returned 25 published pieces: 2025 board and advisory council election results, a candidate forum with voting from 30 October to 7 November, the extension of an NRO Number Council nomination deadline to 14 July 2025, ARIN 56 recaps and registration notices, and a 2 July 2025 distribution of 83 IPv4 blocks from the waitlist. A targeted search for "ARIN revocation" returned nothing. None of that coverage reads section 12, the notice instruments, the return clock, the fee treatment during a pending revocation, or the publication question; those provisions are the ground this briefing stands on. The American Registry for Internet Numbers is in our archive under its own entry (directory).

Judgement, offered as judgement. The writable power here is the shape of the review, not the revocation that ends it. A process that opens without cause outside a 24-month window, measures its six months from the holder's duty to renumber rather than from any right to contest, sets the fee meter to the end state while the outcome is pending, and publishes a removal bucket where a decision would go, is not a process that hides. It is a process built for renumbering speed and abuse resistance — and those two goals are paid for by the outside world losing the ability to audit any single case.

The evidential limit travels with the claim: every quotation here was read on 18 November 2026 from ARIN's published pages through a page-text rendering rather than a browser session, the renderings may be truncated outside section 12 and the quoted clauses, and no individual revocation case, decision or appeal outcome was read in this run.