Summary

  • ICANN's announcement records recognition of AFRINIC as the fifth Regional Internet Registry on 8 April 2005, and RIPE NCC's own news archive records its congratulations while acknowledging that it had provided registry services for the African region before that recognition.
  • AFRINIC's About page dates its management of Africa's Internet number resources to 2004, and the documents obtained in this review do not enumerate what object-level records moved, record an acceptance by the receiving registry, or reconcile the two registries' data sets — so the layer that decides who controls a specific block stays open.

A registry handover is usually reported as a recognition event, and on that measure this one is well documented. ICANN's own announcement page records recognition of AFRINIC as the fifth Regional Internet Registry on 8 April 2005 (ICANN announcement). RIPE NCC's own news archive records a congratulation to AFRINIC on that recognition and acknowledges that RIPE NCC had provided registry services for the African region before it (RIPE NCC news archive). AFRINIC's About page states that AFRINIC has managed Africa's Internet number resources from its headquarters in Mauritius since 2004, and describes a nonprofit, member-based organisation registered in Mauritius (AFRINIC About).

Three institutional pages, published by the three institutions involved, and two different years. The gap is not a contradiction to score against anybody. It is a definitional signal, and it is the reason this article separates four things the registry system routinely fuses into one word.

Recognition is what a coordination body announces: this institution is the regional registry for this region. Service provision is what a registry does: receiving requests, publishing objects, answering holders. Custody of record is holding the authoritative record of a specific object, such that third parties must consult you and you can authenticate the holder. Authority to amend is being the body whose authenticated instruction changes that object's registered holder, status or delegation.

The documents obtained in this review establish the first two. Recognition is dated 8 April 2005 and attributed to ICANN. Service provision before that date is stated by the predecessor itself, in RIPE NCC's own archive item. AFRINIC's About page then describes continuous management from 2004 onward.

For the third and fourth layers the documents obtained here do not deliver, and that is a statement about this review's evidence, not about the world. Which body holds the authoritative object-level record of a particular legacy African block, and which body can authenticate its holder and amend it, are not established for any specific block by the three institutional pages reviewed here. An announcement naming a regional registry is not that finding. Neither is a registry lookup on its own, and neither, emphatically, is the fact that packets still reach the network behind the block.

This is where the money is. When recognition is published richly and object-level transfer thinly, three costs move outward. The first lands on the operator, who must prove continuity of title during a renewal, a transfer, a corporate reorganisation or a dispute — and must prove it with records the operator did not create. The second lands on the court, which has to reconstruct a chain of custody from conduct, correspondence and behaviour rather than from a reconciling document.

The third lands on the next institution to inherit the archive: a successor registry inheriting a set it cannot fully reconcile has inherited an expense it did not budget for.

Every one of those costs is invisible at the moment of transfer. They surface only when a specific block is contested, which means the incentive to document the transfer is weakest exactly when the transfer is easiest to perform quietly.

The practical test for custody is narrow and unglamorous: ask which body can authenticate the holder and authoritatively amend the block. That question has one answer per object, and it can be tested by asking what happens when a holder record must change. Packet reachability is not the test. A registry lookup page alone is not the test. An announcement naming a registry is not the test. The test is amendment authority.

Responsibility, once the layers are separated, is best assigned by function rather than by institutional name. Enumerating and certifying the exported set is the transferor's function. Accepting, reconciling, preserving provenance and explaining the current set is the receiver's function. Verifying or enforcing any handover condition is the recogniser's function — and only where such a condition was in fact imposed, which the documents obtained here do not establish either way.

That framing matters because it prevents two lazy conclusions. It is not a scandal narrative: nothing in the material obtained supports an allegation of concealment, bad faith or fabricated records, and the institutions involved describe the transition in their own words on their own pages. It is also not a settled matter. The absence of a reconciling document in the material obtained is an auditability problem with a cheap remedy, not a criminal one with an expensive trial.

The remedy is procedural. Publish, beside the recognition, the scope of the objects moved; the exceptions and reserved blocks; an acceptance by the receiving registry; and a reconciliation statement connecting predecessor and successor snapshots. That set would let an outside party connect a recognition decision to an individual object without reconstructing anything from conduct. It is a recommendation of this article, not a description of any existing rule, and it is unusually cheap for the assurance it buys.

On scope: this review examined the recognising body's public announcement archive, the predecessor registry's public news archive and the receiving registry's public About page, with a cut-off of 7 November 2026. The material obtained consists of institutional summaries and one reported excerpt from those pages rather than instrument text read line by line, which is why no sentence here is presented as a verbatim quotation from a handover instrument.

The argument does not depend on finding a missing document. It depends on what the reader can do with the documents that exist. AFRINIC's entry in this publication's directory, RIPE NCC to AFRINIC Transition Only for Strategic Circle, describes an entity that performs registry functions for internet number resources; the pages reviewed here describe the recognition and the prior service, and stop short of the object ledger. Until a reconciled account is published beside a recognition of this kind, an operator holding pre-handover African space carries a provenance question it did not create — and answers it only under pressure.