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
346Stories
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…
Story
ARIN-2025-1 turns a terminology edit into a scope migration
The draft calls implementation “Immediate,” while ARIN staff estimate six months for training, documentation, procedures and application updates. These are two distinct source statements, not a contradiction created by BTW.
Story
ARIN Net Type Records Registration Path, Not a Current Customer Relationship
“Reallocated” and “reassigned” look like labels for a business relationship. In ARIN’s registry, they do something narrower: they describe how an address block entered a downstream registration chain and what the recipient intended to do with it. That history is useful, but it is…
Story
ARIN’s IRR Objects Keep the Channel That Created Them
An IRR object migrated from ARIN’s email service can be deleted in ARIN Online but not edited there. The asymmetry is defensible as a record of provenance. The trouble begins when the web remedy—delete and recreate—changes that provenance without a visible continuity receipt.
Story
ARIN's SMS Country List Is Now an Attack-Cost Boundary
A request to make SMS authentication more convenient ended with a security-cost decision. ARIN says the limited numbers it supported outside its service region created a costly attack vector; the public record explains the boundary it chose, but not the attack it measured.
Story
ARIN’s Alternate Whois Link Is a Substitute View, Not Independent Corroboration
One ARIN RDAP record points sideways to ARIN’s older Whois REST service. That link is useful, but it does not turn two views from the same registry into two independent witnesses.
Story
ARIN's RDAP Transition Needs Evidence at Three Different Exit Gates
ARIN wants one standardized directory protocol in place of three older services. The destination is coherent; the operational test is whether Whois-RWS, RWhois and Port 43 can each leave on evidence suited to the users and dependencies they actually carry.
Story
ARIN’s RDAP Remarks Qualify This Object, Not Every Registry Record
Human-readable text inside an RDAP response can look like a general registry instruction. Its location matters. In ARIN’s live entity response, Registration Comments sit inside a particular entity entity, while service terms and reporting notices occupy the response’s top level.
Story
ARIN’s RDAP Notices Describe the Lookup Service, Not the Network’s Operating Policy
The warning labels attached to a registry lookup travel with the answer, but they do not belong to the network named inside it. ARIN’s top-level RDAP notices tell a reader how the lookup service may be used, where suspected inaccuracies can be reported and who claims copyright in…
Story
ARIN’s Reverse-DNS Controls Follow the Parent Block
A customer’s address range does not tell an operator where the reverse-DNS handoff belongs. ARIN’s direct-allocation rules put the editing boundary higher in the tree than a downstream inventory may suggest.
Story
What Comes After ARIN’s Empty Whois Replies
ARIN resolved a problem with some Whois queries in August. For anyone whose tools retained a suspect result, the next task is different: checking the local copy without turning a failed observation into a registration verdict.
Story
ARIN Publishes IPv6 Requests Beside Delegations. The Cohorts Are Not Joined.
An IPv6 request can enter ARIN’s system, pass automatically or move into staff review, prompt a request for more information, receive approval, wait for fees and a signed agreement, and only then become an issuance. ARIN publishes useful numbers at the entrance and the exit of…
Story
ARIN-2025-1 Has Two Official Status Labels. Neither Is Adoption.
One ARIN page records a 25 August Recommended Draft action for ARIN-2025-1. Another places it in the Recommended Draft list while its own status cell says Draft Policy. That public difference is a reason to preserve the record, not a licence to guess which label wins.
Story
ARIN’s Caribbean IPv6 Ranking Needs a Source-Coverage Receipt
The new Caribbean table is useful precisely because it avoids pretending to be a verdict on every network. Its next improvement is equally modest: show which available measurement sources made each jurisdictional average.
Story
ARIN Is Benchmarking a New Survey Against 2023. It Needs a Composition Bridge.
ARIN invited its community to a 2026 customer-satisfaction survey with an explicit wish to compare repeated questions with an earlier survey. That aspiration is sensible. But comparison is not a property of two percentages alone: it needs a public bridge between the two…
Story
ARIN Kept Five Services Running Without Updates. Its Service-Level Report Has No Freshness Column
A registry can answer a question and still have nothing new to say. ARIN's planned July maintenance made that distinction visible: five reader-facing services remained operational while updates were not being published. The public service-level report measures availability well…
Story
ARIN's Two Audit Findings Sound Opposite. They Test Different Controls
One ARIN Board record says no audited ticket was out of policy; another says inconsistencies appeared in every area examined. The difference is not a proven reversal in performance. It is a warning that audit findings become misleading when the test, standard and denominator are…
Story
ARIN's NET Permissions Change With the Lookup Path
One child NET, three ways to identify it, and three different questions about authority. An ARIN community suggestion reported that a direct registrant could reclaim a Detailed Reassignment and retrieve it through an exact address range, but could not use the same API key to GET…
Story
ARIN Put 17,000 Legacy Networks in a Blog Post. The Status Table Is Missing
ARIN has published an unusually concrete warning about the contact records attached to legacy IPv4 space: roughly 17,000 networks, an `about half` risk description, 11% currently validated, another 20% incomplete, and a 76% comparison for resources under agreement. The figures…
Story
ARIN Links ROAs to IRR Objects. Only the ROA Side Has a Visible Action Log
ARIN has made it possible for one routing-security action to leave two related records. That convenience is real. The evidentiary problem begins when the records later separate: the documented public history can explain the ROA, but not yet the whole operation that created…