Summary

  • On 8 October 2025, AFRINIC’s Receiver filed an “Application for Termination of Receivership”; the Board and Receiver said this began, rather than completed, his formal release.
  • AFRINIC’s public case list returned on 11 August 2026 with the “Application for discharge of receiver” in row 86 and its status marked “Ongoing” — a 307-day interval from filing.
  • During that interval, AFRINIC said its Interim Management Committee would report jointly to the Board and Receiver, while CEO-search, NRO/ASO and bylaws-review decisions relied on Receiver consent.
  • The closed 16-source packet does not contain a discharge order, the Receiver’s filed report, signed consent instruments, a function-by-function delegation matrix or a final handover inventory. Those records may exist elsewhere.
  • The evidence does not prove the Board, Receiver or any decision unlawful. It proves that an election did not by itself end temporary control, while public descriptions of collaboration stopped short of showing who could bind AFRINIC on each material function.

Row 86 is the unfinished transition

The most consequential entry on AFRINIC’s public case page is not a new accusation or judgment. It is one word in the status column: “Ongoing”.

Row 86 identifies a matter dated 8 October 2025 involving AFRINIC in receivership, Receiver Gowtamsingh Dabee and 12 interested parties. The nature of the matter is “Application for discharge of receiver”. When BTW retrieved the page on 11 August 2026, it returned HTTP 200 and still carried that status. The page is maintained by AFRINIC; it is not presented here as the Supreme Court’s own independently verified docket.

The elapsed time is nevertheless a public fact. There are 307 calendar days between the listed filing date and the retrieval date.

That number matters because AFRINIC’s first description of the filing was careful. In a joint statement published on 13 October, the announced Board and Receiver said Dabee had filed a report titled “Application for Termination of Receivership”, thereby “initiating the process” for formal release. A decision was awaited. Until formal discharge, the statement said, the Receiver would continue supporting implementation after the appointment of directors.

An application is a request to a court. It is not the order sought. An election produces names. It is not, by itself, the documented transfer of every corporate, technical and operational power held during receivership.

The 307-day interval is therefore not empty time. It is the period in which two centres of authority appeared together in AFRINIC’s own records.

The verbs reveal a dual chain

The October statement used the language of close collaboration. It also described actual decisions.

The Board had constituted Finance, Audit, Remuneration and Legal committees. The Legal Committee was asked to take stock of ongoing cases and optimise legal resources. The Receiver, not the Board, had appointed Forvis Mazars as external auditor for 2022, 2023 and 2024, under what the statement called exceptional circumstances. Board and Receiver were working together on CEO recruitment. The Board was reviewing resource allocations and member rights that remained before the courts.

On 19 November, the chain became more explicit. AFRINIC said the Board created an Interim Management Committee with the Receiver’s consent. That committee was to oversee day-to-day operations across finance, technology, infrastructure, governance and member engagement — and report jointly to the Board and Receiver. The CEO Search Committee was also constituted with Receiver consent. So was the decision to appoint an AFRINIC representative to the NRO Number Council and ASO Address Council.

The same structure was still visible on 2 March 2026, when AFRINIC said the Board constituted its Bylaws Review Committee and appointed its chair with Receiver consent. Ten days later, a member update said the Board was collaborating with the Receiver pending his formal discharge. It said the discharge application had been heard and judgment was awaited. It also said the Receiver was approving IP allocations.

Those are not ceremonial functions. Day-to-day management directs staff and systems. An external audit touches accounts and statutory reporting. Litigation strategy determines which claims a company advances and what it pays to defend them. Bylaws define internal power. IP allocations alter the registry state relied on by networks.

AFRINIC’s statements may describe a legally necessary transition. Nothing in this packet proves that the overlap was unlawful. But “working closely”, “with the consent” and “report jointly” do not answer the operational question: for each category of act, who had final authority to bind the company, who performed the technical assessment, and who carried responsibility if the decision caused harm?

The mandate began with preservation and restoration

The public starting point is narrow enough to quote accurately. AFRINIC’s February 2025 appointment notice says Dabee was appointed Receiver in place of the Official Receiver under cause SC/COM/MOT/000082/2025. It states that the appointment aimed to secure the company’s assets and see that its Board was reconstituted in accordance with the bylaws.

AFRINIC then announced eight election winners on 12 September. That announcement proves the result AFRINIC published. It does not, without a final judicial record, settle every challenge to the election or define the legal effect of the resulting Board.

NRS maintains that the September election was not lawfully or conclusively completed and that material issues remain disputed. Its June 2026 member action asks for transaction-specific evidence: the Board resolution, delegation, Receiver instruction and court authority used for each step. These are NRS’s positions, not court holdings.

The distinction protects this briefing from both institutional shortcuts. AFRINIC cannot turn “the membership elected” into automatic proof that all temporary powers had already returned. Its critics cannot turn an unresolved challenge into automatic proof that every later act was illegal.

The harder, documentable conclusion sits between those claims: AFRINIC announced a Board, but its own later notices continued to place the Receiver inside the approval and reporting chain.

The public packet shows results, not the authority map

The exact 16-source packet used for this briefing contains no order discharging the Receiver. It contains no copy of the report he filed on 8 October. It contains no court-approved handover plan, complete delegation matrix or inventory recording the custody of credentials, contracts, open member requests, litigation instructions and pending registry decisions.

Nor does the packet contain the signed Receiver-consent instruments behind the November management and appointment decisions or the March bylaws committee. The announcements say consent existed; they do not show its date, legal basis, scope, conditions or duration.

This is a bounded absence. The documents may sit in a private company record, a court file or a public location outside the frozen packet. Their absence here does not prove they never existed, that the statements were false or that the acts were invalid.

It does identify what members cannot reconstruct from the public record. Could the Board instruct staff without Receiver approval? Could it sign a long-term vendor contract? Who authorised a contested allocation? Who controlled privileged registry credentials? Did the Receiver approve individual decisions or categories of decisions? What event ended a delegation? Which acts would survive a later adverse ruling?

The phrases used by AFRINIC supply no function-by-function answer.

Power is the approval path, not the title

Heng Lu’s doctrine makes the analytical error visible. Institutional titles and regional representation are the outer language of governance. Actual control lies in the structures that can approve, block, delegate and enforce decisions. The network or resource holder bears the operational and asset downside when those decisions go wrong; the committee or temporary office often does not bear comparable liability.

Applied here, the important unit is not “Board” or “Receiver” in the abstract. It is the approval path for each material act.

If an allocation altered AFRINIC’s registry, whose legal authority approved it, whose technical capability assessed it and whose record can later be audited? If the Legal Committee directed litigation, which organ authorised the instruction and accepted the cost? If the Interim Management Committee reported to two principals, what happened when their instructions differed? If the Bylaws Review Committee was created with Receiver consent, what limit prevented a temporary authority from shaping the terms under which permanent authority would later operate?

These questions are not a demand that sensitive credentials, member data or litigation advice be published. They are a demand that public power be described more precisely than a shared press release.

The agency problem is acute because continuity creates its own incentives. Staff need instructions. Vendors need signatories. Registry requests cannot wait indefinitely. A Board wants to demonstrate that ordinary governance has returned. A Receiver needs to preserve the company until the court releases him. Each actor can reasonably favour a functioning process. Members and networks, however, bear the consequences if the wrong office approves an irreversible act.

Continuity may justify action. It does not eliminate the need to identify the authority used.

A handover receipt would make the overlap auditable

A credible transition need not publish every confidential document. It can publish a compact authority register.

For each function — finance, staff direction, contracts, litigation, resource allocation, RPKI, Whois and RDAP changes, DNS, security credentials, policy work and constitutional reform — the register would name the current corporate approver, the legal source of power, any delegate, the technical reviewer, the duration, conflict controls, reversibility and escalation route. Each Board resolution or Receiver instruction would cite that register.

Receiver consent should leave a receipt: date, signed instrument, subject, scope, conditions and termination event. A committee reporting to two offices should have a written rule for conflicts. High-impact registry actions should preserve a decision record that separates legal approval from technical execution.

The final court discharge should then trigger a handover certificate. It would record control of bank mandates, contracts, litigation files, privileged accounts, signing systems, open member queues, unresolved incidents and decisions made under temporary authority. Independent assurance could confirm the inventory without exposing secrets.

This counterfactual does not require the court to operate a registry or the public to read security-sensitive files. It requires AFRINIC to show how temporary corporate power entered live Internet administration and how it left.

The evidence supports a sharp but bounded conclusion. The October filing began a Receiver exit; it did not complete one. Over the following 307 days, AFRINIC’s Board acted while repeatedly invoking Receiver consent, and its management structure reported to both. The packet does not prove illegality or personal wrongdoing. It proves that practical power crossed the supposed handover before the public record supplied a complete map or a final receipt.

For the deeper operational analysis of what a Receiver-controlled Internet registry must hand back, the separate BTW research below carries the long-form file. This briefing reports the new dated event: the exit application remained publicly ongoing while dual authority continued to govern.

Sources