The 24th SIG-NOC (Special Interest Group on Network Operations Centres) meeting took place on 9–10 April 2026 in Utrecht, the Netherlands. It was hosted by SURF and co-located with Security Days. In total, 30 participants joined on site, and 19 joined remotely. The meeting brought together the NOC community to share updates and discuss key topics in network operations, including automation, AI, security, sustainability, and common tools.
Meeting summary
Participants explored new routing security methods (ASPA), how AI can support workflows and make tools easier to use, and how different teams work together across networks such as EuroHPC. There was also a discussion about the risks and safe use of AI in NOC work. Participants heard how the SURF NOC works with an external partner and what tools they use in practice. Sustainability was also covered, with examples of how to measure and reduce the environmental impact of network operations.
On the second day, the focus was on community tools and services (such as perfSONAR, Argus, and network automation platforms), security tools, and ideas for what could be built together in the future. There were also talks about challenges with hiring and keeping skilled staff in NOCs, as well as updates about broader GÉANT network developments.
Overall, the meeting showed a clear focus on using automation and AI, improving security, sharing tools, and making network operations more efficient and sustainable through community collaboration.
Discussion takeaways
Group discussion focused on two main topics: the use of AI in NREN operations and the challenges around community-developed tools. On AI, participants highlighted the need for clear policies or guidelines, along with the right infrastructure to support safe use (such as cloud or on-prem solutions, licensing, and scaling). A key concern was making sure AI tools are used safely, especially when handling operational data and protecting privacy.
On community tools, participants noted that it is often unclear what tools exist or what their development plans are, and that better visibility and timing of communication are important so people can actually use them when needed. There was also discussion about whether to build tools in-house or use and contribute to existing solutions. While in-house development helps build internal knowledge, using well-known tools can be better for long-term sustainability and staff mobility. Overall, the discussion showed that these topics are complex and depend heavily on context.







