APNIC · 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
292Stories
Story
A Locally Served DNS Root Has a Refresh Bill
Serving the root zone beside a recursive resolver removes many outward queries, but it does not remove network traffic. A new measurement highlighted by APNIC shows that the bill moves into the update loop—and that software behaviour can matter more than the name of the…
Story
APNIC proposal tests a one-/24 IPv4 bridge for IPv6-only networks
APNIC prop-165 version 4 would let an organisation eligible for an initial IPv6 allocation request one IPv4 `/24` for transitional functions in an IPv6-only deployment. The proposal is still under discussion: its practical significance lies less in the size of the grant than in…
Story
APNIC’s RDAP Registrant Role Identifies a Registration Party, Not Corporate Ownership
One word inside a nested APNIC record carries real evidentiary weight, but less than its everyday meaning may suggest. The RDAP role `registrant` identifies the entity recorded for a registration; it does not turn the response into a corporate-ownership register or a live map of…
Story
APNIC prop-164 Turns Smaller IPv6 Allocations into a Reservation Test
APNIC prop-164 would let account holders begin with IPv6 allocations smaller than `/32` while preserving room for growth. The proposal may improve Whois and RDAP accuracy, but its durable test is whether reserved address space becomes a visible, reviewable registry commitment…
Story
APNIC's Larger IPv4 Delegations Need a Queue Rule Before a Bigger Ceiling
APNIC's prop-168 would let eligible account holders grow toward an aggregated /22 while proposing a separate /12 transition reserve. The proposal defines who may ask and how much they may receive; its own scarcity arithmetic shows why it must also define who goes first when…
Story
APNIC’s RDAP objectClassName Defines a Schema Class, Not a Network Role
The label `ip network` appears near the top of an APNIC RDAP response. It is easy to read it as a description of what an organisation does. Its real purpose is narrower and more useful: it tells software which RDAP entity schema it is processing.
Story
APNIC prop-170 Must Price the Space Between IPv6 Need and Nibble Alignment
A technically valid IPv6 prefix is not always an easy unit to operate. APNIC prop-170 would let an LIR request the smallest nibble-aligned allocation that satisfies an already validated need. The proposal promises cleaner plans without abandoning needs-based allocation; its…
Story
APNIC's IPv4 Needs Test Should Match the Delegation Under Review
APNIC prop-169 would replace a fixed `/23` reference in an IPv4 LIR usage-plan test with the delegation actually being assessed. It is a narrow wording repair, but it matters because evidence should measure the request an applicant is making, not a larger block the policy no…
Story
APNIC’s RDAP Active Status Describes a Registry Object, Not Route Reachability
The word `active` looks like an operational verdict. In an APNIC RDAP response, however, it belongs to the registered entity—not to a live measurement of routes, packets or services.
Story
APNIC prop-174 Turns an Abuse Mailbox into a Policy Control Surface
APNIC’s prop-174 would move abuse-mailbox operations from implementation practice into explicit policy. That can make contact duties measurable, but it also makes delivery, filtering, triage and response records part of a chain that may eventually reach membership consequences.
Story
APNIC’s Automation Workshop Has a Second Job: Teaching Its Successors
The Mumbai course is meant to prepare engineers to teach and rebuild their own training labs. That makes it part of a practical handoff before network automation leaves APNIC’s instructor-led curriculum at the end of 2026.
Story
APNIC REx: When a Date Becomes a Matching Key
Three historical address records changed their dates without changing their ranges. The case shows why reconstructing a resource's past also requires understanding the past of the fields used to identify it.
Story
APNIC's Directory Terms Proposal Turns Query Access Into a Governance Question
Prop-173 would replace ambiguity around ordinary APNIC WHOIS and RDAP queries with a public, versioned acceptable-use policy. The consequential question is not whether terms should exist, but whether their rules distinguish legitimate operational reuse from a substitute data…
Story
APNIC Can Define Internet Abuse Without Becoming Its Judge
Prop-172 would give APNIC policy a common vocabulary for abuse involving IP addresses. Its usefulness depends on a harder boundary: naming conduct must not quietly become authority for the registry to decide allegations, monitor networks or impose remedies.
Story
APNIC Logged 57,088 Addresses as M&A Transfers. Its Daily File Still Shows 2007.
One APNIC file says that nine IPv4 prefixes changed hands on 1 September 2026. The next daily statistics file gives every resulting row the date 3 December 2007. This is not a contradiction or a stale update. It is what happens when an event clock and an origin clock share the…
Story
The RIR Governance Draft Would Freeze Its Own Amendment Path During an Emergency
The newly public Version 3.4 RIR Governance Document does not merely describe how a registry crisis might be handled. It also proposes a small constitutional restraint: while the crisis machinery is active, the machinery's own rules cannot be amended.
Story
APNIC’s Orbit Email Queue Was Delayed for 32 Hours. Its Release Needs a Receipt.
APNIC has recorded the service window and the stuck email processor. That is a useful notice. It is not yet a public account of the transition from a delayed mailing-list queue to a reconciled delivery record.
Story
APNIC’s Five-Year Audit Rule Needs a Public Exception Record
The interesting sentence on APNIC’s transparency page is not the comforting one about a financial audit. It is the operational one: the audit firm is rotated at least every five years. That is a rule a reader can hold in mind. The December 2025 Executive Council minutes then…
Story
APNIC Reissued Four Expired ASPAs. Its Repair Needs a State Receipt.
APNIC has reported a bounded correction: automatic renewal did not run, four ASPA entities expired, and the entities were reissued and published at 11:03. That is useful operational disclosure. It is not yet a measurement of what every repository, validator, router or customer…
Story
APNIC's EC Adopted Topic Shepherds. No Public Charter Says What a Shepherd Can Do
APNIC's Executive Council has chosen a sensible answer to a familiar board problem: give individual members continuing responsibility for important subjects. Its May minutes call them topic “Shepherds” and say they will lead discussions on allocated areas. The missing part is not…