Seven Years of NOG Support — What Volunteer Networks Actually Build

I joined a NOG mailing list in 2019. It was the first time I'd been in a community where network operators talked to each other as peers rather than through vendor or standards-body intermediaries. The signal-to-noise ratio was the best I'd seen on any technical list. I lurked for six months, then started replying, then started showing up at the in-person meetings.

By 2024, the same mailing list was coordinating emergency fiber restoration into Ukraine. Same people. Same conversational tone. Bigger stakes. That distance — between "we discuss BGP route filters" and "we route emergency communications into a war zone" — is what NOG communities actually do over a span of years.

The standards bodies write the documents. The vendors ship the equipment. The NOGs are where the work that makes those two useful actually happens.

What a NOG is, operationally

A Network Operator Group is a regional or topical community of people who run actual networks. It is not a standards body. It is not a trade association. It has no formal product. The artifacts are mailing lists, meetings two to four times a year, a public website, and an informal coordination function that nobody has on a job description.

The membership shape is consistent. Independent network operators, ISPs from small to large, university networks, content networks, occasional vendors as participants but never as leaders, the occasional regulator on the periphery. The thing that bonds it together is the shared problem space: keeping networks running, peering with each other, debugging the same protocols across organisational boundaries.

The cultural rule that holds these communities together is unwritten: vendors and consultants participate as peers, not as salespeople. Pitch your product and the room cools. Help debug somebody's BGP problem and the room warms up.

Why volunteer-run beats vendor-run

The thing NOGs do that nobody else can do is converge on operational practice fast. When a new attack pattern appears, the people running networks affected by it can be talking on a NOG list within hours, agreeing on a mitigation within a day, deploying the mitigation across multiple independent networks within a week.

The standards-body equivalent of that process takes 18-36 months. RFC publication has its own cadence, vendor implementation cycles on top, and customer deployment cycles after that. By the time the standards process produces a recommendation, the NOGs have been operating mitigations for two years.

This isn't because standards bodies are slow at what they do. It's because the work the NOGs do is fundamentally different. The standards bodies produce documents that have to survive multi-stakeholder review. The NOGs produce operational practice that has to survive contact with production traffic. Both are useful. Only one of them is fast.

Episodes that mattered

A short list of NOG-coordinated work I've watched closely over seven years:

The 2020 routing-leak response. A specific large-scale BGP route leak event led to a same-day mailing list discussion across multiple NOGs, and by 48 hours later there was a recommended set of route-filter additions that several major transits adopted directly without going through formal change control. The leak's impact window closed faster because the operators talked to each other.

The 2021 abuse-contact reachability survey. A NOG member ran a script against every RIR's abuse contacts and published the results. The percentage of broken contacts shocked the community. Three years later, the same survey shows a substantially better number. The improvement was driven by social pressure from the survey results, not by any RIR rule change.

The 2023 RPKI deployment push. Cloudflare's enforcement triggered it. NOG meetings provided the venue where operators who hadn't yet deployed got the practical advice they needed from operators who had. The deployment curve steepened visibly after each major NOG meeting.

The 2024-2025 Ukraine fiber coordination. A separate post in this series goes into this in detail. The compressed version: NOG-affiliated operators identified fiber restoration priorities, donated splicers and time, and coordinated logistics through informal channels that no formal organisation could have moved through.

What outsiders consistently get wrong

Three misunderstandings that turn up regularly when I describe what NOGs do.

"They're industry conferences." They aren't. Industry conferences have keynotes, paid speakers, sponsor booths, and an explicit commercial structure. NOG meetings have technical presentations from operators describing what they actually built or broke, in clinical detail. The audience asks technical questions. The booth space, where it exists, is small and quiet.

"They're a lobbying organisation." They're not. NOGs occasionally engage with regulators on specific technical questions but they don't have a policy agenda. They don't have formal positions on most political questions affecting the internet. Where they have positions, they're narrowly technical.

"It's mostly large operators." It's not. The biggest networks send senior people, and those people are often well-known in the community, but the working majority of any NOG list is mid-size and small operators. The egalitarian pattern is part of the structure — a 50-person ISP and a 50,000-employee network operator have equivalent voice in the room.

Why I keep showing up

Seven years in, the reason I still attend the meetings and still read the lists is straightforward. The peer-to-peer learning rate is higher than any other professional venue I have access to. The advice is current. The discussion of failure modes is honest. The bullshit-to-signal ratio is low.

It's also where I've met most of the people I now consider friends in the industry. The professional network that comes out of seven years of consistent participation is real and useful in ways that go beyond technical learning. When something breaks in my own infrastructure at 2 AM, I have people I can text. That's not a small thing.

What I'd tell somebody just starting

Three pieces of advice, distilled.

Lurk first. Read the mailing list for three months before posting. The conversational norms are subtle and getting them wrong stings. Learn how people address each other, what level of detail is expected, how to ask a question that the room can productively answer.

Show up in person. Mailing lists are good. In-person meetings are how you actually become part of the community. The first time you go, you'll know almost no one. The second time you go, you'll recognise three or four faces. By the fourth meeting, you'll be in the conversations that don't happen in the formal sessions, and that's where the real work is.

Bring something to the table. Don't just consume. Find something you've built or learned or debugged that the community would benefit from hearing about. Present it. Write it up. The contribution is what makes you a member rather than a spectator.

What comes next

The NOG model is under pressure. The work is growing — Ukraine coordination, supply-chain resilience, the climate impact of network infrastructure, AI-fabric coordination across operators. The funding is not growing. NOGs run on volunteer labour and small membership fees. The hour cost on the volunteers is rising.

I don't know what the model evolves into. I know that the function the NOGs perform is increasingly important and the structure isn't scaling proportionally. The next five years will be interesting in a way that's not always pleasant for the people doing the volunteer work.

If you're a network operator and you've never participated in a NOG, this is the post that nudges you to fix that. The community will be better for your presence. So will the network you run.

Seven years from now, you'll have your own version of this story.