Summary

  • AFRINIC's current public team and staff pages list no position titled Chief Technology Officer; technology operations appear under an Infrastructure & Security department led by a Head of IT & Security, and registry software functions under a separate Registry Products unit (AFRINIC staff roster, team page).
  • The AFRINIC WHOIS database nonetheless resolves two legacy objects: a maintainer named CTO-MNT, which maintains itself, and a person object "CTO AFRINIC" (nic-hdl CA15-AFRINIC) at an Ebène, Mauritius address with a generic CTO mailbox at the registry's own domain (WHOIS query result).
  • As early as December 2020, a community mailing-list participant quoted that exact person record and remarked, "I doubt that there is a person with that name" — evidence that the object has functioned as a role placeholder for years before the crisis (community-discuss archive, December 2020).
  • The Court of Civil Appeal judgment 2024 SCJ 473 records that AFRINIC's CEO ceased office on 4 November 2022 and that, at the relevant time, the company had "at best an inquorate board of directors (four only)" (2024 SCJ 473).
  • AFRINIC's own Annual Report 2025 states that from June 2022 to September 2025, in the absence of a Board and a CEO, management was overseen by the leadership team of Heads of Department, subject to successive court-appointed receivers — not by any CTO (Annual Report 2025).
  • Technology oversight was later assigned within an Interim Management Committee: Mukom Tamon was mandated to oversee Technology, Infrastructure and Strategy functions, alongside Nirmal Manic (Finance and Administration) and Arthur N'Guessan (Stakeholder Development & Communications), reporting jointly to the Board and the Receiver (Annual Report 2025, AFRINIC Board Updates announcement).

A role that exists only in a database

Begin with the objects themselves. Query the AFRINIC WHOIS service for CTO-MNT and the service returns "Found 2 objects." The first is a maintainer object: mntner: CTO-MNT, described as "MNTNER for CTO", with admin contact CA15-AFRINIC and two PGP-key authentications, maintained by — itself. The second is a person object: person: CTO AFRINIC, located at the 11th Floor, Standard Chartered Tower, Cybercity, Ebène, Mauritius, with the registry's public phone number and the handle CA15-AFRINIC. A third-party mirror of the AS37708 (AFRINIC-MAIN) routing records shows this identity has been referenced in change lines dating back to at least 2014, including a change line dated 3 December 2014 attributing updates to the registry's CTO mailbox, and further updates in 2017 — a longstanding artifact, not a fresh creation (WHOIS query result, third-party AS37708 mirror).

Nothing on the registry's current staff pages corresponds to it. The public roster enumerates nine departments — from the CEO's Office through Finance and Accounting, Capacity Building, Communications, Infrastructure & Security, Member Services, Registry Products, Stakeholder Development and Value Added Services — and names the people in each. In Infrastructure & Security, the head is Michel Odou, titled Head of IT & Security, supported by systems engineers, a DevOps lead and a database manager. Registry Products is led by Keessun Fokeerah. Nowhere in that structure does a Chief Technology Officer appear, on either the staff page or its mirror (staff roster, team page).

The title did once exist in some form. Alain Aina, one of AFRINIC's founders, served as acting CTO from June to December 2008 and later as acting CEO from March to August 2011, according to his professional profiles — which today list him as CTO of WACREN, a different organisation (AfPIF speaker profile, WACREN 2022 speaker profile). The historical record, in other words, supports the idea that AFRINIC has had a technology-executive function — but only as an acting post, seventeen years ago, and never as a permanently staffed title in the current published structure.

A December 2020 message to the AFRINIC community mailing list shows that outside observers had already reached the same conclusion. Quoting the person record in full — address, phone number, handle — the writer added: "I doubt that there is a person with that name." That single sentence, six years old and written by a community participant rather than the registry, is the earliest retrieved independent observation that the CTO object was a role artifact rather than an incumbent (community-discuss archive, December 2020).

The vacuum the judgment described

What does a registry do about technology leadership when it has no CTO and, soon after, no CEO and no functioning board? The 2024 SCJ 473 judgment of the Supreme Court of Mauritius supplies the record. It finds that Mr Kayihura ceased to be AfriNIC's Chief Executive Officer on 4 November 2022, "with the result that AfriNIC found itself without a CEO" when Cloud Innovation lodged its application in March 2023. It quotes Article 15.1 of AFRINIC's Bylaws: the business and affairs of the company shall be managed "under the direction and supervision of the Board" — and notes that the board was, at best, inquorate, with four directors where the Bylaws require not fewer than five for a quorum. The judgment says nothing about a CTO, because by then there was nothing to say (2024 SCJ 473).

The receivership order of 12 September 2023 appointed an official receiver whose mandate, as the Number Resource Organization described it in its public statement, was to "maintain the status quo of AFRINIC's assets and preserve the value of the business" — and to see the election process, the formation of a board and the appointment of a CEO through (NRO statement).

AFRINIC's own Annual Report 2025 fills in the management shape of those years in one paragraph: "In the absence of a Board and a Chief Executive Officer for the period June 2022 to September 2025, the management of AFRINIC was overseen by its leadership team, comprising its Heads of Department, subject to such oversight by the successive court-appointed receivers." Read against the staff roster, this is the operative answer to who held technology control: not a CTO, but a head of IT & Security operating inside a heads-of-department collective, supervised by receivers whose mandates never once mention a technology executive role (Annual Report 2025, NRO statement).

The IMC and the distributed CTO

In 2025, with a newly elected board in office from 15 September 2025, the structure changed shape but not principle. The board, with the Receiver's consent, established a three-person Interim Management Committee drawn from senior Heads of Department: Nirmal Manic for Finance and Administration, Mukom Tamon for Technology, Infrastructure and Strategy, and Arthur N'Guessan for Stakeholder Development & Communications. The committee reports jointly to the Board and the Receiver and serves until a substantive CEO is appointed (Annual Report 2025, AFRINIC Board Updates announcement). BTW has previously examined the authority questions raised by this arrangement — that its decisions are framed "with the consent of the Receiver", including the 24 August 2026 announcement of CEO designate Mike Silber, who takes office on 1 January 2027 (AFRINIC IMC authority-gap analysis, CEO designate announcement).

What the IMC adds to the CTO question is the decomposition of the role. Technology, infrastructure and strategy — the portfolio a CTO would plausibly own — sits with one committee member; day-to-day infrastructure sits with the Head of IT & Security; registry software sits with Registry Products; and IT governance oversight, the annual report notes, is attributed to the Audit Committee. The CTO function was not abolished; it was disaggregated, and each piece is accountable to a different principal.

Did the technology work anyway

Accountability reporting matters most when the titled role is missing. The strongest available evidence on output comes from the registry's own reporting: the Infrastructure and Security Department stated that critical services were typically maintained above 99.7% availability in 2025, alongside DNS/DNSSEC, RPKI, WHOIS replication and MyAFRINIC v2 work (Annual Report 2025). Independent context cuts in both directions. ICANN's Chief Technology Officer John Crain wrote to the Receiver on 7 March 2025 raising concerns that limitations under the receivership had restricted AFRINIC's ability to perform numbering-resource assignments — an external technology executive documenting performance concerns at precisely the moment AFRINIC had none of its own (ICANN Crain to Dabee letter, 7 March 2025). By February 2026, The Register reported AFRINIC as back on track to deliver a budget and strategy (The Register, 10 February 2026). BTW's earlier examination of AFRINIC's technical controls under receivership provides the adjacent baseline against which this article's novelty should be measured: prior coverage examined the controls; this article examines who was accountable for them (BTW: technical controls under receivership).

The evidentiary boundary should be stated plainly. The staff roster is a curated listing; an internally titled technology executive under a different label cannot be ruled out from it alone. The PDFs cited here were inspected through rendered excerpts rather than full independent downloads. And the WHOIS snapshot reflects a fetched state of a live database that could change. Even tertiary reference works such as Wikipedia list the CEO vacancy but no Chief Technology Officer (Wikipedia — AFRINIC). What the record establishes is narrower and firmer: at no point in the retrieved public record — staff pages, judgment, annual report, receiver mandates, IMC instruments — does a Chief Technology Officer appear as a filled AFRINIC role, while the WHOIS object named for that role continues to resolve.

What the phantom role proves

A registry that allocates internet number resources for an entire continent ran for roughly three years with its technology accountability distributed across a head of department, an interim committee mandate and receiver supervision — and its global database still answers "who is the CTO of AFRINIC" with an object naming a role nobody holds. Both facts are true, and together they describe an institution that kept its operations running while its accountability surface thinned.

The lesson is not that AFRINIC uniquely failed; it is that continuity artifacts — the database entries, the role objects, the maintained aliases — outlive the governance that created them, and stakeholders who rely on either the roster or the WHOIS alone will be misled. The question for the incoming CEO administration taking office on 1 January 2027 is whether technology accountability is reconsolidated under a titled, named executive, or remains a committee assignment one consent letter away from its supervisor. The record so far answers neither way.