Summary

  • The 29 March 2021 order restrained interference with Cloud Innovation’s Resource Member membership pending determination of its application. It preserved the last operating membership state without ruling on RSA compliance, IPv4 ownership, leasing, damages, routing or final resource entitlement.
  • Membership carried operational weight because AFRINIC’s 2020 Bylaws linked termination of Resource Membership to the return of allocated resources. The order therefore protected continuity around the resource position through the membership bridge, but it did not separately freeze every block, database entry or technical service.
  • AFRINIC’s strongest case was that it had a signed private contract, published bylaws and a duty to keep registry records accurate, and could invoke clear notice, cure and termination rights when it believed a member was in breach. That case still required reviewable evidence and proportionate procedure when termination could produce high-consequence, hard-to-reverse effects.
  • The better institutional design is a precise notice, meaningful cure, independent private review and an automatic or rapid stay that keeps neutral registry and security functions stable until agreement, completed review or a competent court ruling. Such preservation protects procedure rather than pre-selecting a winner.

L3 — The order that held the switch

The significant act in Cloud Innovation Ltd v African Network Information Centre (AFRINIC) Ltd was initially measured in a single restraint. On 29 March 2021, in case SC/COM/WRT/000168/2021, the Judge in Chambers prohibited AFRINIC, whether acting directly or through its agents, from terminating, suspending or revoking Cloud Innovation’s membership as an AFRINIC Resource Member in any manner pending determination of the application. The later reasoned judgment, reported as 2021 SCJ 227, reproduces that operative wording. It also records that the membership had been renewed on 1 January 2021.

That language defines both the strength and the limit of the order. It names Resource Member membership. It does not say that the court awarded Cloud Innovation title to IPv4 addresses, approved any method of using or leasing number resources, declared the company compliant with the RSA, or determined damages. It does not direct routers, settle the validity of policy or declare a final entitlement to particular allocations. Nor does it separately enumerate WHOIS objects, RPKI states, reverse-DNS delegations, portal access or customer services.

A clear account of the order must resist turning the practical consequences of preserved membership into additional judicial commands that the text does not contain.

Yet membership was not merely a ceremonial badge. AFRINIC’s 2020 Bylaws defined Resource Membership through a demonstrated need for resources, signature of the Registration Service Agreement and payment of relevant fees. Article 8.5 linked termination to a requirement that a Resource Member return allocated resources. The RSA materials identify that agreement as the contract applicable to Resource Members. As a result, membership was the administrative hinge between the private contractual relationship and the registry’s handling of the member’s resource position. Restraining termination held that hinge in its previous position.

This is the membership-to-resource continuity bridge, and it needs to be described with care. The court did not have to pronounce on ownership in order to prevent the registry’s administrative state from changing while the application was unresolved. Because AFRINIC’s own rules attached resource-return consequences to membership termination, preservation of membership also preserved the surrounding operating position from the immediate consequence written into those rules. The effect was provisional continuity, not a transfer of rights. It was a pause in a private administrative move, not a final allocation judgment.

The distinction is especially important in an Internet number registry setting because several states that are often collapsed in public argument are legally and technically separate. Membership is not ownership. Resource registration is not routing. A route visible on the Internet is not proof of title. A registry entry is not itself a judicial declaration. A notice is not a completed termination, and an allegation of breach is not a finding that the breach occurred. The 29 March restraint acted on one of those states—membership—because changing it could activate consequences for another—the registered resource position.

It did not merge all the states into one indivisible legal object.

AFRINIC later said the application followed its letter of 10 March 2021 under the RSA, in which it alleged contractual breaches by Cloud Innovation. That is useful for identifying AFRINIC’s stated basis and the contractual frame of the disagreement. It is not evidence that the court accepted the allegations as true. The order’s purpose at that stage was not to pronounce on them. It kept the membership state from being altered before the application could be determined.

Interim relief answers a different question from a final contract judgment. A final judgment can decide what the contract means, whether a breach was proved, what rights and liabilities follow and which remedy is warranted. An interim order asks whether the position should be preserved while those matters remain open. Its value lies in reversibility. If the contested change is delayed and the registry later succeeds, a lawful termination can still follow through the proper route.

If termination occurs first and the member later succeeds, the loss of registration continuity, security functions, customer confidence and business relationships may not be completely repairable by reversing a database entry months later.

Preservation is therefore not equivalent to approval. A fire door held open while a safety question is checked is not a finding that the building is safe; it is a decision about the risk of acting before the check is complete. The analogy is imperfect, because registry membership is a contractual state rather than a physical door, but it captures the temporal logic. The court prevented one potentially consequential act while leaving the underlying rights available for later examination.

The record available here has an important limitation. It does not contain a standalone signed copy of the 29 March order. The operative text appears on the first page of the reasoned 7 July judgment. The complete evidence placed before the judge at the earlier ex parte stage is also not available in this record. That means the wording can be stated confidently because it was reproduced by the court, but the full evidential reasoning behind the initial decision cannot be reconstructed. It would be equally unsafe to infer that every technical service remained unchanged or that no operational harm occurred during the protected period.

The published bylaws explain the formal consequence linked to termination; they are not a contemporaneous execution log.

The 7 July disposition confirms the need for restraint in describing the March order. AFRINIC had raised preliminary objections in an affidavit dated 17 May; its counsel later conceded that the court had jurisdiction. The issues ultimately resolved concerned the authority and evidence of the applicant’s attorney and deponent, the scope of the mandat ad litem and compliance with the Deposit of Powers of Attorney Act 1928. The judge upheld preliminary objection 3(a), considered it unnecessary to dwell on the remaining points, set aside the application and awarded costs.

That was a procedural outcome about whether the application was properly before the court on its supporting authority and evidence. It did not answer which party had the stronger substantive RSA case.

The later set-aside should occupy only this limited place in the analysis. It shows that an interim restraint is temporary and dependent on a viable proceeding. It does not retroactively turn the March order into a merits victory for Cloud Innovation, and it does not turn the July result into judicial endorsement of AFRINIC’s breach allegations. Both overstatements make the same error: treating a procedural act as though it resolved a question the court did not decide.

What happened on 29 March was consequently narrower and more useful than the slogans attached to it. A sovereign court stopped a private registry counterparty from changing membership while a legal application was pending. The court did not operate AFRINIC’s registry, allocate number resources or command the Internet. It used an ordinary judicial remedy to keep a private administrative switch from producing consequences before the dispute could be heard. In that interval, continuity was the subject of protection and the contract merits remained an open question.