APNIC recently held a dedicated Member Gathering and RPKI tutorial in Bangkok alongside the 10th BKNIX Peering Forum (BPF) and ThaiNOG 8 to better understand Member challenges in Thailand and help encourage RPKI adoption.
It was a great opportunity to meet with Members both large and small, as while Thailand has a mature and active Internet community, many Thai APNIC Members prefer local industry events over regional conferences. This has meant that attendance from Thai delegates at APNIC meetings has traditionally been lower than from some neighbouring economies. The Bangkok events provided an opportunity to address this.
A growing regional platform
The tenth BKNIX Peering Forum (held with ThaiNOG 8) highlighted the event’s growth. With more than 400 registrants, including participants from Laos and Myanmar, it has evolved from a local peering event into a significant regional forum. For APNIC, this created an ideal opportunity to engage with operators from both Thailand and across South East Asia.
During the event, the APNIC team met Members at the booth, answered questions, carried out Data Accuracy Check reviews, and held side meetings with several operators to explore how we could assist them further. APNIC also presented on ASPA at ThaiNOG 8.
Member discussions focused on operational matters such as resource transfers, allocation requests, and MyAPNIC features. Others explored broader topics, including IPv6 deployment, routing security, Autonomous System Number (ASN) portability, and support for emerging infrastructure projects in neighbouring economies.
What stood out most was the quality of the discussions. Members were seeking more than administrative support — they wanted practical guidance on managing resources, adopting best practices, and preparing their networks for future growth.
These conversations highlighted the value of face-to-face engagement, particularly in economies where opportunities for direct interaction with APNIC has been less frequent.
Building capacity through practical learning
While BPF and ThaiNOG supported networking, the APNIC Member Gathering and RPKI tutorial enabled deeper discussion and focused knowledge sharing.
Routing security remains a critical issue for network operators. However, getting started with RPKI, including validation and deployment, can still be challenging. The tutorial covered key RPKI concepts, deployment considerations, and emerging technologies such as ASPA. It focused on practical benefits and current best practices, rather than positioning routing security as a compliance task.
Positive Member feedback reflected both the quality of the content and the demand for more hands-on technical training.
The APNIC Member Gathering featured presentations on MyAPNIC, Internet resource management, IPv6 deployment, and IPv6 and RPKI adoption trends in Thailand. By combining policy, resource management, and operational insights, the session provided Members with a clearer understanding of how these areas contribute to Internet resilience and growth.
Strengthening relationships for the future
The most valuable outcome of the Bangkok events cannot be measured by attendance or survey results. It was the quality of conversations and the relationships built through them. Feedback, particularly on interactions with APNIC staff, highlighted how much Members value access to expertise and support.
These engagements also gave APNIC valuable insight into the needs of Thai Members, helping identify where future training, technical assistance, and community support can have the greatest impact.
Looking ahead
The Bangkok experience highlighted a simple lesson: capacity development works best when it is integrated into existing community events and supported by local engagement.
For APNIC, this was more than participation in a local event. It was an opportunity to strengthen relationships and support the development of skills and knowledge that help keep the Internet open, secure, and resilient.
The views expressed by the authors of this blog are their own and do not necessarily reflect the views of APNIC. Please note a Code of Conduct applies to this blog.