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
284Stories
Story
One Revoked Certificate, Three Browser Outcomes at APNIC 62
The certificate was on the revocation list. That was not the end of the story. Geoff Huston's APNIC 62 demonstration put the same adverse record in front of three browser policies and obtained different results—a useful warning about the distance between publishing a security…
Story
APNIC’s Twin 28-Minute Incidents Need a Correlation Receipt
Two MyAPNIC incidents ended after exactly 28 minutes within roughly 49 hours. APNIC gave each a bounded explanation; it has not publicly said whether their dependency paths were compared.
Story
Presto Leaves Applications Unchanged. Its Peers Still Have Conditions
Presto’s POSIX layer can preserve the application’s familiar socket boundary. The published prototype nevertheless asks operators to condition the NIC and every peer that meets it on the wire.
Story
APNIC Wants Login to Read the Current IRT Email State
An account should not inherit yesterday’s lock answer when today’s IRT contact state says something else. APNIC’s 2026 roadmap proposes replacing reliance on a static account lock flag with a login-time check of continuously tracked IRT email validity. That is a small sentence…
Story
India Opened Lower 6 GHz. APNIC 62 Still Needed a Client Receipt
The band could be lawful, the access point could contain the right radio, and a device could still never see the network. APNIC 62 turned that gap between authorization and usable capacity into an operational record—but not yet a reproducible one.
Story
APNIC’s Two-Nameserver Run Had Fewer Repeats. The Difference Still Needs a Reproduction Receipt
APNIC measured fewer authoritative DNS queries in a later run using two nameservers than in an earlier run using one. The observation is real in the published aggregates; the cause is not settled. A reproducible decision needs the two treatments to share a clock, cohort and…
Story
APNIC's RDAP Use Is 20%. That Is Not an Adoption Rate.
APNIC's new survey puts RDAP at 20% among respondents asked about core registry services. The number is useful evidence about reported use; it is not a census of deployed systems, a traffic share or a verdict on whether RDAP can replace WHOIS.
Story
APNIC Says prop-170 Reached Consensus. APNIC-127 Still Does Not Say “Nibble”
On 14 September, two official APNIC pages described prop-170 as having reached consensus at APNIC 62. A third official page still labelled it “For Discussion at APNIC 62 OPM”. The operative policy supplied a more important answer: APNIC-127 still contained the old IPv6 allocation…
Story
TWNIC’s Table Leaves 68 Completions Beyond Its 30-Day Gate
A 328-member validation ledger closes arithmetically, but its cumulative milestones imply 68 completions after the access-restriction threshold without showing which controls were used.
Story
ISIF Now Starts With a Concept Note. The Foundation Performs the First Review
A shorter opening application can widen access to Internet-development grants. It does not make the entire selection sequence an independent committee decision—and the 2026 rules do not claim that it does.
Story
APNIC 62’s OTC Warning Is Also a Looking-Glass Problem
BIRD can stop a leaked route before ordinary filters have an entity to retain. The September warning asks for more than softer rejection: an explanation that survives without giving the route permission to travel.
Story
APNIC’s Volunteer Leadership Has a Cost Before the Ballot
APNIC’s leadership consultation identifies a barrier that an election cannot remove: somebody must make the working day available. Published EC guidance distinguishes unpaid service from reimbursable expenses. The harder question is how to support participation without turning…
Story
APNIC Will Put VRP History in REx. A Timeline Still Needs a Vantage Point
APNIC plans to show current and historical RPKI VRP information for an individual Internet number resource in REx. That could turn a specialist dataset into useful public memory. But a dated line is not self-explanatory: unless it names the observation, derivation and scope…
Story
IRINN’s 13 Webinar Bars Sum to 3,567. The Same Slide Says 5,000+
IRINN’s APNIC 62 update offers an unusually useful test of capacity-building evidence: thirteen visible webinar counts reconcile exactly to 3,567, while a footer on the same page reports more than 5,000. Both may describe real activity, but the public record does not say whether…
Story
APNIC’s 53% Willingness-to-Pay Signal Has No Price Attached
APNIC found a majority willing to consider paying extra for premium support—but only inside a preselected group, and without naming the price or the service bought. That makes 53% a reason to ask the next question, not an answer to it.
Story
APNIC Has an ASN Endpoint and an Empty Changelog. They Do Not Prove the Same Release
APNIC Has an ASN Endpoint and an Empty Changelog. They Do Not Prove the Same Release intelligence summary explains the development, the public evidence available to readers, the organisations involved, the regional context, market exposure, and the infrastructure consequences…
Story
A Correct RIR Record Did Not Fix One Geo-IP Error After Two Months
An APNIC 62 case study exposed a small but consequential accountability gap: the registry data could be right, several geolocation databases could agree, and one downstream service could still send a customer to the wrong country.
Story
APNIC’s Priority Survey Has Three Bases: 1,039, 1,038 and 1,037.
APNIC asked its community to divide exactly 100 points among eight strategic activities. The resulting chart looks unusually complete: every point is accounted for and no priority overwhelms the rest. The publication trail is less settled. Three official artifacts attach three…
Story
BCAP’s Prize Entry Preceded Training. Its Outcome Receipt Has Not.
The WSIS Prize submission window closed two days before BCAP’s published professional-development start window opened. The project won in July and is still listed as ongoing through 2027. The award may be sound; the public record still needs to say which finished phase and which…
Story
APNIC's ASPA Interface Checks Observed Paths. A Standby Provider Leaves No Path to Check.
APNIC has built a sensible safety rail into its new ASPA interface: suggest providers from visible routing data, then show how an edit would affect paths that BGP observers can see. The awkward provider is the one hired precisely not to be visible yet. A standby link turns the…