APNIC

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 they count the same thing.

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.

An API call can finish successfully without settling the more important question: which registry rule did it execute? APNIC’s public records show an ASN-capable NIR endpoint, a direct-delegation project that reached final QA, and a roadmap card with no release history. The missing link is small, but it separates usable software from auditable authority.

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.

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 different response bases to the same question, while the averages disclose a centre without showing how any individual respondent built a budget.

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 editor from a route checker into a record of future authority, and that change needs its own receipt.

An acceptable-use policy can change while the response governed by it remains in a cache for years. APNIC's prop-173 would make ordinary WHOIS, RDAP and web queries subject to a clear, versioned policy and would tell users that querying or using the service means agreeing to those terms. That is a useful repair to an ambiguous boundary. Yet the draft asks each response to point only to the current policy URL. It does not make the response identify the policy version that applied when the data was returned.

“Alignment” sounds like database housekeeping. In APNIC’s Q3 2026 roadmap, it means something harder: deciding how resource holdings, a route-management template, Whois route objects and RPKI authorizations should change when they disagree—and preserving enough evidence to show why the machine chose one state over another.

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 they count the same thing.

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 different response bases to the same question, while the averages disclose a centre without showing how any individual respondent built a budget.

APNIC’s conference report does something more useful than recording winners and losers. It preserves a third procedural state. Prop-165 and prop-172 were discussed, but no consensus call was held. The next record should explain where that state leads without pretending it means rejection.

A probe in a box is an opportunity to measure the Internet. A probe that has connected, remained available and filled a blind spot is measurement capacity. APNIC’s 2025 reporting places 60 distributed devices beside 23 deployed ones, but does not publish the join that would tell members how one became the other.

APNIC 62's linked result sheet contains four polls but no NIR SIG contest. That blank is not a missing tally. It is the visible edge between two procedures: contested positions go to the online system; one confirmed candidate goes to acclamation in the SIG room.

APNIC can point to a genuine finish line: in the second quarter of 2026 it completed a multi-year move away from end-of-life CentOS hosts. Its wider security record is less linear. Tests, findings, classifications and exercises appear in separate reports, but the public evidence seldom follows a control all the way from scope to disposition and retest. The missing link is not more security theatre. It is a compact closure receipt.

APNIC's new survey does not produce one verdict on governance. It produces a positive score among people able to judge eight claims, and a separate measure of how often members could not judge them. Any decision that carries the first number forward should carry the second one too.

An APNIC 62 presentation turns one deliberately exposed server into a useful security instrument. Its headline, however, moves between attacks, attack events and events—three labels that cannot safely share one number.

APNIC has a sensible answer to an awkward governance question: Executive Council members who may seek re-election do not help choose the committee that polices the election. The trouble is not the answer. It is where the answer lives—and how little of the annual record shows the safeguard working from the first shortlist to the final appointment.

A 9 September APNIC Blog account turns a household outage into a precise infrastructure lesson: resilience begins only when an alternative service is running, reaches the clients that depend on it, survives a controlled failure and can be rolled back.

On 8 September, APNIC Labs could describe India’s observed ROV filtering as 1.14% or 6.03%. Both figures came from the same dated record. The difference was the window—and it is exactly why a national routing-security promise needs a receipt, not a headline number.

At APNIC 62, researchers put a regional number on a quiet control-plane problem: 4,611 routers across 1,343 APNIC-region autonomous systems answered an unsolicited BGP OPEN exchange in a February IPv4 scan. That is firmer evidence than a port banner, but it is neither a breach report nor a live inventory. The missing step is a confidential record of notice, operator explanation and comparable rescan.

The latest completed hour says APNIC received 3,192,583 WHOIS queries. Add the seven query types printed beside that total and the answer is 3,183,463. The missing bridge is not a rounding error; it is the meaning of the measurement.

APNIC has documented who joined the first stage of its leadership-diversity consultation and what barriers they described. The next test is whether it can connect outreach, participation and proposed remedies to a broader leadership pipeline without identifying individual contributors.

An APNIC 62 charter-review deck asks seven National Internet Registries four different questions, then places one 86% support chart beside them without saying which question it answers. The proposed charter may still deserve support. But if the NIR SIG is to consolidate views for the Executive Council, its first test is whether readers can trace a reported view back to the proposition that produced it.

APNIC Labs sent several kinds of “no” from an experimental authoritative DNS service. Definitive negatives drew roughly four queries per test. `SERVFAIL` drew 51.73 and silence 83.46. Those are measurements of received traffic—not a verdict on which resolver layer multiplied it.

APNIC built one definition document so the same words would not acquire different meanings as they crossed policy files. The document now has a different problem. Its main web page presents version 004 as a draft; its stable official-text address still presents version 003 as active. The authority can be reconstructed, but only by leaving the page that is supposed to define it.

APNIC 62 opened its SIG ballot online on 8 September. That describes the voting medium, not the electorate: an individual conference attendee still has to be in Mumbai, check in at the registration desk and show a record of participation in an earlier APNIC or APRICOT meeting. The distinction is defensible, but it should be measurable after the vote.

A cryptographic signature can make a statement authentic without making it an observation. An APNIC ASPA records which upstream providers an ASN holder authorizes. It becomes routing evidence only when a validator compares that declaration with an actual BGP AS path.

APNIC has done the difficult part that institutions often avoid: it identified an old role with no settled scope, named the governance risks around it, and formally adopted a replacement. The next part was deliberately separated. Observer attendance, confidentiality and information sharing were left to an operating protocol between APNIC and APNIC Foundation. That can be sound design. Yet the reviewed public record does not show whether the protocol is being drafted, agreed, used or replaced. A thin status receipt would close that gap without opening a single confidential board paper.

A service notice should let a Member decide when to act. APNIC’s current online-payment notice instead presents one four-hour window in its identity and timetable, then names a different day in the description. The responsible conclusion is not to choose between them. It is to make the conflict—and the record needed to resolve it—operationally visible.