Summary

  • ARIN's posted registration agreement and its policy manual both print six months over the same act — taking a holder's registration away — and the two periods measure different events, one running from a payment due date and the other from a request to return addresses.
  • The agreement names itself the winner wherever the two texts conflict and lets ARIN rebind holders to a rewritten manual upon publication, so which clock governs an individual holder depends on which document is invoked, and no single cure date can be computed from the public pair.

Start with the invoice. ARIN's Registration Services Agreement, posted as Version 14.0 dated 15 August 2025, gives a holder a sequence rather than a deadline: an invoice at least thirty days before payment is due, a Delinquency Notice, thirty days to pay, a Final Delinquency Notice with reasonable efforts to reach the holder by telephone, thirty more days. After that ARIN may stop providing Services. And if any invoice remains unpaid six months after payment was due, it may terminate the agreement and revoke the included number resources.

That six months is a duration measured from a date the holder already knew: the due date. It is not a grace period after a warning, and the subsection supplies no appeal to anyone outside ARIN. It offers restoration instead — bring the account current before revocation, or reapply for resources that were revoked and not reissued, on an additional fee and the agreement then in force.

Now the other six months. Section 12 of the Number Resource Policy Manual governs resource review. It opens the whole database to review, then lists the ways a review begins: a new resource request, a belief that resources were obtained fraudulently or against policy, a belief that reassignment or reallocation rules are not being followed, or, plainly, "at any other time without having to establish cause unless a full review has been completed in the preceding 24 months." When a review ends, ARIN tells the organisation what further actions, if any, are required. An organisation found materially out of compliance "shall be requested or required to return resources," and the permitted degree of non-compliance rests on "the reasonable judgment of the ARIN staff."

Then the sentence that matters here: "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." And immediately after it: "Except in cases of fraud, or violations of policy, an organization shall be given a minimum of six months to effect a return."

Read that carefully, because it is not the same instrument as the invoice clock and it is not a cure window either. The period is time to move addresses off a network and renumber the customers behind them. It begins when the organisation is given it, and section 12 prescribes no form, no delivery method and no dated notice for that communication. The runway can be extended if ARIN believes the organisation is working in good faith and needs more time to renumber, and it can be withdrawn altogether in cases of fraud or policy violations — a determination the same section assigns to no one else.

So the two six-month periods diverge at the only point that would let a reader compute anything. One has a printed start: the payment due date. The other has a printed length and an unpriced start. And a third period sits in neither of those places: the sixty days in the agreement's termination clause, which applies when a holder breaches "any other provision" and the breach remains uncured for sixty days after ARIN's written notice, with cure judged "as determined by ARIN in its reasonable determination."

That sixty-day window is the closest thing in either document to a conventional cure period, and it is drawn narrowly. The same clause allows suspension without notice at all for breaches of four enumerated sections, and immediate termination on written notice for non-payment, for material breach of three named sections, or under a further provision. Enumerate enough breaches and the residual sixty days covers what is left.

Where the two texts disagree, the agreement says which one wins.

Section 1(c) incorporates the manual and ARIN's other policies, calls the pair the "Service Terms," and then states the rule: "In the event of any inconsistency between the Policies and this Agreement, the terms of this Agreement will prevail but solely to the extent of the inconsistency." Section 5 repeats the hierarchy in the middle of the amendment power, obliging compliance with the policies "except to the extent the Policies conflict with the terms of this Agreement." Section 14(c) says it a third time, incorporating the policies "to the extent they do not conflict with this Agreement."

The manual does not answer back. Its only located reference to the agreement is definitional: resources issued under ARIN policies are subject to a contractual agreement, and all past and future forms of that agreement are called the Registration Services Agreement. Nothing in section 12 names the agreement as controlling over the manual. A hierarchy stated three times in one document and zero times in the other is still one instrument talking.

Section 5 makes the hierarchy move. ARIN "may at any time in its sole and absolute discretion amend the Policies, implement new policies ... or revoke existing Policies," and those changes bind the holder "immediately upon publication on ARIN's Website." So the runway in the manual is not a floor the community controls; it is a term the agreement imports on condition, and the same instrument holds the pen that can rewrite the condition.

Here is what a reader holding only these two public documents can actually compute. Our arithmetic, not ARIN's: sixty days is sixty days. Six months is not printed as 180 days anywhere in either text, and neither document sets out how months become days. The invoice clock can be reconstructed backwards from a due date, if you have the invoice. The compliance runway cannot be reconstructed at all without knowing when the organisation was given it, and the manual does not require that moment to be written down anywhere a holder could later point to.

That is the missing quantity, and it is not a period. Every duration is printed. What is missing is the start event: which instrument ARIN invokes, on what date, in what document. A holder who receives a review finding and a fee demand in the same quarter is inside two clocks with two different triggers and no printed rule reconciling them, because the reconciliation rule lives only in the contract.

One smaller discrepancy is worth recording because it is exactly the kind of thing a reader would otherwise trip on. The manual's HTML copy and its PDF copy both carry the 3 March 2026 date, but the PDF is labelled Version 2026.1 and the HTML copy 2025.1. Section 12 reads the same in both. The label is a publication artefact; the text is the text.

Three boundaries on all of the above. Both documents were read on 21 November 2026 through page-text renderings of ARIN's own published files, not a continuous browser read of either PDF, so clauses outside those passages were not inspected. The posted agreement is Version 14.0, and individual holders may still be governed by older versions — which version binds a particular holder is not established by the posted text. And no revocation notice, case file or arbitration award was obtained, so nothing here describes how ARIN has applied section 12 to any holder, or what any holder did.

What would make this pair auditable is not a longer period. It is one printed line in the review procedure: the date on which the organisation was given the return runway, in a document the organisation holds too. Until that exists, the answer to "how long does a holder have?" depends on which of ARIN's two documents is speaking — and the agreement has already said which one speaks loudest.

ARIN's own entry in our directory records the operator behind the registry: American Registry for Internet Numbers.