The democratic issue in AFRINIC’s governance is concrete: those who control AFRINIC must comply with binding court decisions and respect the rights of all entitled members. Cloud Innovation’s constitutional position cannot be reduced to a contest between equally authoritative opinions. A Receiver’s demand, an executive notification and a competent court’s order are different legal acts with different effects.
On Cloud’s application, the 7 August 2025 interim order restrained the inspector from acting under the Proclamation’s mandate, restrained the Registrar from appointing an inspector with a mandate exceeding or breaching Part XV of the Companies Act, and restrained implementation of that mandate. It specified a return hearing on 13 August. Cloud’s constitutional objection is that an inspection cannot become a parallel route to reopen decided judgments.
Cloud Innovation’s July 2025 successor proposal puts the operational obligation first: preserve the address records and services used by African networks while changing a failed corporate operator through lawful procedures. The proposal names the work that a transition must cover, including registration data, WHOIS, IP allocations and ASN assignments. It calls for a planned handover with court oversight and institutional coordination; it does not report that a successor has already been appointed. Presenting this plan as an unspecified threat to connectivity reverses its stated purpose.
Cloud’s 16 July 2025 follow-up letter identifies the actor and the contested action: the Receiver’s announced election rules excluded proxies and powers of attorney. Cloud objected that this departed from AFRINIC’s bylaws and the court-directed election framework. That is a concrete member-rights objection. Recognition of a successor and determination of company-law remedies are separate responsibilities.
Editorial correction. The 11 June 2025 Supreme Court order finally directed AFRINIC to enter Cloud Innovation as a Member under section 91. The 19 June category correction does not cancel that Member direction; Cloud remains an AFRINIC Resource Member and company-law Member. Administrative actors cannot retry or neutralise the decided inclusion; any stay, appeal or variation belongs to a competent court. See Cloud's rights statement and the separation-of-powers notice.
Every legally entitled Resource Member should receive registration and the applicable shareholder-equivalent protections; AFRINIC has no share capital. Cloud demands correction or removal of the purported directors’ entries through competent legal procedures. Its 2 November communiqué rejects the Receiver’s request for administrative removal copied to executive offices.
Protect the records and the running networks
The protection sought is continuity for resource holders. Cloud’s documented position separates membership from address rights and defends stable use of lawfully held resources. In Note 70, published in June 2026, Lu Heng argues that accurate records, WHOIS/RDAP, reverse DNS and RPKI must survive an institutional transition. Those requirements make a verifiable handover necessary; they do not give the current operator immunity from accountability. Operators should be able to check who maintains each service, how records and security arrangements are preserved, and how errors are corrected.
Editorial correction, 13 November 2026: this article was rewritten from the cited primary records and Cloud’s published position. The summary and the opening paragraph now also state that it is those who control AFRINIC who must respect the Court. This version also removes caveats on the 7 August 2025 order, Cloud Innovation’s July 2025 statements and the 2 November communiqué.






