AFRINIC · RIR Watchdog
Story
BTW reporting and context linked to this RIR. For the proposal-by-proposal history, the people involved and their changing positions, start with Policy.
Story
Latest stories
1,192Stories
Story
AFRINIC-10 changed its certified electorate from 36 to 40 before voting
A number on a presentation slide became a live test of how a private registry turns its accounts into a corporate voter roll: the official account of AFRINIC-10 records 36 certified eligible voters at slide time, a correction to 40 before the ballot, 41 ballots cast and 40 found…
Story
The Cairo no-consensus finding AFRINIC’s record cannot reconstruct
On 21 May 2009 in Cairo, the IPv4 Soft Landing proposal was recorded as having failed to reach consensus and was returned to the RPD mailing list for further discussion. That procedural disposition is clear. The official record does not preserve the objections, the assessment…
Story
A /48 for local networks—and a subsidy with no named payer
AFPUB-2009-v6-001 tried to solve a precise access problem with a technically disciplined IPv6 offer. Its unresolved question was not the size of the address block, but who would finance the special path and on whose authority.
Story
Soft Landing's 13 May revision and the eight-day review window
Douglas Onyango’s 13 May 2009 revision of Soft Landing did more than polish a familiar proposal. It changed the practical test for further IPv4 allocations, fixed /23 as both minimum and maximum, introduced overlapping four-allocation limits, removed a critical-infrastructure…
Story
AFPUB-2009-v4-001 implemented the final-/8 allocation formula
On 6 March 2009, AFRINIC recorded AFPUB-2009-v4-001 as implemented while the ICANN Board ratified the same global policy and directed staff to implement it. The rule protected one final /8 for each of the five regional Internet registries, but it did not attempt to make the needs…
Story
AFRINIC-10 and the Recovered-IPv4 Return Formula
In Cairo on 21 May 2009, AFRINIC-10 recorded approval of AFPUB-2009-v4-002, a proposal for returning recovered IPv4 blocks to an IANA pool and reallocating them among eligible Regional Internet Registries. The proposal offered an unusually precise answer to a real scarcity…
Story
AFRINIC’s legal review says dashboard punishment rules are still unwritten
AFRINIC’s 23 June assessment of a proposed automated compliance dashboard warns that the draft leaves staff to define essential sanction rules, omits adequate due process and data protections, and gives the Board a vague exception power. The proposal was still “Under Discussion”…
Story
The first Soft Landing proposal turned AFRINIC's future final /8 into a rationing instrument
On 7 January 2009, an email to AFRINIC's policy list converted a distant shortage into a design problem: when ordinary allocation could no longer avoid the prospective final /8, who should receive how much, under which conditions, and with what protection for whoever arrived…
Story
AFRINIC’s 2008 Bad-Debts Line and the Missing Control Bridge
AFRINIC’s 2008 accounts left a precise number and an imprecise institutional story: a sharply larger “Bad debts” expense appeared in the financial summary, while the aggregate records needed to understand collection, classification, approval and any service consequence are not…
Story
The 1,024-Number Rule: What AFRINIC Actually Approved in 2008
The 1,024-Number Rule: What AFRINIC Actually Approved in 2008 intelligence summary explains the development, the public evidence available to readers, the organisations involved, the regional context, market exposure, and the infrastructure consequences that may follow. The Story…
Story
The policy chain AFRINIC made visible—and the powers it left unresolved
On 27 February 2008, AFRINIC announced and implemented a new policy-development process that replaced its transitional model. The enduring question is not whether the new process looked open, orderly or communal, but who acquired power at every handoff from proposal to running…
Story
The Number AFRINIC-7 Did Not Decide
AFRINIC-7 exposed a consequential gap between agreement on an IPv4-exhaustion policy direction and authorization of the quantity that would make the proposal operative.
Story
AFRINIC’s Receiver exit has remained an application for 307 days
AFRINIC said in October 2025 that its Receiver had begun the process for formal release. On 11 August 2026, AFRINIC’s own public case list still labelled the discharge application “Ongoing”, after the announced Board had formed committees and management structures with Receiver…
Story
AFPUB-2007-GEN-001 cut the allocation and assignment planning horizon from two years to one
AFRINIC’s 2007 change looked like a simple adjustment to a forecast period. In operation, however, the difference between accepting two years of prospective need and accepting one year changed both how much uncertain demand could enter a single decision and how soon a growing…
Story
What AFRINIC’s 9–5–1 hand count did—and could not—establish
On 27 September 2007, a show of hands at AFRINIC-7 gave one IPv4-exhaustion proposal the larger recorded response, but the surviving numbers cannot answer the question later claims of mandate would require: larger among whom, under what response rules, and with what checkable…
Story
The Six Rows Missing From AFRINIC-6
AFRINIC’s surviving account of its sixth policy meeting offers a memorable result—three proposals reached consensus, two were withdrawn and one did not reach consensus—but not the decision ledger needed to verify it at a glance. Reconstructing the six proposal lines shows that…
Story
The bylaw bridge from registry policy to membership termination arrived in 2012, not 2007
AFRINIC’s archive reveals a consequential constitutional change in two stages: a broad Associate Member termination-and-return structure in the instrument labelled 2007, followed in 2012 by an express clause making compliance with Number Resources Management Policies a condition…
Story
AFRINIC’s 2007 Fee Clause Made Discretion a Continuing Duty to Account
Article 4 of the instrument archived as AFRINIC’s 2007 bylaws gave the Board continuing authority to review a portfolio of recurring charges. That was adaptable private-company financing, not taxation; but where operators depend in practice on reliable registry coordination…
Story
Resolution 200605.28: When a Board Calendar Creates Capacity but Not Accountability
In May 2006, AFRINIC’s Board fixed a recurring teleconference date for its own work. The choice was practical and potentially valuable. But a date on a calendar is only the space in which oversight might happen; the public record needed to show whether that space was used is a…
Story
ASO turned AFRINIC’s disputed appointment into a working global-policy seat
The NRO welcomed AFRINIC’s post-election Board, that Board announced a representative with the Receiver’s consent, and ASO records later show the appointee doing council work. What the 16-reference does not supply is the underlying appointment resolution, minutes, vote roll or…