APNIC is the Regional Internet Registry administering IP addresses for the Asia Pacific
APNIC is the Regional Internet Registry administering IP addresses for the Asia Pacific
The 2026 APNIC Survey is now open — have your say!
By Dale Roberts
The 2026 APNIC Survey — your chance to directly inform APNIC’s strategic planning, priorities, and future direction — will be open from 1 to 28 June 2026. It takes about ten minutes to complete, and you could win a prize.
Introducing the APNIC WhatsApp Community
By Dan Fidler
The APNIC WhatsApp Community offers a direct way to stay informed and connected, wherever you are, delivering timely updates, discussions, and event information directly to your phone.
Homepage highlight
The 2026 APNIC Survey is open until 28 June
This is your chance to directly inform APNIC’s strategic planning, priorities, and future direction. Take the survey today!
Persistent device identity in the era of MAC address randomization
By Premanand Seralathan
Guest Post: A RADIUS-based framework for stable device identification.
Centrality in the Internet’s names
By Geoff Huston
The Internet's Domain Name System undertakes a vitally important role in today's Internet. The question here is — is the DNS centralized?
![Banner image for [Podcast] About time article.](https://blog.apnic.net/wp-content/uploads/2023/06/Time_FT.png)
[Podcast] About time
By George Michaelson
This episode of PING explores how today’s dependence on highly synchronized clocks is colliding with unstable Earth rotation, legacy system epochs, and the growing need to secure Internet time itself.
Register now for APNIC 62 in Mumbai
By Timothy Hildred
Registration has opened for APNIC 62, being held from 4 to 10 September 2026 in Mumbai, India. Register before 31 July to receive an early bird discount for the workshops.
RADIUS isn’t going away, so let’s fix it properly
By Alan DeKok
Guest Post: "RADIUS is the protocol that will never die". So given that RADIUS is staying, what do we need to do to make it secure for the next 30 years?
Understanding traceroute by reimplementing it in Rust
By George Michaelson
What can be learned by reimplementing the common traceroute utility in Rust? The inner workings of traceroute, and the importance of careful interpretation, for a start.