The internet is decentralized, but some of its most important technical resources still require global coordination.
Every public-facing network depends on unique identifiers. IP addresses must not conflict with one another. Autonomous System Numbers need to identify distinct networks. Technical registries need to remain accurate enough for operators around the world to understand which resources have been allocated and where responsibility sits.
This creates an unusual governance system.
No single organization controls the internet, yet several institutions perform essential coordination functions that allow thousands of independent networks to operate together.
Two important parts of that system are the Internet Assigned Numbers Authority, or IANA, and the Regional Internet Registries, or RIRs.
Understanding the relationship between them also helps explain why the prolonged governance problems surrounding AFRINIC have attracted attention far beyond the organization itself.
The Internet Needs Coordination Without Central Control
The internet consists of independently operated networks.
Telecommunications companies, cloud providers, universities, governments, content networks, hosting companies and enterprises all operate infrastructure according to their own technical and commercial requirements.
Yet these networks still need a common system for certain globally unique resources.
Two unrelated networks cannot simply decide to use the same globally routed IP address block without creating potential conflicts.
Similarly, Autonomous System Numbers must be administered consistently so that networks participating in interdomain routing can be identified.
The internet therefore requires coordination, even though it does not require a single central operator.
That distinction is fundamental to understanding internet governance.
What Role Does IANA Play?
At the global level, IANA coordinates several categories of unique internet identifiers.
Its core responsibilities include maintaining information related to the DNS root zone, coordinating global pools and registries for IP addresses and Autonomous System Numbers, and maintaining registries for internet protocol parameters.
For readers unfamiliar with this part of internet infrastructure, this guide explaining what IANA is and how the Internet Assigned Numbers Authority works provides a useful overview.
IANA’s role is primarily one of technical coordination rather than centralized control.
For internet number resources, it maintains top-level registries and provides large blocks of address space and AS Numbers to Regional Internet Registries. Those regional organizations then administer resources within their respective service regions.
A simplified model looks like this:
IANA → Regional Internet Registry → Network operator or local registry → End user
The exact allocation path varies, but the hierarchy helps explain how globally coordinated resources reach individual networks.
Why Regional Internet Registries Exist
It would be impractical for one global organization to handle every IP-address request, membership relationship and local registration issue across the entire world.
Regional Internet Registries provide a distributed model.
There are five RIRs serving different regions:
- AFRINIC
- APNIC
- ARIN
- LACNIC
- RIPE NCC
IANA coordinates internet number resources globally, while RIRs manage registration and distribution processes at the regional level.
The model allows regional communities to participate in policies affecting number resources while maintaining compatibility with a global system.
However, decentralization introduces another requirement: each regional institution must have governance structures strong enough to perform its responsibilities reliably.
That is where the AFRINIC experience becomes particularly important.
What Is AFRINIC?
AFRINIC stands for the African Network Information Centre.
It is the Regional Internet Registry serving the African region and is responsible for administering internet number resources within its service area.
Readers who need a basic introduction can start with this explanation of what AFRINIC is and how its IP resource management role works.
AFRINIC performs a technical and administrative function within the larger internet-number registry system.
Its importance is therefore not simply organizational.
The networks depending on its services include internet service providers, telecommunications companies, hosting companies, enterprises and other infrastructure operators.
This means governance problems inside an RIR can have implications beyond employees or board members.
They can become questions about the resilience of internet infrastructure institutions.
When Registry Governance Becomes an Infrastructure Issue
A normal corporate governance dispute might involve disagreements between directors, shareholders or executives.
A governance dispute inside a Regional Internet Registry carries additional significance because the organization administers resources used by operational networks.
AFRINIC has faced a prolonged combination of governance disputes, legal proceedings and institutional challenges.
BTW Media’s detailed AFRINIC governance crisis case file tracks the situation through issues including board legitimacy, election integrity, legal process and institutional continuity. The publication currently characterizes the dispute as a multi-year governance and legal crisis with potential implications for broader RIR accountability.
This raises an important question:
What happens when an institution designed to provide stable internet-resource administration becomes institutionally unstable itself?
Technical Continuity and Institutional Continuity Are Different
One of the most important lessons from registry governance disputes is that the internet can continue operating even while the institution behind a registry experiences serious problems.
Existing IP addresses do not suddenly stop routing simply because a board dispute occurs.
Network operators still have routers, upstream providers, BGP sessions and operational infrastructure.
That technical resilience is important.
But it should not be confused with institutional health.
A Regional Internet Registry still needs to maintain accurate records, process legitimate requests, administer member relationships, manage policy implementation and maintain trusted organizational authority.
Long-term registry resilience therefore depends on both:
Technical continuity, meaning networks and core registry systems continue functioning.
Institutional continuity, meaning there is legitimate authority to make decisions, maintain records and administer the organization.
The two are related, but they are not identical.
Why Governance Matters to IP Address Holders
To a network operator, governance may initially sound distant from day-to-day technical operations.
In reality, registry governance affects several practical questions.
Who is authorized to change registration information?
Who approves transfers?
Who manages resource-holder accounts?
Who determines whether policies have been followed?
Who represents the registry in legal disputes?
Who oversees databases and technical services?
Who can appoint senior management?
Who has responsibility when something goes wrong?
When governance is stable, operators rarely need to think about these questions.
When authority becomes disputed, they can suddenly become very important.
The Registry Is a Record Keeper, Not the Network Itself
Another useful distinction is between the authority of a registry and control of the underlying internet infrastructure.
A registry may maintain authoritative information concerning an IP address allocation, but it does not operate every router using that address space.
Actual internet routing depends on independently operated networks and technologies such as BGP.
Likewise, IANA coordinates global registries but does not decide every routing announcement made by every network. Its influence comes from maintaining trusted and globally consistent technical records.
This distinction matters during governance disputes.
Control of a registry record, contractual relationship, routing announcement and physical network infrastructure may involve different organizations and different forms of authority.
Internet governance becomes much easier to understand once these layers are separated.
Why Accurate Registries Matter
The registry system works because participants generally trust authoritative records.
Those records help establish where number resources were allocated and which organizations are associated with them.
If registry information became unreliable, conflicting or impossible to administer, several practical problems could emerge.
Network operators might have difficulty confirming resource status.
Transfers could become more complicated.
Ownership or contractual disputes could become harder to investigate.
Routing-security processes could face uncertainty.
Operational troubleshooting could become more difficult.
At the global level, IANA’s number-resource functions are designed to maintain consistent authoritative registries and coordinate allocations to the RIR system.
Regional institutions therefore have an important responsibility to preserve that integrity further down the hierarchy.
The AFRINIC Case Is Bigger Than One Registry
AFRINIC’s problems matter partly because the global registry system is interconnected.
Each RIR serves a particular regional community, but internet number resources participate in a global routing environment.
This means serious institutional problems in one region can generate questions relevant everywhere.
Could another RIR face similar governance paralysis?
What happens if a board cannot legally function?
How should operational continuity be protected during litigation?
How should elections be conducted during an institutional crisis?
What authority should external internet organizations have during a regional registry failure?
How can members challenge decisions without threatening essential services?
These are questions about institutional design, not only AFRINIC.
That makes the case useful for evaluating the resilience of the RIR system as a whole.
Governance Should Be Designed for Failure
Engineers rarely design critical networks on the assumption that nothing will ever go wrong.
They use backups, redundant links, multiple power sources, failover systems and disaster-recovery procedures.
Internet institutions should apply similar thinking to governance.
A resilient registry should be prepared for situations in which:
- Directors resign.
- A board loses quorum.
- Elections are disputed.
- Senior executives leave.
- Litigation affects normal operations.
- Financial access becomes restricted.
- Members challenge institutional decisions.
- Critical records need to be preserved through a leadership transition.
Governance resilience means knowing what happens next before the crisis arrives.
Checks and Balances Matter
The challenge is not merely giving someone enough power to keep an organization running.
Too much concentrated authority can create another form of institutional risk.
A resilient governance framework therefore needs both continuity and accountability.
Emergency mechanisms should be capable of restoring normal governance without becoming permanent substitutes for it.
Election procedures need clear rules.
Financial decisions need oversight.
Technical administrators should have defined authority.
Legal responsibilities need documentation.
Members need credible channels for challenging decisions.
And institutional records should be preserved independently of individual officeholders.
The purpose of these mechanisms is not to eliminate disagreement.
It is to ensure that disagreement does not destroy the institution’s ability to function.
What Network Operators Should Learn
Network operators cannot control every governance development affecting the institutions around them.
They can, however, understand their dependencies.
An organization relying on internet number resources should know:
Which RIR maintains its registration?
Who has access to its registry account?
Which legal entity holds the resource relationship?
Which policies affect transfers or assignments?
How routing authorization is maintained?
Which records should be retained independently?
Who inside the organization is responsible for communicating with the registry?
These may appear to be administrative details until a dispute occurs.
Then they become part of operational risk management.
From IANA to AFRINIC: A Chain of Trust
The relationship between IANA, Regional Internet Registries and network operators can ultimately be viewed as a chain of technical coordination and institutional trust.
IANA maintains global number-resource registries and coordinates resource pools.
RIRs administer resources regionally.
Networks operate those resources in the real internet.
Each layer has a different role.
None should be confused with absolute ownership or control of the entire system.
The effectiveness of the model depends on each institution performing a relatively narrow function reliably and transparently.
When one institution experiences prolonged governance failure, the technical community gains an opportunity to test whether the surrounding system is resilient enough to cope.
Final Thoughts
The AFRINIC case demonstrates that internet governance is not merely about meetings, elections and policy documents.
It is also about the institutions that maintain the administrative foundations of global networks.
Understanding what AFRINIC does explains why stability at the regional level matters.
Understanding IANA’s role in global internet coordination explains where the RIR system fits within the larger architecture of internet identifiers.
And examining the ongoing AFRINIC governance crisis and its wider implications shows why institutional resilience deserves as much attention as technical resilience.
The internet does not require one central authority to function.
But it does require trusted institutions.
When those institutions manage globally significant technical resources, governance is no longer just an organizational concern.
It becomes part of internet infrastructure itself.
