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
277Stories
Story
RPKI’s Sub-One-Per-Cent BGP Result Is Useful. It Is Not a Stability Verdict.
A peer-reviewed study finds that RPKI-associated updates remain a small share of observed BGP UPDATE volume. That matters, but message volume is only one meaning of network stability.
Story
AS24940’s RPKI Snapshot: 91 Routes, 63 Matches, 49 Broader Permissions
AS24940’s RPKI Snapshot: 91 Routes, 63 Matches, 49 Broader Permissions 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.…
Story
APNIC’s Helpdesk Averaged 7.47 Business Hours. The Average Has a Boundary.
APNIC’s first-quarter report puts two useful service results above their targets: a 7.47-business-hour average Helpdesk response time and 95.5% favorable ratings. The next question is not whether those numbers are good. It is what, exactly, they describe.
Story
When a TLS Allowlist Calls the Future Non-Compliant
A two-week study of 50.7 million TLS handshakes found that four national guidance sets could label between roughly 14% and 80% of the same institutional traffic non-compliant. The spread is not a direct measure of insecurity. It is a warning about what happens when a dated list…
Story
When the Routes Stop But the Registry Keeps Moving: The AS142207 Timeline After July 2026
When the Routes Stop But the Registry Keeps Moving: The AS142207 Timeline After July 2026 intelligence summary explains the development, the public evidence available to readers, the organisations involved, the regional context, market exposure, and the infrastructure…
Story
APNIC Ties an Eight-Service Outage to a Misplaced Load-Balancer Drain
APNIC says a maintenance step intended for one load-balancer node was run against the other, causing an outage across eight listed services. The notice calls it 15 minutes, although its displayed start and end times are 17 minutes apart.
Story
APRICOT 2027 Fellowship Bars AI-Drafted Applications
The current call asks applicants to describe their own operational work in their own words. It also gives a closing date: 12 October at 23:59 Hong Kong time.
Story
APNIC’s 93% Service Score Needs a Member-Only Comparator
APNIC’s published service-quality line reads 94%, 95%, then 93%. The numbers remain high, but the 2026 endpoint brings a broader respondent mix into a measure previously reported for Members. A Member-only bridge would preserve the trend without erasing the wider community’s…
Story
APNIC Was 3.0% of One Geofeed Success Sample. That Is Not an Adoption Rate
The smallest bar in an APNIC 62 chart is precise to one decimal place. The footnote does more work than the bar: 200,000 geolocation rows were sampled, publishers were reduced to distinct netnames, and two of the five RIRs were left out. The result is a useful signal about one…
Story
APNIC's AS0 Maintenance Window Has a Delegation Clock
Four service names appear in APNIC's notice for 29 September, with no downtime expected. One of them is not merely a page to reach. The AS0 ROA Service makes a security assertion about address space that APNIC has not delegated. If an address moves out of that category, the…
Story
Stork’s DNS Serial Comparison Begins With the Zones It Could Fetch
APNIC 62 showed a useful cross-server mismatch signal. Its meaning begins one step earlier: which daemons, views and zone configurations entered the cache, when they were fetched, and what the fetch could not observe.
Story
APNIC’s Survey Asked for More Training—and Proof It Reached the Network
The 2026 APNIC Survey does not say technical training has failed. It says something harder to measure: respondents value skills development, yet want the journey from a lab to a working network to remain connected, observable and locally supported.
Story
The Route Was Absent. The Traffic Still Found It: APNIC 62’s BGP Neighbor Problem
A route-origin filter can leave an operator’s table clean while a downstream neighbor forwards toward the rejected destination. An APNIC 62 presentation made that uncomfortable distinction concrete. The useful response is to preserve separate evidence of received routes, local…
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.