Summary

  • ARIN reaches revocation through two different doors: its registration services agreement revokes only as a consequence of terminating the agreement, while its number resource policy manual revokes directly for material noncompliance found in a resource review. Neither document ranks the other.
  • The last dated, period-bounded revocation figures located in ARIN's public record end at 30 September 2011. Current ARIN reporting counts requests and inventory instead of outcomes.

Revocation is the moment a registry stops being a records office. It is where an administrative finding turns into the loss of addresses that an operator's routing, customers and contracts rest on. ARIN, the registry for the United States, Canada and parts of the Caribbean and North Atlantic, prints that power in two documents that two different readers hold: the agreement a resource holder signs, and the manual a policy participant amends.

As reported in the version retrieved for this review, the registration services agreement, version 14.0 dated 15 August 2025, puts revocation downstream of termination — "if this Agreement is terminated, then (i) ARIN will immediately revoke the Included Number Resources and otherwise cease providing the Services and will have no liability for doing so" (ARIN registration services agreement, version 14.0).

The same agreement then narrows its own reach. Section 6 provides that ARIN "has no right to revoke Included Number Resources under the Agreement due to lack of utilization", while reserving the right to refuse transfers or further allocations where resources are not used in accordance with policy. Read the scope terms, not the headline. The denial lives under the Agreement.

The policy manual takes the other door. In the section 12 text returned from version 2026.1 dated 3 March 2026, if an organization does not voluntarily return resources, "ARIN may revoke any resources issued by ARIN as required to bring the organization into overall compliance" (Number Resource Policy Manual). No termination is required. The trigger is material noncompliance found in a review, and section 12.4 hands the degree of permitted noncompliance to "the reasonable judgment of ARIN staff".

So one act has two trigger sets. Nothing in either retrieved text says which instrument governs where a utilization shortfall is simultaneously a policy requirement: the case that section 6 of the agreement addresses and section 12 of the manual also reaches. Section 12.8 partly answers a neighbouring question, creating no additional authority to revoke legacy address space, but it expressly keeps legacy utilization inside the overall compliance assessment.

Three clocks, and none of them is the other one's

The agreement's clocks come first. Section 13(b) lets ARIN suspend services without notice for named breaches, terminate immediately for the fee and material-breach grounds it lists, and terminate for any other breach only if it stays uncured for sixty days after written notice. Section 4(c) builds a separate fee clock: a Delinquency Notice, a Final Delinquency Notice thirty days later, a right to stop services thirty days after that, and termination with revocation where any invoice remains unpaid six months after payment was due.

The manual's clock is a different animal. Section 12.6 gives an organization a minimum of six months "to effect a return", then removes it — "[e]xcept in cases of fraud, or violations of policy". The exception covers the category that triggers the process in the first place, and that is a drafting problem inside one paragraph rather than a reader's misreading. Section 12.3 requires ARIN to say that a review is concluded and what further action is required, and specifies no written form, no delivery method and no interval before a revocation.

Section 12.7 keeps services running while a return or revocation is pending — and calculates maintenance fees as though the return were already complete.

The operational page carries the third clock and dates nothing. It prints 120 days past due for stopping services and removing resources and records from Whois and RDAP, and 180 days past due for terminating the agreement, revoking the included resources and returning them to available inventory, with the process run every Tuesday (Resource Revocation, Returns, and Reinstatement). That 120-day stop arrives later than the agreement's own permission to stop services thirty days after a Final Delinquency Notice. The page reads as an implementation of the agreement and reconciles itself to neither the agreement nor the manual. With no publication date in the retrieved text, nothing says when that schedule took effect or whether it still runs as printed.

One manual, two version labels

The manual's two renderings disagree about what they are. The PDF labels itself version 2026.1 dated 3 March 2026; the plain-text rendering labels itself version 2025.1 on the same date, and the section 12 wording returned from both is identical (plain-text rendering). Either the label lags the text or the text lags the label, and no page read for this piece explains which.

What ARIN used to count

ARIN has published period-bounded revocation figures. A staff update given at APNIC 28, hosted on APNIC's conference site and authored by ARIN's then chief executive, reports for January 2005 to 31 July 2009: 3,852 ASNs revoked and 533 IPv4 blocks revoked, the blocks totalling 84.3 /16 equivalents (ARIN update, APNIC 28).

A staff presentation at ARIN XXVIII carried the second table, for 1 January 2005 to 30 September 2011: 461.78 /16 equivalents and 1,618 ASNs returned voluntarily; 120.93 /16 equivalents and 4,665 ASNs revoked; 7.06 /16 equivalents and 15 ASNs reclaimed (Registration Services Update, ARIN XXVIII). The slide carries its own key. Returned means voluntarily by registrant. Revoked means, in the slide's own words, "For non-payment". Reclaimed means "For fraud, misappropriation, or business dissolution". These count resources, not events, notices or organizations.

Now my own subtraction, labelled as mine. Both tables key from 1 January 2005, so their difference describes 1 August 2009 to 30 September 2011: 4,665 minus 3,852 is 813 ASNs, and 120.93 minus 84.3 is 36.63 /16 equivalents. That is arithmetic on two ARIN tables, not an ARIN figure, and it inherits every difference between what the two slides counted.

What ARIN counts now

No document read for this piece carries a revocation series past 30 September 2011. What ARIN publishes is throughput. The Registration Services Department report presented at ARIN 57 on 22 April 2026 prints 2025 volumes of 1,555 ASN requests, 1,339 IPv6 requests and 2,780 transfer requests (ARIN 57 registration services report). The 2025 annual report prints 1,555 total ASN requests and 1,922 total IPv4 requests (2025 annual report). The statistics index presents charts aggregated by month for the current year — delegations, requests by category, reserved pool status, transfer requests, transfer tickets processed — with no revocation or non-renewal series visible in the retrieved text (Statistics and Reporting).

A 2017 policy suggestion response records a commitment to a biannual report on active and inactive ASN inventories and prints inactive inventory of 1,019 two-byte and 44 four-byte ASNs (ACSP Suggestion 2017.14). That is a stock, not a flow. How many numbers sit unused at a moment says nothing about how many were taken back, from whom, or on which trigger.

The word splits in ARIN's own documents

Three statements, three cuts. The 2011 slide defines revocation as non-payment and files fraud under a different noun. Section 12.5 uses revocation for material policy noncompliance. And in July 2022 ARIN's chief executive wrote on the public policy list that revocations can occur for violations of the policy manual "for any resource in the ARIN registry" and/or violations of a registration services agreement (ARIN public policy list, July 2022); the post does not address section 6's no-revocation-for-lack-of-utilization clause.

A specific enforcement outcome has been reported too. An account published by APNIC on 22 May 2019 describes a scheme to defraud the community of approximately 735,000 IPv4 addresses across 11 companies, and an arbitration award "which allows ARIN to revoke all of the resources held by the defrauding entities" (Taking a hard line on fraud). It does not say whether, when or to what extent revocation followed.

Where a stranger's reading stops

Set the documents side by side and ask what a person holding one revoked block can establish from published pages. Which instrument was invoked? Both produce the same visible result and print different triggers. Which clock ran? Three schedules, one of them undated. Who decided? Staff judgment on permitted noncompliance, with no named officer, committee or appeal in the retrieved text. Which dated record confirms the outcome? None read here joins a trigger, a period and a resource to a decision.

That is the finding, and it is a legibility finding rather than a charge. It does not say any revocation was wrong, arbitrary or unreviewed. It says the papers do not let an outsider reproduce the act. The standard we apply is plain: an institution holding a lever over resources other people have built businesses on owes a relying reader a printed clause, one trigger set, one clock, and dated records labelled by trigger of what it actually did. ARIN prints the clause twice, and printed the records once. The clause-only half is what a reader gets today.

One provenance fact belongs with the quotations. These are ARIN's own words as returned by the text extraction made for this review, not a page-by-page audit of the publisher's files, and ARIN's pages state ARIN's position rather than an independent account of its practice.

What would have to change

Two things, either of which would move this from a documentary gap to an auditable record. First, a dated series — period, counted noun, trigger label, instrument invoked — issued on a schedule, the way ASN inventory issues twice a year. Second, one sentence in one instrument that ranks the agreement against the manual for a single act. Neither is exotic, and both are cheaper than the ambiguity they retire.

The American Registry for Internet Numbers is in our directory.