Summary

  • Section 12.6 of the Number Resource Policy Manual gives an organisation at least six months to effect a return, except in cases of fraud or violations of policy; section 12.3 requires ARIN to communicate that a review has concluded, but the reviewed text states no separate advance-notice interval before revocation.
  • ARIN's published Appeal Process — 30 business days, escalated through Registration Services, the RSD Director and the Chief Experience Officer before it reaches the President and CEO and the General Counsel — is written for decisions on number-resource requests. The only express route a holder has against a termination or suspension is section 14(k) of the Registration Services Agreement: 30 days of negotiation, then binding arbitration before a single arbitrator.

Two instruments decide whether a block survives. American Registry for Internet Numbers publishes both, and they answer different questions. The policy manual says when a resource review can start, what standard decides it and how long a holder gets to move its network. The Registration Services Agreement says what happens when money, services or the agreement itself is at stake — and, crucially, who hears the argument afterwards. Reading one without the other produces the wrong clock and the wrong forum.

The six months is not a notice period

The manual's version 2025.1, dated 3 March 2026, sets the review machinery in section 12. A review can be triggered by a new resource request, by suspected fraudulent or policy-inconsistent acquisition, by suspected noncompliance with reassignment or reallocation rules, or without cause — the last only where a full review has not occurred in the preceding 24 months (Number Resource Policy Manual).

Section 12.3 then requires ARIN, after a review in which it solicited information from the holder, to say that the review has concluded and to identify further actions. The standard is material noncompliance with current policy, and the reviewed text leaves how long an organisation may remain out of compliance to ARIN staff's reasonable judgment, balancing utilisation, the available address pool and the wish to avoid near-term additional requests or unnecessary route de-aggregation.

That is the interpretive soft spot, and it is written in deliberately. When policy says staff judge, the first characterisation of a holder belongs to staff. The six-month sentence that follows does not move it earlier; it governs what happens after the characterisation, and the manual scopes it precisely: "Except in cases of fraud, or violations of policy, an organization shall be given a minimum of six months to effect a return." ARIN may negotiate longer where an organisation is acting in good faith to restore compliance and needs time to renumber.

Three limits sit in the same section and matter to anyone testing a conclusion. Legacy address space gets no additional revocation authority from this policy, though its utilisation may count when overall compliance is assessed. A policy timeframe cannot be used to measure noncompliance before that timeframe has elapsed. And under section 12.7 services continue while a return or revocation is pending — but maintenance fees are calculated as if the return or revocation were already complete. The holder keeps working during the period it is being asked to plan its exit; the invoice does not.

The other clock runs on invoices

The contract carries a separate timeline. Section 4(c) of Registration Services Agreement version 14.0, dated 15 August 2025, issues the invoice at least 30 days before its due date, then a delinquency notice if it goes unpaid, then a final delinquency notice after another 30 days, along with reasonable telephone contact efforts. Services may stop after the final-notice period. Termination and revocation of the Included Number Resources become available where an invoice remains unpaid six months after payment was due — the agreement's words being that ARIN may "terminate this Agreement and revoke the Included Number Resources" (Registration Services Agreement).

ARIN's operational page runs a faster, simpler schedule: services stop at 120 days past due, and at 180 days past due "ARIN will terminate the ARIN Registration Services Agreement," revoke the included resources and return them to inventory for reissue (Resource Revocation, Returns, and Reinstatement). Neither reviewed document reconciles 120 and 180 days past due with six months after the due date. ARIN's own FAQ states that it does not alter or modify RSA terms, so the agreement remains the anchor and the page reads as an operational claim about how the schedule is run (RSA FAQs).

Do not merge the two clocks. Six months to effect a return after a compliance finding is remediation time. Six months after a due date is delinquency time. A holder can be inside one and nowhere near the other, and the remedies differ.

What the contract actually gives back

Section 6 is the most useful sentence in the agreement for a holder accused of sitting on space: except as provided, ARIN will not reduce current services or revoke Included Number Resources solely because of lack of utilisation. It may still refuse transfers or additional allocations where existing resources are not used in accordance with policy. Idle space is not, by itself, a revocation ground.

Termination mechanics matter more. Section 13(b) lets ARIN suspend services without notice for listed breaches, including sections 2(c), 2(d), 4 and 7, and terminate immediately with written notice for nonpayment or material breach of those sections. Other uncured breaches get a 60-day cure period after written notice. Section 13(c) gives the holder a for-cause exit after specified breaches remain uncured for 60 days — but if ARIN disputes the asserted cause, the holder must obtain an arbitrator's determination under section 14(k) before terminating.

Legacy resources revert to legacy status on that route; resources ARIN issued are returned. Under section 13(d) a voluntary return needs written notice and ARIN accepts it 30 days later. Under section 13(e), apart from those two circumstances, termination immediately revokes the Included Number Resources and ends services, while fees through the termination date stay payable.

Restoration is graded by timing. Before revocation, bringing the account current restores service. After it, the holder needs the resources to be unreissued, the required amounts paid, qualification under current policy and a signature on the then-current agreement.

Where the argument goes

Section 13(b) says the holder may use section 14(k) to dispute an ARIN termination or suspension. Section 14(k) then sets the sequence: cooperative settlement negotiations first; if they fail, or do not occur within 30 days after initiation, either party may require binding and final arbitration. For a holder with its principal place of business in the United States, that is Washington, D.C., under American Arbitration Association rules, before a single arbitrator, with the award enterable in a competent court.

The courthouse door is narrow and named: either party may seek a temporary restraining order, preliminary injunction or other injunctive relief to preserve the status quo in the United States District Court for the Eastern District of Virginia or the Circuit Court for Fairfax County, Virginia, while the dispute proceeds under section 14(k).

The appeal that reads like the obvious remedy is a different instrument. ARIN's Appeal Process version 3.0, dated 19 May 2025, is expressly for ARIN decisions regarding number-resource requests and applies to first-time and returning applicants (ARIN Appeal Process). It has an escalation ladder — Registration Services, then the RSD Director, then the Chief Experience Officer — and then a written appeal by the registered Admin POC to the President and CEO and the General Counsel within 30 business days after the denial notice. It says it follows the provisions of the Registration Services Agreement. Nothing in the reviewed scope language extends it to a revocation that follows a completed section 12 review.

So the two routes are not interchangeable. One is a request-appeal ladder with named officers and a 30-business-day deadline. The other is a contractual arbitration clause with a 30-day negotiation trigger, one arbitrator and a two-venue interim-relief carve-out. A holder who reads only the first will miss the deadline that actually governs.

Know which agreement you signed

The posted agreement is version 14.0. Section 14(l) says a holder is not required to adopt a subsequent version, and the FAQ confirms that organisations are not required to update their RSA when ARIN publishes a new one. That makes the operative dispute route version-bound: the posted text is the current default, not proof of what any particular holder agreed to. Which version governs a specific holder is not established by these documents, and the difference is not academic — the arbitration clause, the cure periods and the restitution language all live in the version actually in force between the parties.

What a holder can actually control

The division of labour is the point. Staff decide whether there is material noncompliance, and the standard is their reasonable judgment. An arbitrator decides whether a termination or suspension survives, if the holder moves. Court access exists to hold the situation still, not to hear the merits. Sections 6 and 12.8 are the express limits on what staff judgment can be used to reach, and they do not depend on the appeal route's scope at all.

That leaves a holder with three questions worth answering before spending money on a transfer. Which document decides whether the block is at risk — section 12, applied by staff. Which document decides who reviews the decision — section 14(k), applied by one arbitrator. And which of the two can change without that holder's consent — the posted agreement can, for future holders, while the version already signed does not follow it upward.