Summary

  • AFRINIC has operated under a court-appointed official receiver since 2025, with the Number Resource Organization publicly acknowledging the appointment and ICANN documenting the escalation that preceded it in March 2025 correspondence and an update on the receiver appointment (NRO; ICANN update, 9 March 2025; Crain-to-Dabee letter, 7 March 2025).
  • The registry's technical services continue to publish observable evidence: RPKI validator data, DNSSEC statistics, resource certification documentation and audited financial statements for fiscal 2025 (RPKI validator; DNSSEC stats; resource certification; FY2025 financials).
  • ICANN's recognition framework — ICP-2 as baseline and the 2025 governance document for recognition, maintenance and derecognition of RIRs — is the external check on whether operational continuity translates into maintained recognition (ICP-2; 2025 recognition governance document).
  • AFRINIC's own communiqués describe continuity measures while legal proceedings continue, and the organisation has named a CEO designate, Mike Silber, as part of the transition (communiqué, 15 May 2026; member update; CEO designate announcement).
  • The unresolved question is evidential, not rhetorical: uptime and published statistics prove that machinery responds, but not that authorisation, detection, reversal and audit of high-impact technical changes remain bound to lawful authority. The Register reported ICANN's renewed intervention to defend AFRINIC on 27 May 2026, confirming that recognition risk is still live (The Register, 27 May 2026).

Prior BTW coverage of this subject established that allocation authority is split across contract, receiver custody and ICANN recognition, that revocation powers sit in the registration services agreement rather than the company constitution, and that operational continuity does not by itself prove governance repair (see the AFRINIC directory entry and prior dual-control transition coverage). What that coverage did not examine is the control layer beneath allocation: the routing-security and certification machinery that African networks touch every day.

That layer has a concrete test surface. AFRINIC's RPKI validator page and DNSSEC statistics are public and machine-readable; the consolidated policy manual and resource-certification pages describe the processes by which resource holders obtain certificates and publish route authorisations (validator; DNSSEC; policy manual; DNSSEC service). The durable-repair question is therefore checkable in a way governance rhetoric is not: do published RPKI validity and DNSSEC signing data remain consistent and attributable through the receivership period, and is there any public record of who authorised changes to those systems since the receiver took custody?

The honest answer from public sources is that the machinery appears to run and the accountability trail does not. Neither the receiver's mandate as publicly acknowledged by the NRO, nor ICANN's March 2025 correspondence, nor AFRINIC's own stability communications identifies who holds change-authorisation for the routing-security stack, how an unauthorised change would be detected, or what audit artefacts exist.

Under the 2025 recognition framework, sustained inability to demonstrate such controls is the kind of condition that a derecognition assessment would weigh; the document itself is the standard, and the public record does not yet show that AFRINIC has been measured against it in published form.

For operators, the bounded consequence is practical. Route Origin Authorisations and DNSSEC chains issued under receivership custody remain valid technical instruments; nothing in the public record indicates their integrity has been compromised. The risk is remedial, not operational: if recognition were contested or custody arrangements changed, the evidentiary basis for trusting that specific issuance chain would depend on audit artefacts that public sources do not currently exhibit.

Sources: https://www.theregister.com/networks/2026/05/27/icann-again-intervenes-to-defend-afrinic/5246790 · https://www.nro.net/nro-statement-on-appointment-of-an-official-receiver-for-afrinic/ · https://itp.cdn.icann.org/en/files/administration/governance-document-for-the-recognition-maintenance-and-derecognition-of-regional-internet-registries-08-04-2025-en.pdf · https://afrinic.net/afrinic-member-update-organisational-stability-and-ongoing-legal-challenges.html · https://afrinic.net/afrinic-communique-15052026.html · https://afrinic.net/appointment-of-mr-mike-silber-as-ceo-designate.html · https://afrinic.net/assets/pdf/financials/ar_25_afs.pdf · https://validator.afrinic.net/rpki/rcynic/index.html · https://stats.afrinic.net/dnssec/ · https://itp.cdn.icann.org/en/files/correspondence/crain-to-dabee-07mar25-en.pdf · https://www.icann.org/en/announcements/details/icann-update-on-afrinic-receiver-appointment-09-03-2025-en · https://www.icann.org/en/system/files/files/icp-2-28feb07-en.pdf · https://btw.media/en/afrinic-board-receiver-dual-control-transition · https://www.afrinic.net/ · https://afrinic.net/news.html · https://afrinic.net/resource-certification.html · https://afrinic.net/dnssec.html · https://afrinic.net/resources-2 · https://afrinic.net/consolidated-policy-manual.html · https://afrinic.net/news · https://www.icann.org/resources/pages/new-rirs-criteria-2012-02-25-en · https://lists.afrinic.net/pipermail/announce/2025/002501.html