Summary

  • AFRINIC's statement of 31 October 2026 objects to "the purported entry of Cloud Innovation Ltd on the Register of Members kept by the Registrar of Companies" and says it has served a Legal Notice demanding immediate removal. It describes no revocation of number resources, no route withdrawal and no operational injunction.
  • A remedy binds one named party in one proceeding; a rule binds how an institution may treat a whole class of members. Reading a register-correction demand as the second when it is the first is the mistake that turns an administrative step into an imagined constitutional settlement.

The sentence is short, and it is worth reading twice, because almost everything else written about this dispute reads past it. AFRINIC, the regional internet registry for Africa, published an official statement on 31 October 2026 saying it "strongly objects to the purported entry of Cloud Innovation Ltd on the Register of Members kept by the Registrar of Companies" and that it "has served a Legal Notice demanding its immediate removal" (AFRINIC statement, 31 October 2026). The same statement sits on AFRINIC's own front page (AFRINIC).

Notice what the demanded remedy is. Not the withdrawal of an allocation. Not the revocation of a membership certificate held in the registry's own database. Not an order restraining a network from announcing prefixes. The object of the demand is an entry in a companies register — a book kept by a statutory officer, in which the members of a company are listed. AFRINIC is asking that a line in that book be deleted.

That is a narrower instrument than the language surrounding it suggests, and the narrowing is not a technicality. It tells you which question the registry has chosen to fight, and which question it has, on this record, left alone.

Two books, two questions

A regional internet registry keeps several kinds of record, and they are not the same kind of thing. There is the register of who holds which number resources and under what agreement. There is the routing system, which is not a register at all but a live conversation between networks. And there is, separately, the corporate existence of the entities that hold membership — who their members are, who their officers are, whether they stand validly constituted under the law that created them.

AFRINIC's 31 October 2026 statement engages the third of those. It does not engage the first two.

This distinction is not pedantry; it is the whole mechanism. Deleting an entry from a register of members changes the legal list of who belongs to a company. It does not, by itself, move a single address block, terminate a single agreement, or alter a single routing announcement. The book and the network are different instruments, kept by different institutions, under different law, and they fail in different ways.

So the honest description of what AFRINIC has done is this: it has opened a front on the layer where standing is recorded, while the layer where resources are held and used continues to run. That is a legitimate strategic choice. It is also a choice with a specific shape, and the shape matters to anyone whose holdings depend on which layer the next move lands on.

What the record does not say

Here the discipline has to bite, because the material available is thinner than the commentary around it.

AFRINIC's news page also carries a communiqué dated 15 May 2026 referring to a judgment of the Supreme Court of Mauritius delivered on 14 May 2026. The excerpt that survived retrieval stops inside that sentence, at the point where the judgment is about to be described. Its operative effect therefore cannot be stated here at all — not the orders, not the reasons, not which party it favoured (AFRINIC news page). The same page lists earlier communiqués referring to court orders of 19 June 2025 and 5 September 2025 in the matter Cloud Innovation Ltd v G Dabee & Anor, Case Ref SC/COM/WRT/000599/2025. That establishes a running proceeding and a case number. It does not establish what any order decided.

CircleID's commentary on the dispute reports more, and its reporting is worth naming precisely because it is reporting. According to that account, an interim order of 14 May 2026 restrained Cloud Innovation from representing that the court had authorised leasing or commercialising AFRINIC-allocated number resources, and the judge considered an affidavit from TESPOK when granting ICANN leave to intervene. The same commentary reports that AFRINIC learned of the register entry on 28 October 2026 and that the receiver demanded removal on 29 October 2026, two days before the public statement (CircleID).

Read that reported restraint carefully, because its grammar is the argument. It restrains a party from saying something. A prohibition on a representation is the most minimal kind of judicial intervention available: it forbids a claim, not an act; it protects a court's authority from being borrowed, without deciding the underlying entitlements. A negative restraint of that kind is not a direction to a registry to amend a policy, and it is not a finding that resources were wrongly held.

The limits of this review should be stated once, plainly. The operative judgment text and reasons, AFRINIC's bylaws and membership contract, the Registrar of Companies filing and the Legal Notice itself were not obtained. Two retrieval attempts were spent on that instrument class and neither returned them: one ended with provider capacity unavailable, and one returned no accessible document at the pages queried. That is a statement about the scope of this review, not a finding that those documents do not exist.

Several questions therefore stay open: whether any order addressed AFRINIC's revocation procedure rather than Cloud Innovation's conduct, whether AFRINIC's own conduct has been found unlawful, whether the register entry has since been removed, and whether any number-registry-side process is pending alongside the Legal Notice. The record shows only that the statement describes none.

Why the registrar is the cheaper venue

An institution choosing where to fight is choosing what it must prove. Before a court on a resources question, a registry has to establish that a holder's title is defective, that a revocation was properly grounded in the applicable agreement and policy, and that the process met whatever standard of fairness the governing documents impose. Those are hard, documentary, contestable propositions.

Before a companies registrar, the question is different in kind. It is whether a record is accurate: whether the person listed as a member is in fact a member, and whether the filing that put them there was properly made. That is a question about the state of a book. It is cheaper to ask, faster to answer, and — crucially — it does not require anyone to litigate the operational entitlements at all.

This is the asymmetry that deserves attention. A challenge to an address-holder's standing can be prosecuted through a corporate registry while the addresses themselves continue to be held and announced. Recognition and operation are separable layers, and the separation is visible the moment you look at which institution received the demand. The registry's real lever, on this record, is recognition — the power to determine who counts as belonging — and it is being pulled where that lever is cheapest to pull.

There is a second-order point here for the governance argument. Commentators who describe litigation of this kind as reform of a registry's internal constitution are describing an outcome the instrument does not deliver. A court order that restrains one company's public statements, plus a demand that a registrar correct one entry, may constrain a named party's conduct in a specific proceeding. Neither is a rule about how the registry must treat its members in future.

Confusing remedy with rule is how a private dispute gets mistaken for a constitutional settlement — and it flatters whichever side is currently winning the press cycle.

The chokepoint ahead

The reason this is not a merely semantic distinction is that registers get used as premises. A deleted membership entry is not inert. It is a fact that a later litigant can point to when arguing that a holder lacks standing to complain about anything at all — that it is not a member, therefore not entitled to the procedural protections membership confers, therefore not a proper party to contest a policy decision.

That is the forward risk, and it is worth naming as a conditional rather than a prediction. Nothing in the material reviewed here establishes that any such argument has been made or is planned. But the structure invites it. If the corporate register is where recognition is settled, then control of the corporate register becomes a chokepoint upstream of every operational question downstream. The resources keep flowing while the standing that would let someone defend them is quietly relocated into a book in a different building.

For a holder, the practical lesson is unglamorous: keep both kinds of record in good order. Corporate filings and registry agreements fail on different grounds, and a holder who has defended the first has not thereby defended the second.

Two tests that would settle it

A thesis that cannot be falsified is a mood, not an argument. Two observable developments would decide this one.

If the operative paragraphs of the judgment rest on the membership contract or the registry's bylaws and order correction as between the named parties — restore this entry, restrain this representation, settle this account — then the private-dispute reading holds, and nothing about how the registry treats other members follows from it. The instrument stays a remedy.

If, by contrast, operative paragraphs direct AFRINIC to amend a revocation or admission procedure in terms that apply beyond the named respondent, then this reading fails and must be replaced. An order that changes the rulebook is a rule, whatever the caption of the case, and the governance-reform framing would then be earned rather than assumed.

Until one of those developments is on the record, the responsible description of 31 October 2026 is the narrow one. A registry asked a registrar to delete a line. That is a real move, aimed at a real vulnerability, in a dispute where the addresses are still moving and the book is being edited. The register is not the routing table. Confusing them is how institutions win arguments they have not yet had.

Sources