Summary

  • AFRINIC’s public Case List says Skyconnect, formerly Skyvision Guinee SA, filed SC/COM/PWS/000132/2026 on 9 March to challenge the Board’s ratification of AFPUB-2020-GEN-006-DRAFT03. The main plaint is marked ongoing.
  • A separate interim-order application, SC/COM/WRT/000167/2026, is described as declined and not served on AFRINIC; the list also marks that entry ongoing.
  • A third entry records a 7 April appeal against an order in the interim matter and marks the appeal ongoing. The public list gives no appeal number or grounds.
  • The fixed 17-source packet includes no plaint, defence, requested relief, reasoned interim order, appeal grounds, hearing record or judgment on the merits.
  • The litigation matters because the ratified text makes AFRINIC’s written approval a gate to recognised transfers and bars AFRINIC-issued pool resources from leaving the region. Yet the public court record does not establish whether the authority behind that gate is lawful or unlawful.

Three docket rows, one unresolved authority question

The most important word on AFRINIC’s public Case List is not “declined.” It is “separately.”

Row 88 identifies Skyconnect, formerly Skyvision Guinee SA, as plaintiff in SC/COM/PWS/000132/2026. AFRINIC and another party are listed as defendants. The description says the plaint challenges the Board’s ratification of the inter-RIR transfer policy. It was filed on 9 March 2026 and is marked ongoing.

Row 90 describes a different matter: SC/COM/WRT/000167/2026, an application for an interim order. The list says the application was declined and not served on AFRINIC. It also displays “Ongoing” in the status column.

Row 91 records a third procedural event, an appeal filed on 7 April against an order in the WRT matter. It too is marked ongoing. No appeal cause number, grounds or outcome appear in the fixed packet.

Those entries cannot safely be compressed into the sentence “Skyconnect’s case was rejected.” The main plaint has its own number and remains open on AFRINIC’s list. Nor can the entries be turned into the opposite claim that Skyconnect has established the Board lacked authority. The record supplied here contains no merits judgment either way.

The news is narrower and more consequential: a challenge directed at the ratification remains alive, while the public procedural record is too thin to show the arguments, the relief sought or the court’s reasoning.

What the challenged ratification controls

On 4 February, AFRINIC announced that its Board had ratified AFPUB-2020-GEN-006-DRAFT03 after years of governance interruption. The policy is not merely a statement of aspiration. It divides number resources into categories and determines which resources may move between regions.

Legacy resources and resources that were transferred into the AFRINIC service region can, subject to the policy, be transferred out. Resources issued from AFRINIC’s own pool cannot. Every permitted transfer requires AFRINIC’s express written approval. The text gives AFRINIC a decision-making role and says it does not recognise transfers outside approved policies.

That is a concrete operating surface. A registry decision can affect exit, the ability to complete a transaction, the recognition of the registration record and the commercial planning around an address holding. A resource holder, buyer, lender, investor, customer or dependent network can bear the downside of delay or refusal even when the people making or defending the rule do not bear the same transaction-specific exposure.

The proposal page estimates 12 months for implementation and includes reciprocity updates dated April 2026. The fixed packet does not contain a single completion notice or a production transaction report. It would therefore be inaccurate to call the policy either fully implemented or unimplemented. Its status has to be split into at least four questions: ratification, implementation work, live transaction capability and judicial status.

AFRINIC’s institutional certainty is not a judicial finding

AFRINIC’s 18 February communiqué presents a confident position. It says the Board was properly constituted, the Policy Development Process was legitimate, the policy did not confiscate resources and allegations of unlawful targeting were unsupported by the policy or AFRINIC’s mandate. It also describes the process as bottom-up and consensus-based.

Those statements are material because they reveal how the institution justifies the gate it has claimed. They are not findings of the Mauritius court in SC/COM/PWS/000132/2026.

AFRINIC’s bylaws say policy proposals are discussed through the PDP at Public Policy Meetings and ratified by the Board. Separate provisions cover urgent policies adopted by the Board and later endorsement. The fixed packet does not say D3 was an urgent-policy measure. A 2021 mailing-list summary says co-chairs found rough consensus and moved the proposal into Last Call from 8 December 2021 to 5 January 2022.

That chronology shows steps recorded by AFRINIC. It does not answer the contested question of whether the body that converted those steps into a ratified rule possessed the authority asserted for it in February 2026. A title, a process label and a claim of consensus are evidence of what the institution says and did; none is self-proving authority.

The interim refusal has a hard evidentiary limit

Interim applications can matter greatly. They may determine what happens while a main dispute is pending. But the meaning of a refusal depends on the request, the legal test, the evidence, service and the court’s reasons.

None of those materials appears in the fixed packet. The case list says “Declined and not served on AFRINIC.” It does not reproduce the application, identify the exact interim relief, explain why it was declined or show whether the decision was procedural, jurisdictional, evidential or otherwise. The continuing “Ongoing” label is itself unexplained.

The 7 April appeal makes overstatement even less defensible. AFRINIC’s list says the appeal challenges an order in the WRT matter and remains open. It supplies no appeal number, grounds, directions or result. An appeal’s existence does not show that the earlier order was wrong; it shows only that the procedural branch is not fully closed on the public list.

The correct conclusion is therefore bounded. The interim request was declined and not served, according to AFRINIC. That does not resolve the separately numbered main plaint and does not establish that the ratification is valid, invalid, operative, suspended or court-approved.

A 2022 appeal did not decide these merits either

The public record contains another tempting shortcut. In 2022, AFRINIC’s Appeal Committee considered an appeal related to an earlier D2 version of the transfer proposal. Its report found the appeal inadmissible, expressly said there was no need to delve into the merits and set the appeal aside.

That disposition matters as institutional history. It shows that a challenge existed within the PDP appeal system and ended at a procedural threshold. It does not validate the substance of D2 or D3, the February 2026 ratification or the legal authority of the current Board.

This distinction is central to accountable governance. A process that ends without merits review cannot later be cited as if it supplied the missing merits review. Procedural closure and substantive validation are different public facts.

The power dispute cannot be outsourced to labels

NRS describes D3 as a regional lock-in, disputes that the current Board was lawfully seated and argues that a Receiver’s role is preservative rather than legislative. LARUS warns that variation in RIR transfer rules and governance disputes can reach operational planning. A LARUS-hosted legal opinion argues more broadly that actual authority, accountability and legal structure matter more than the appearance of community governance.

These sources identify the right power questions: who may create the approval gate, who bears the downside, what liability follows an incorrect decision and what exit remains available to the governed party. They are not court judgments in Skyconnect’s cases. The fixed packet also contains no evidence that Skyconnect acts for, is controlled by or coordinates with Cloud Innovation, NRS, LARUS or another named actor. Similar policy interests do not prove agency.

The same discipline applies to AFRINIC’s titles. Referring to a Board or Receiver records the roles claimed in the documents. It does not settle the legal dispute over their authority. AFRINIC asserts proper constitution; NRS disputes it; the main plaint challenges ratification; and this packet supplies no judgment resolving the conflict.

Who carries the uncertainty while the case remains open?

The doctrine running through the Heng Lu notes is practical: representation must be demonstrated, power should remain attached to responsibility, reduced exit increases dependence, and agents may impose risks they do not personally absorb.

Applied here, the chain begins with the 2021 consensus announcement, passes through a 2022 procedural appeal, reaches the Board’s 4 February ratification and then becomes an AFRINIC approval gate over recognised transfers. The court challenge is one possible check on that chain. Yet the public judicial layer currently exposes little more than names, numbers and status labels.

Resource holders and transaction counterparties cannot use those labels to price timing, understand available relief or predict whether a registry instruction will survive review. The fixed packet identifies no transaction-specific compensation, equivalent liability or neutral continuity mechanism borne by those who ratify, approve, refuse or delay a transfer.

That asymmetry is the current governance fact. Institutional certainty can operate immediately; public scrutiny of the authority behind it remains dependent on a case file that has not been made legible in the frozen record.

A publishable record would separate four kinds of status

The missing clarity does not require AFRINIC or the court to litigate through press releases. It requires a disciplined public index, subject to court rules and legitimate privacy limits.

For the main plaint, the record should provide the pleading, defence, relief sought, issues list, hearing timetable and eventual reasons. For the interim branch, it should provide the application, service record, reasoned order and the status meaning. For the appeal, it should identify the cause number, grounds, directions and later disposition.

AFRINIC can separately publish the Board resolution, attendance, votes, recusals, ratification report and legal authority relied upon, together with any relevant Receiver consent or court direction. None of those items should be implied from the institutional word “ratified.”

Operational reporting should then distinguish a policy that is ratified from one whose implementation work is under way, one capable of processing live transactions and one whose authority has been judicially examined. Aggregate figures for transfer applications, categories, approvals, refusals, reasons, processing time, appeals and reversals could expose whether the gate works without revealing confidential transactions.

The bounded finding on 11 August is clear. AFRINIC’s own docket says the main challenge to the Board’s ratification is ongoing. It also says an interim application was declined and not served and that an appeal remains ongoing. Those facts neither validate nor invalidate D3. Until pleadings and reasoned decisions connect authority, policy effect and remedy, AFRINIC’s claims of proper constitution and legitimate consensus remain institutional positions operating ahead of a publicly testable merits record.

Readers seeking the broader liability analysis can consult BTW’s separate research listed below. That longform is further reading only; this is a native news briefing based on the frozen public record of the Skyconnect court and policy dispute.

Sources