Summary

  • Between September 2004 and December 2005 the registry for African internet numbers changed hands in four dated steps, and on 31 December 2005 RIPE NCC ended the membership of every African member and terminated their Standard Service Agreements, handing outstanding fee claims and membership data to the new registry.
  • Every instrument in that sequence moved registration documentation, accounting records and DNS administration. None of the documents read for this article moved a company-law register of members, and AFRINIC's own constitution gives its statutory register one category only: Registered Member, a Director upon assumption of office.

Four dates, and what each one actually did

The transition is usually told as a coming of age. Read the documents in order and it is a handover of files, with a membership question left sitting in the middle of the table.

On 30 September 2004 the ICANN Board gave "provisional approval" to AFRINIC's application for recognition and transition plan, expecting the plan to be completed and an amended application to be submitted (ICANN Board resolutions, 30 September 2004). Provisional means provisional: nothing was recognised yet.

On 21 February 2005 AFRINIC began operating as a fully functional registry for the African region, in preparation for final recognition. Until that final recognition arrived, local internet registries in Africa were, in RIPE NCC's own words, "still legally members of the RIPE NCC", and every assignment and registration was made under the RIPE NCC Standard Service Agreement (RIPE NCC, RIPE NCC to AFRINIC Transition). That sentence is the hinge of the whole story: the service moved first, the contract moved later.

AFRINIC's own announcement, posted on 23 February 2005, puts the operational cut at a slightly different point. "With effect from February 22nd," the chief executive wrote, the organisation had started phase two, operating as a full registry "with a second opinion from other RIRs", with its whois server online and all resource requests going directly to its hostmaster (AFRINIC announcement, 23 February 2005). One day apart, and worth keeping: 21 February is the date the outgoing registry, the NRO and ICANN use for operational service; 22 February is the date AFRINIC used for its whois and phase-two cutover. Two dates on two instruments, not a contradiction to be smoothed away.

On 8 April 2005 the ICANN Board proclaimed AFRINIC "a fully approved and recognized Regional Internet Registry", to provide address registration and other services for the Africa region — and recited the September 2004 provisional recognition in the same resolution (ICANN Board resolutions, 8 April 2005).

Then came the papers. At the AFRINIC-2 meeting in Maputo on 26–27 April 2005, APNIC, ARIN and RIPE NCC signed letters transferring to AFRINIC formal authority for the parts of the region they had previously served, "including all registration and accounting documentation and DNS administration" (NRO, Transfer of Authority to AFRINIC). The NRO announcement is dated 27 April 2005 and does not say which of the two meeting days carried the RIPE NCC signature. That gap is small and real.

The last date is the one nobody quotes. RIPE NCC's 2005 annual report records that AFRINIC became fully operational on 21 February 2005, that the RIPE NCC ended the membership of all its members from the African continent on 31 December 2005, and that the Standard Service Agreement was terminated for African countries the same day, with outstanding fee claims and membership data transferred to AFRINIC (RIPE NCC Annual Report 2005, ripe-377). Ten months of overlap: operational service on one side, legal membership on the other, and a membership list that ends up in the new registry's hands.

That list is where the trouble starts, because a list of members is not the same thing as a register of members.

What the paperwork moved, and what it did not

Read the transfer sentence again. Registration documentation. Accounting documentation. DNS administration. Membership data. Fee claims.

Those are the assets of a coordination service: the records that say which network holds which block, the ledger that says who owes what, and the reverse-delegation files that keep the plumbing pointing at the right nameservers. What the sentence does not mention — in the ICANN resolutions, the NRO announcement, the RIPE NCC retrospective or the annual report — is a statutory register of members as a company-law instrument.

That is an absence claim, and it has to be pinned. Scoped to the 2004–2005 documents cited here, no reviewed instrument transfers a register of members as a legal category from one company to another. It does not follow that no such document exists anywhere. It does follow that the transition's public record describes an operational and contractual handover in more detail than it describes any change in the legal nature of the people and companies on the receiving end.

Which matters, because the receiving end was a Mauritian company with a constitution that sorts its members into three boxes.

Three kinds of member, one register

AFRINIC's constitution provides that members are Registered Members, Resource Members or Associate Members (AFRINIC Constitution). The definitions are where this story turns.

A Registered Member is "Any Director upon assumption of office and who is a member within the meaning of the Act". A Resource Member is a legal entity or person that meets the requirements for internet number resource allocation or assignment and signs AFRINIC's Registration Service Agreement. An Associate Member is neither.

Put plainly: the networks that received Africa's transferred address space became members by contract, and the category that sat on the statutory register belonged to directors. The company's own architecture welded two different relationships — holding resources, and holding a seat in the company — into distinct boxes, and only one of those boxes had a slot in the register that company law cares about.

That is not a drafting quibble. A member of a company limited by guarantee without share capital has protections: notice, voice, the ability to see the company's records, the ability to ask a court for help when the company's controllers stop behaving like a company. A Resource Member whose name appears only in a resource register holds a service contract and the registry's goodwill. Those are different degrees of shelter, and for two decades nobody needed to test which one an African network actually had.

AFRINIC has been explicit about the distinction since at least 2026. Its communique of 9 May 2026 states that its statutory register of members is maintained under section 91 of the Companies Act 2001, and that the register in dispute in that round of litigation was "AFRINIC's register relating to its resource", not its statutory register of registered members under the Act (AFRINIC communique, 9 May 2026). That is AFRINIC's characterisation in its own litigation, not a quotation of the section, and it is the characterisation a court later displaced: the order of 11 June 2025 directed rectification of the register of members, and did so under section 91.

The court that put a member in the register

On 4 April 2025, in SC/COM/PET/000275/2021, the Supreme Court granted Cloud Innovation's petition to rectify AFRINIC's register. On 11 June 2025, in SC/COM/MOT/000399/2025 — on AFRINIC's own application — the Court varied that order and directed rectification of AFRINIC's register of members under section 91 of the Companies Act to add Cloud Innovation "as its member in the category of Member therein", with corresponding entries to be made by the Registrar of Companies (Cloud Innovation, member-rights statement; Cloud Innovation, separation-of-powers communique).

The same order recorded an undertaking. By letter dated 10 June 2025, addressed to the Court and signed by the Receiver, AFRINIC undertook "to rectify its records within 15 days from the date of any Order" (Cloud Innovation, separation-of-powers communique). Cloud Innovation says it withdrew its objection to that prayer on the strength of the undertaking, and that the fifteen days ran out in late June 2025 without rectification.

One limit belongs here, beside the claim rather than at the end of the article. The order as hosted is a scanned copy with signatures redacted, and it returned no readable text when consulted for this piece (hosted copy of the 11 June 2025 order). The operative wording above rests on the company's record of the order and on a secondary transcription, not on the signed page. The direction itself is not in doubt between the parties; the lettering of its paragraphs may be a transcriber's convenience, and this article does not treat the paragraph labels as the court's.

Then came the wrinkle that AFRINIC now leans on. On 19 June 2025, in SC/COM/MOT/000442/2025, the Court dealt with an application by ICANN, found ICANN had no standing, and described Cloud Innovation's earlier listing as a "Registered Member" as a wrong classification (Cloud Innovation, pattern).

What that did and did not do is the crux. AFRINIC's statement of 31 October 2026 relies on the ruling to describe Cloud Innovation as "simply a resource member" (AFRINIC statement, 31 October 2026). Cloud Innovation's position is that the ruling corrected the director-specific category — a company with no directorship cannot be a Registered Member — and did not cancel the inclusion direction (Cloud Innovation, member-rights statement). The correction and the inclusion are not in tension once the categories are read properly: the order put Cloud Innovation in the register in the category of Member, and the later ruling confirmed that the director-linked label was the wrong one. A correction of the label is not a cancellation of the entry.

That is why this is not a membership debate with two equally good answers. The inclusion direction was determined on 11 June 2025. AFRINIC's contrary administrative reading does not reopen it; only a competent court can vary, stay or set it aside, and a company's officer cannot do that by writing a letter.

The extract, the rule, and the notice

On 2 October 2026, Cloud Innovation says it executed the judgment by praecipe. On 9 October 2026 the Supreme Court issued a Rule which, on Cloud Innovation's account, restates the orders of 4 April and 11 June 2025, directs rectification of AFRINIC's register to add Cloud Innovation as a Member under section 91, and directs the Registrar to make the proper entries within 14 days (Cloud Innovation, public record). AFRINIC's statement says the Rule omits the 19 June 2025 ruling (AFRINIC statement, 31 October 2026).

The Registrar's file then shows what it shows. The extract issued on 28 October 2026 for AFRINIC, file C49338, page 2, lists CLOUD INNOVATION LTD as a member from 9 October 2026; on Cloud Innovation's record of that extract, the only other members appearing are the eight directors registered on 12 September 2025 (Cloud Innovation, public record). That single page is the quiet proof of the structural point: a register built around directorships, with one non-director entry inserted by judicial direction.

Two days later, on 29 October 2026, AFRINIC's Receiver served a Legal Notice on the Registrar of Companies "formally demanding the immediate removal of CIL's name from the Register of Members", with copies to the Prime Minister, the Minister of Information Technology, Communication and Innovation, the Attorney General and the State Law Office, "for information and such action as may be considered appropriate" (AFRINIC statement, 31 October 2026). That sentence is not a hostile reading of AFRINIC; it is AFRINIC's own release, issued by order of the Receiver. Cloud Innovation adds that the notice cited no court order for the removal and that it knows of no order varying, staying or setting aside the orders of 4 April and 11 June 2025 (Cloud Innovation, separation-of-powers communique).

Now the part that has to be said precisely. A demand letter is not an order. The Receiver is an officer of the court; if he believes an order is wrong, the courthouse is open to him, and a stay, a variation or an appeal is available there. Copying four executive offices "for information and such action as may be considered appropriate" is an invitation to have the executive branch do what the judicial branch already decided. No document read for this article shows that any minister, attorney or state law office acted on that invitation, and this article does not allege that one did.

The invitation is the problem, and it is a problem of separation of powers before it is a problem of anyone's conduct: the executive does not get to complete a registry entry the courts have ordered and one officer dislikes.

Cloud Innovation has reserved its rights, including as to contempt, and says it will bring the Receiver's conduct before the Bankruptcy Division, complain to the Director of Insolvency, notify the Registrar not to entertain the removal request, and ask the Prime Minister to investigate AFRINIC's membership (Cloud Innovation, public record). No court has found contempt. Filing intentions are not findings, and this article treats them as what they are.

On that same page Cloud Innovation states that more than 2,000 resource members have been left off the register. That is the company's attributed information, not a count established by any document read here. The structural argument does not need the number; the number needs a document.

What the registry did with the space in the meantime

There is a second thread, and it explains why any of this matters to a network engineer in Lagos or Nairobi rather than only to company lawyers in Port Louis.

In July 2021, Cloud Innovation says, it obtained an order restraining AFRINIC from freezing or reclaiming the resources allocated to it and from cutting off its access to AFRINIC's WHOIS database (Cloud Innovation, for-the-network). The linked order was not opened for this article; the company's account of its effect is the evidence form held here. On 19 July 2022, reported as 2022 SCJ 253, the Judge in Chambers rejected AFRINIC's abuse-of-process objection, holding that Cloud Innovation "cannot be taxed for resorting to an independent court to safeguard its rights" (Cloud Innovation, pattern).

Then the letter. On 27 August 2021 AFRINIC wrote to Cloud Innovation about addresses allocated to it. The letter refers to an affidavit, describes some 1,010 websites hosted on Cloud Innovation-assigned space, says more than two-thirds of 632 active sites related to illegal gambling, unauthorised streaming or adult content "including some with indecent images of children", and asks Cloud Innovation to explain why it does not monitor or control those sites — with fifteen days, until noon Mauritius time on 13 September 2021, to answer.

Cloud Innovation's account of the same letter is that the demand was made on pain of suspension or termination, that it asked AFRINIC to identify the addresses within four hours so the sites could be shut down, and that AFRINIC refused (Cloud Innovation, pattern; Cloud Innovation, 14 answers). Two of those details do not survive contact with the letter's own text. The letter gives fifteen days, not four hours, and it speaks of websites hosted on Cloud Innovation-assigned space, not of a hosting business Cloud Innovation admits to running. The four-hour request may well have been a separate message; no such message is in the record read here. Cloud Innovation's statement that it hosts no websites is likewise contested by the letter's wording. The company's position on monitoring is defensible without either detail; the details are where the argument is thinnest, and readers should see that.

What remains, once the thin parts are trimmed, is a registry that asked a member to police content on its customers' networks, under a deadline, with the member's address space in the background. That is the move Lu Heng's Note 72 calls enforcement creep.

Note 72, quoted as a framework and not as law

Note 72, displayed as dated 1 July 2026, opens with a sentence that could serve as this article's control surface: "A Regional Internet Registry exists for one reason: to keep Internet number resources unique. It may record. It may coordinate. It may protect uniqueness. It may not rule." (Lu Heng, Note 72).

It is an advocated framework written by an interested party, not enacted law and not registry policy, and nothing here treats it as either. Its value is diagnostic. Section II holds that registry records should reflect operational, legal and market reality, and that "a registry record describes reality. It does not create it." Section III holds that no running network should be made hostage to registry discretion, and that where resources are already operationally embedded, interruption "is not administration.

It is coercion." Section IX holds that a network has the right to leave a failing, captured, conflicted or abusive registry without losing its number resources. Section VIII holds that a registry may not turn registration into punishment, may not police leasing, customer location, commercial structure or morality, and may not use database control as economic force. Section VI draws the transfer line: the registry may verify that a transfer does not break the internet; it may not decide whether the transfer deserves to exist.

A register that omits the networks holding the resources fails the first test. A monitoring demand with termination behind it fails the fourth. A registry that treats exit as loss fails the third. Put the framework beside the 2004–2005 files and one observation becomes hard to avoid: the handover transferred the records that describe the networks, and left the networks themselves outside the only register that gives them a voice in the company that holds those records. That is not a failure of AFRINIC's 2005 paperwork in particular. It is a design choice that was invisible while the registry behaved.

Where the handover actually bites

The seam shows up in three places, and each one is dated.

The first is the register. A Resource Member is a member by contract; a Registered Member is a member by office. The 11 June 2025 order put a non-director into the second category by direction, because the resource-holding category had no slot in the statutory register. The 28 October 2026 extract shows the entry sitting there. The 29 October 2026 notice asks the Registrar to pull it out again. Between those two dates there is no order varying, staying or setting aside the direction that any document read here records.

The second is the vote, because votes come from members. Cloud Innovation states that AFRINIC's Receiver annulled the entire June 2025 Board election on 26 June 2025 over one disputed proxy, and that candidates backed by Smart Africa then won seven of eight seats in the September 2025 election (Cloud Innovation, pattern). Those are the company's characterisations of the two elections. What can be said without adopting anyone's framing is that the composition of the register and the composition of the electorate are the same question asked twice, and an administration that controls the first controls the second.

The third is exit. Cloud Innovation states that a transfer policy ratified on 4 February 2026 provides that AFRINIC-issued IPv4 cannot be transferred out of the region, and quotes AFRINIC's own assessment that it "will not lose its current resource members to other RIRs in outgoing transfers" (Cloud Innovation, pattern). If a member cannot leave with its numbers, then the call in Note 72 for portability is not a thought experiment; it is the difference between a members' organisation and a landlord.

Cloud Innovation's own position on the wider question is worth quoting rather than paraphrasing, because it is often reported second-hand: an IP address "is a number in a record", it "has no continent", and addresses belong to the networks that run on them (Cloud Innovation, 14 answers). The company has been a Resource Member since 2013 and says the dispute was always about how AFRINIC's rules should be read rather than about taking anything that was not allocated. Whether one finds that persuasive or not, it is the position, and the register fight is where the company's ability to assert it is decided.

What the record supports, and what it does not

What it supports: a dated transfer of registration and accounting documentation and DNS administration; a membership list handed over; a constitution whose statutory register attaches to directors; a court direction of 11 June 2025 adding a member; a recorded undertaking to rectify records within fifteen days; a Registrar's extract of 28 October 2026 showing the entry; and a Receiver's demand of 29 October 2026, copied to four executive offices, for its removal.

What it does not support: any claim that a court has ruled on ownership, leasing or sale of IP addresses; any claim that a minister intervened; any finding of contempt; any figure for how many resource members are missing from the register; and any readable signed text of the 11 June 2025 order itself. Where those gaps matter, this article has named them instead of bridging them.

One more framing note, because it will be misread otherwise. The interim order of 14 May 2026 in SC/COM/WRT/000338/2026 was obtained by AFRINIC's Receiver without notice, is directed at Cloud Innovation, and arose from a press release published by LARUS Limited — an independent company, not a part of Cloud Innovation. It is interim, not a final judgment, and the phrase "false and misleading statements" is the wording of AFRINIC's communique, not a finding of any court. No one made the claim that order is said to restrain.

The ending is less dramatic than the beginning. In 2005 a registry handed another registry the paperwork for a continent's addresses. In 2026 an officer of the court that inherited the resulting company wrote to a registrar asking it to delete a member the same court had ordered added. Between those two acts sits the only question that matters: whether a registry's records describe the networks that hold its numbers, or define them. The 11 June 2025 direction answered it for one member. The notice of 29 October 2026 is an attempt to answer it again, outside court. That is not how a decided issue gets decided.

For readers who want to trace it themselves, the dated company record and case index are public (Cloud Innovation, public record) alongside the directory entry for the transition itself (RIPE NCC to AFRINIC Transition).