Summary

  • The record obtained for this review documents AFRINIC's political reconstruction in unusual detail: a board dissolved in 2022, a chief executive contract that expired in November 2022, court-appointed receivership from 2023, a board election halted in June 2025, a completed election in September 2025, interim management, and a chief executive named to start on 1 January 2027.
  • The same record contains no designation of a Chief Technology Officer, or of an equivalent technical owner, anywhere in that window, and this review obtained no Mauritian court order, gazette notice, insolvency-practitioner notice, board resolution or annual report that would settle the question either way.

A reconstruction documented seat by seat

The chronology that survives in the record obtained for this review reads like a minute book of institutional repair. The Supreme Court of Mauritius dissolved the previous board in 2022. The chief executive's contract expired in November 2022 and, the record states, could not be renewed because there was no complete board to renew it. From 2023 the registry operated under a court-appointed receivership. In June 2025 the receiver attempted a board election and halted it over concerns about electoral integrity; in September 2025 a board election went through. Interim management was appointed and a budget and action plan were developed. The leadership table now records the Chief Executive Officer seat as vacant, with Mike Silber starting on 1 January 2027 (the record obtained for this review).

Read that list as governance documentation rather than as news, and the pattern is hard to miss. In the account obtained here, every political seat carries a paper trail: a court, a date, a decision, a successor. The legitimacy layer is not merely repaired. It is legible.

The seat the record skips

The same record lists the staff departments inside the registry, among them Infrastructure and Security and the CEO's Office. It does not identify a Chief Technology Officer as a distinct office at any point since 2022. That is a statement about the material this review obtained, not a statement that AFRINIC has no such officer. Whether an acting or interim CTO was appointed after 2022 is not established here. The identity of any officeholder and the instrument of appointment are not established. Whether Infrastructure and Security formally absorbed the CTO function is not established.

This review obtained no court order, gazette notice, insolvency-practitioner notice, board resolution or annual report from Mauritius, so the legal character of the receivership rests on a provider-reported passage rather than on an instrument read directly.

Hold both halves of that paragraph together, because together they are the article. The absence is not proof of a vacancy. It is evidence of an accountability line this review could not trace from outside the building.

Two continuities, not one

The chronology quietly separates two things that managerial language likes to merge. Corporate continuity is the board, the chief executive, the election calendar. Operational continuity is whatever kept the registry answering queries while those seats were empty. The record reports that, without a CEO or board, staff continued to conduct basic operations. Read that sentence for exactly what it says: some operational capability persisted through the gap. It does not identify a formal technical authority, prove a valid delegation, or establish uninterrupted performance, quality or security for any published service.

No telemetry, service-status archive, incident record or assurance report was obtained for this review.

That distinction blocks a comfortable inference. Restoring a board, completing an election or naming a chief executive for a future date cannot, by itself, explain who authorised technical changes during the gap or who answers for them now. The corporate seat and the technical function ran on different clocks, and only one of those clocks is documented.

Why the technical seat is not a courtesy title

Set AFRINIC aside for a moment. In the ordinary practice of a regional internet registry, the technology office is the custodian of the things that make a number mean something: provisioning systems for IPv4, IPv6 and autonomous system numbers; the WHOIS and RDAP publication service that tells the world who holds a block; reverse DNS delegation; the RPKI repository and the route-origin authorisations built on it; the DNSSEC key material for the zones the registry signs; and the operational continuity of each of those.

That is my description of the function, not a quotation from an AFRINIC charter — no AFRINIC charter text was obtained for this review. The point rests on general registry practice, not on a clause.

Now put the registry back in. Members, regulators, courts and counterpart registries do not interact with a function. They interact with a person or an office that can be named, questioned, escalated to and, when it matters, held to account. A role object with a name and a date on it is the difference between a decision you can challenge and a decision that simply happened.

Accountability follows the function, not the job title

A fair objection deserves a straight answer: a registry can be entirely accountable with nobody carrying the title Chief Technology Officer, provided equivalent responsibilities are formally allocated to a named person or unit, with an instrument, effective dates, decision rights and escalation lines an outsider can discover. A title alone would prove nothing either. The question is not whether three particular words appear on a website. It is whether the function has an owner on the record.

That reframing changes what counts as evidence. If Infrastructure and Security owns registry provisioning and routing security under an identified accountable head, the missing title is a labelling fact and hardly a scandal. If those responsibilities sit in an undocumented arrangement among staff, the absent title is a symptom of something larger: decision authority that cannot be traced, cannot be delegated in writing and cannot be audited after the fact. The record obtained here does not settle which of those is true. A functional responsibility map — function, owner, instrument, effective date — would settle it in a page.

Where the evidence stops, dated

The retrieval boundary belongs in the article because it bounds the finding. On 4 November 2026 this review sought AFRINIC's own published record and the encyclopaedia entry. The registry's site itself carried no readable passage on the technical office. No court order, gazette notice, insolvency-practitioner notice, board resolution or annual report was obtained.

So the honest formulation is narrow, and it is the one this article uses throughout: as of 4 November 2026, the record obtained for this review contains no designation of a technical owner. Whether that reflects a gap in what the institution publishes, a limit of indexing or access, or a difference of terminology is not established here. The question a member, a counterparty or a court can act on does not depend on which: name the owner, and name the instrument.

The question a member should be able to ask

Strip away the drama of receivership and the ordinary question is almost banal: who is accountable for the registry's technical decisions this quarter? Not which vendor, not which server, not which committee minute stays confidential — who, in a named office, with a date of appointment and a defined scope of authority, signs off on a change to routing security or to a numbering record?

A registry that can answer that in public is not diminished by the answer. It is strengthened, because the answer converts trust from a mood into a citation. The test here is documentary rather than rhetorical. Publish the designation, or the register's technical authority remains an inference drawn from the fact that the lights stayed on.