ARIN · RIR Watchdog
Story
BTW reporting and context linked to this RIR. For the proposal-by-proposal history, the people involved and their changing positions, start with Policy.
Story
Latest stories
345Stories
Story
ARIN’s RPKI Failover Test Left the Dependency Question Open
ARIN blocked access to its RPKI repositories for an hour, restored it, confirmed redundancy five minutes later and reported a return to baseline after another fifteen. That is unusually concrete resilience evidence. It is also narrower than the dependency question ARIN had…
Story
ARIN Described a Two-Person Rule for AI Drafts. It Did Not Describe the Receipt
ARIN’s public answer was unusually concrete: generative AI may assist a narrow class of drafts, the drafter remains responsible, and a second person reviews the result before release. The missing piece is not another principle but the durable record that proves those decisions…
Story
ARIN’s Ombuds Reports Reach the Board. The Public Record Does Not Track the Advice
ARIN’s minutes show that outside advice about the safety and conduct of its meetings does not disappear into a ceremonial file: recommendations have changed practice, some have met practical limits, and the Board is now considering the programme’s scope, continuation and…
Story
ARIN Lets You Name a ROA. Its Online Search Still Ignores the Name
ARIN Lets You Name a ROA. Its Online Search Still Ignores the Name intelligence summary explains the development, the public evidence available to readers, the organisations involved, the regional context, market exposure, and the infrastructure consequences that may follow. The…
Story
ARIN Closed the ROA Wording Fix. The Published Example Drops the Mask Interval
ARIN answered a precise operator complaint in five weeks and marked the documentation repair complete. That is the constructive part of the record. The harder question is why the live example no longer contains the length boundary that made the requested correction capable of…
Story
ARIN Added §4.10 Misuse to Its Fraud Process. Its Form Names Two Other Cases
ARIN now tells the public that misuse of reserved address pools, including space issued under NRPM §4.10, belongs inside its fraud-reporting process. Follow the link to the live intake form, however, and the explanatory copy still names only fraudulently obtained resources and…
Story
ARIN's Retired Origin AS Field Recorded a Possibility, Not a Live Route
Old registration exports can preserve an `Origin AS` value long after ARIN removed the field. The label looks authoritative, but ARIN defined it as an optional holder-supplied list of ASNs from which a block might originate. It was neither a cryptographic authorization nor a…
Story
ARIN’s Whois Retirement Proposal Is a Protocol Transition, Not the End of Directory Data
Three dates in ARIN’s latest consultation can look like shutdown deadlines. They are not. The registry is asking how to retire three older access protocols in favour of RDAP, with separate dependencies and earliest dates for each path. The proposal changes how registration data…
Story
ARIN Adopted an Amended IPv6 Task Force Charter. The Public Index Does Not Show It
ARIN’s Board minutes record the creation of an IPv6 Task Force, an amendment that shortened its planned life, and three people who volunteered to do the work. What the public record does not yet supply is the operative text that joins those facts into a mandate. The missing…
Story
ARIN Closed Its Mailing-List Suggestion With a Prompt, Not a Reach Result
ARIN preserved voluntary choice when it declined to enroll every General Member in a governance mailing list. Its August closure record proves that a prompt reached the membership-request form. It does not yet show how far the list reaches across member organizations.
Story
ARIN’s Incoming-Reassignment Switch Makes Registry Association Consent-Bound
An organization identifier used to be available for an upstream provider’s reassignment workflow unless another requirement failed. Since ARIN’s January 2026 release, the recipient can refuse that association before it is created. The new switch changes registry accountability in…
Story
ARIN Plans ROA Impact Warnings for the Web, Not the API
ARIN is building a warning for the moment before a Route Origin Authorization changes what observed routes look like. The warning belongs to its web interface. The registry’s programmatic writer is still expected to assemble the same evidence elsewhere. That is not a difference…
Story
ARIN’s Off-Earth Address Draft Has Four Locks Before the First Allocation
A proposal can describe addresses beyond GEO, but a registry service cannot begin until four separate institutions settle four separate questions. BTW recommends making that chain publicly reviewable before operational clauses are treated as ready.
Story
ARIN’s Harmonization Draft Needs a Semantic-Diff Ledger
ARIN-2026-4 presents itself as clarification, but two nearly parallel clauses differ in actor and modal force: the current text says registration “guarantees” uniqueness, while the proposal says a public registry is “necessary” to ensure uniqueness of allocated resources. Those…
Story
ARIN’s Property-Language Proposal Needs a Document-Control Ledger
Deleting one sentence from a policy manual does not settle a rights question. It relocates the reader’s evidence path. ARIN-2026-3 makes that relocation the central governance issue: if NRPM Section 6.4.1 is retired, readers need a reliable way to find the proposition that…
Story
ARIN’s Plan-Based IPv6 Policy Needs a Decision Ledger
Removing a sizing equation from a policy book does not remove the allocation decision; it moves that decision into an analyst’s reading of a network plan. ARIN-2026-2 would replace several formula- and utilization-based mechanisms with planning-based evaluation. The key question…
Story
ARIN’s Proposed /24 Out-of-Region Rule Needs an Exposure Ratio
Moving the threshold from /22 to /24 would make the qualifying in-region IPv4 footprint sixteen times smaller. That change makes the relevant control question proportional: how much in-region footprint supports how much out-of-region space?
Story
ARIN’s 4.10 Regional Boundary Needs a Grandfathering Ledger
ARIN’s proposed geographic clarification is brief, but its durable test is temporal: every Section 4.10 decision should be traceable to the policy version and effective date that governed it.
Story
ARIN’s IPv6 draft separates the /48 starting point from the scale-up formula
Recommended Draft Policy ARIN-2025-7 is a narrow wording change with a practical test: whether every justified site count produces one predictable, nibble-aligned IPv6 allocation without changing eligibility.
Story
The New RIR Draft Says Enforceability Does Not Wait for the Procedure
Article 1.3 of the new RIR Governance Document draft says a missing common implementation procedure does not stop the document from being enforced. The next clause, added in Version 3, says a decision must still follow the procedure relevant to the entity making it, including any…