Welcome to APNIC 62
APNIC welcomes you to Mumbai, India for APNIC 62. Here is what you can look forward to over the coming days.
Welcome to APNIC 62
By Timothy Hildred on 8 Sep 2026
APNIC welcomes you to Mumbai, India for APNIC 62. Here is what you can look forward to over the coming days.
WSIS Forum 2026: From commitments to measurable implementation
WSIS Forum 2026 marked the start of a new phase for global digital development, shifting the focus from commitments to measurable implementation.
Community consultation on increasing diversity in APNIC community leadership: Stage 1 report released
The APNIC Executive Council has released the Stage 1 report on APNIC’s community consultation on increasing diversity in APNIC community leadership. The discussion will continue at APNIC 62 in Mumbai, with remote participation available.
What part of ‘No!’ is so hard for the DNS understand?
At APNIC Labs we’ve been experimenting with understanding how the DNS handles requests to resolve nonexistent names to make the DNS more resilient to random name attacks.
[Podcast] Measuring the impact of locally served root zone
An analysis of the traffic impacts of locally served root zones, by Ilyas Rahimi at UvA.
Beeline: Enforcing application-layer policies in eBPF
Guest Post: While many L7 protocols are complex to parse, the logic needed to enforce L7 policies tends to be simple. For the vast majority (89%) of L7 policies in the wild, Beeline can eliminate the service proxy from the critical path.
Recommended Draft RIR Governance Document, Rationale report, and next steps
The NRO NC has published the Recommended Draft RIR Governance Document, including a redline version and rationale document.
The invisible heartbeat of our networks
Guest Post: The recent Telstra outage highlighted a critical but often overlooked dependency in modern networks: Accurate time synchronization.
The day after the zero-days
Guest Post: Patching faster cannot keep up with AI-driven discovery. Leverage structural invariants to make bug classes irrelevant.
The lingering legacy of ‘reserved’ ports
Modern service discovery mechanisms increasingly allow services to run on arbitrary ports, yet DNS may remain the one protocol that cannot fully escape its dependency on the long-established convention of port 53.