Skip to main content

Governance / NOGs

NOGS

Network Operator Group (NOGs) governance intelligence tracks institutions, policy processes, standards activity, registry operations, accountability disputes, and implementation signals that affect internet infrastructure. BTW.

Operator CommunitiesImplementation SignalsCross-Region Comparison
NOGS signal visual
Governance / NOGsNOGS
Research Scope19 NOG Sessions

APRICOT plus major regional and national operator groups.

Primary DomainGovernance

Execution governance and practical operations intelligence.

Signal TypeImplementation Briefing

Routing, peering, resilience, and operational standards in practice.

MethodProfile + News Stack

Institution profile mapped to deployable decision implications.

Latest Coverage

Latest from NOGS

173 articles

Сетевой инженер изучает учебные материалы в прибрежном месте; пустые карточки разложены группами по девять и шесть.

BDNOG

bdNOG22 names 15 fellows, but leaves its applicant pool unseen

The Bangladesh Network Operators Group has published the 2026 fellowship roster and support terms. The public record identifies recipients, but not the size of the applicant pool or whether they attended.

Oct 21, 2026
Two live event statistics panels separated by an undefined point in time.

LACNOG

LACNIC 46 Shows Two Numbers. It Does Not Explain the Gap

During LACNIC 46–LACNOG 2026, the event system published 1,215 registered entities and a separate attendees view totalling 706. The page gives neither a definition for “attendees” nor a visible data-as-of time, so the difference cannot responsibly be called an attendance rate.

Oct 20, 2026
A small, tidy network interconnection room with routers, patch panels and cabling, and Himalayan foothills visible through a window.

SANOG

Bhutan Internet Exchange: membership, peering and the resource footprint behind national interconnection

Bhutan Internet Exchange: membership, peering and the resource footprint behind national interconnection intelligence summary explains the development, the public evidence available to readers, the organisations involved, the regional context, market exposure, and the…

Oct 14, 2026
Conceptual 1990s meeting room with a camera facing a projection screen, branching paths to remote CRT viewers, and a separate fading sound-wave path.

NANOG

Packets Reached CERN; Many Questions Did Not: NANOG 1 and the MBONE, 1994

In June 1994, organizers planned to multicast NANOG’s Ann Arbor meeting over the MBONE. The archive preserves three different kinds of evidence: one person could not find the session, another asked for a steadier view of the screen, and a listener at CERN reported no packet loss…

Oct 13, 2026
Five blank candidate podium markers face two empty Board seats across a conference hall; a cyan ballot trail continues past the venue.

NANOG

Five Candidates, Two Seats: NANOG’s Ballot Outlasts Its Meeting

NANOG’s 2026 Board contest puts five candidates before members for two staggered seats. Candidate presentations are scheduled during NANOG 98 in Miami, but voting opens on the same date and stays open after the meeting ends: the published window runs from 20 through 26 October…

Oct 8, 2026
An editorial illustration of a planned APNOG-style board handover across the Asia-Pacific region.

APRICOT

APNOG Put Its Board on a March Clock. The Handover Is the Test.

APNOG says its Board terms will run from March to March, rather than exactly with the annual general meeting. The stated purpose is practical: give outgoing and incoming directors time to hand over work and let new directors apply for an Australian director ID before appointment.

Oct 8, 2026
Registration table at a network-operators conference minutes before doors open: a neat stack of blank membership cards, orderly rows of blank voting cards with empty checkbox outlines, and an unbranded ballot box with its slot closed, beside an empty folding chair; softly blurred rows of empty seats recede behind.

NANOG

NANOG Kept the Door Open: The Membership Roll as the Corporation's Control Surface

NewNOG, Inc.'s bylaws place the corporation's property, affairs and business under its Board of Directors, and they elect directors through an open nomination and election process from a membership whose joining bar was deliberately kept low. NANOG's own members' meeting record…

Sep 23, 2026
Archived technical messages feed an operations console while an empty legislative chamber remains behind a clear boundary.

NANOG

The Mailing List Is an Operations Room, Not a Legislature

NANOG's mailing list is valuable because operators can expose a fault, compare evidence and correct a diagnosis in public. That practical authority should not be confused with permission to speak for networks whose operators did not join the thread.

Sep 7, 2026
A complete form route and an early-contact doorway meet at an unlabelled junction.

AFNOG

AfNOG’s Partial-Input Invitation Opens the Door Without Mapping the Process

AfNOG’s 2007 call welcomed suggestions and expressions of interest even without all requested proposal information, but the cited page did not explain beside that invitation how these inputs related to a complete proposal.

Sep 6, 2026
A presenter badge reaches a cleared registration gate while a travel path leads to a wallet and an unlabeled doorway.

AFNOG

AfNOG’s Presenter-Cost Rule Waives Registration but Leaves Travel Support Unspecified

AfNOG’s 2007 call said presenters and tutorial instructors were expected to cover travel while being exempt from registration fees, but the cited page did not say beside that rule whether a travel-support exception route existed.

Sep 6, 2026
A presentation document connects to a website through a glowing permission bridge with four unlabeled boundary markers.

AFNOG

AfNOG’s Reproduction-Permission Request Leaves the Licence Boundary Unstated

AfNOG’s 2007 call asked for permission to reproduce the contributor’s presentation after the event, including permission to post it on the AfNOG website. That sentence names two requested acts, but it does not state how long the permission would last, where it would apply…

Sep 6, 2026
A person card and institution card are connected by an unlabeled bridge with empty relationship tokens.

AFNOG

AfNOG’s Affiliation Field Names an Institution Without Defining the Relationship

AfNOG’s 2007 call requested a contributor’s affiliation without defining what relationship that label represented.

Sep 6, 2026
Postal, telephone, fax and email symbols converge into a tray with blank handling labels.

AFNOG

AfNOG’s Direct-Contact Field Lists Reachability Without Stating Its Handling Boundary

AfNOG’s 2007 call requested four published contact points without publishing an adjacent purpose, access or retention notice.

Sep 6, 2026
A proposal card with an adjustable duration bar sits above a programme grid with open time blocks.

AFNOG

AfNOG’s Requested-Time Field Leaves Its Relation to Programme Planning Unexplained

AfNOG’s 2007 call asked contributors how much time they wanted without explaining how that request would relate to programme planning.

Sep 6, 2026
One proposal card branches into presentation, panel and tutorial formats, each with a blank information field.

AFNOG

AfNOG’s Proposal-Type Field Names Formats Without Defining Their Evidence

AfNOG’s 2007 call named three proposal formats without publishing format-specific evidence fields.

Sep 6, 2026
Several information streams converge on a small blank abstract card beside separate proposal fields.

AFNOG

AfNOG’s 200-Word Abstract Cap Leaves the Required Signal Unspecified

AfNOG’s 2007 call capped abstracts at 200 words without stating what those words had to establish.

Sep 6, 2026
A technical lab station sits beside outlined, unspecified workshop resources and dependencies.

AFNOG

AfNOG’s Optional Hands-On Tutorial Format Leaves Resource Needs Unstated

AfNOG’s 2007 call allowed hands-on tutorial components but did not publish their resource needs.

Sep 6, 2026
An operational network and a near-deployment network are separated by an indistinct readiness horizon.

AFNOG

AfNOG’s ‘Soon-to-Be-Deployed’ Tutorial Scope Leaves Readiness Undefined

AfNOG’s 2007 call described advanced training on technology soon to be deployed without defining readiness.

Sep 6, 2026
A fading boundary separates a technical tutorial workspace from an empty display pedestal, depicting an undefined non-commercial principle.

AFNOG

AfNOG’s Non-Commercial Tutorial Principle Leaves Its Meaning Undefined

AfNOG’s 2007 call said tutorials should be non-commercial but did not define that boundary.

Sep 6, 2026
Two paired calendar tiles and one separate tile depict a two-day preference and an undefined one-day possibility.

AFNOG

AfNOG’s Two-Day Tutorial Preference Leaves One-Day Consideration Undefined

AfNOG’s 2007 call preferred two full days for tutorials and said one-day requests might be considered.

Sep 6, 2026

Member Unlock

Restricted Profile Intelligence

Login is required to unlock full profile briefings and deep-dive sections.

Only for Strategic Circle

Strategic Circle Briefing

Join to unlock strategic briefings after signing in.

Join Strategic Circle
Only for Leadership Alliance

Leadership Alliance Briefing

For qualified IP-asset owners and management; sign in to unlock alliance briefings.

Join Leadership Alliance

Session Map

NOG Profiles by Region

NANOG

North American operator community for interconnection and routing practice.

Open NANOG

MENOG

Middle East network operator dialogue with deployment-focused sessions.

Open MENOG

APRICOT

Asia-Pacific operations and policy interface conference ecosystem.

Open APRICOT

JANOG

Japan operator community execution and resilience signal stream.

Open JANOG

SANOG

South Asian operator collaboration and engineering knowledge exchange.

Open SANOG

AfNOG

Africa-focused network operators community and technical training ecosystem.

Open AfNOG

LACNOG

Latin American operator coordination and interconnection quality.

Open LACNOG