Summary

  • AFRINIC's Seat 4 for Central Africa appears twice: an announcement dated 12 September 2025, and a roster page that carries no date at all.
  • The AS37414 registry object names two other men as administrative and technical contacts, while the network holds 3,072 IPv4 addresses and announces 2,048 of them with no signed route origin.

Two documents in AFRINIC's public record put Kayemba Laurent Ntumba in the Central Africa seat. One is dated: a post to the registry's Announce list on 12 September 2025 records "Board - Seat 4 (Central Africa), Mr Kayemba Laurent Ntumba" among the 2025 election results (AFRINIC Announce, 12 September 2025). The other is not dated at all — the roster lists Seat 4 as Laurent Kayemba Ntumba, Congo DRC, Central Africa, with "3 years" in the term column (AFRINIC Board). Neither page prints an appointment instrument, a start date or a removal route. The announcement records an election result; the roster records who sits where. Between them they establish an office and stop.

The network is a different kind of document, and it is the one that matters to anyone asking what an African registry director actually operates.

AFRINIC's RDAP object for AS37414 is an active autnum named ORG-MS1-AFRINIC whose WHOIS port is whois.afrinic.net. Its registration event is recorded at 2012-01-26T11:28:00Z and its last change at 2016-11-17T10:25:00Z; the registrant is Microcom Sprl, at an address in Gombe, Kinshasa (AFRINIC RDAP, AS37414). Its contacts are Ntale Michel (NM16-AFRINIC), administrative, and LEON Ntale (LN1-AFRINIC), technical (same object). Kayemba Laurent Ntumba is not among the entities of that object as it stood on 18 November 2026.

That is a small fact with a long shadow. A contact handle is not a job title — the people who answer abuse mail and push route-object updates are rarely the people who sign the annual report — but it is the only place where the registry itself says who stands behind a number block. On this object, the answer is two Ntales, and the object has not been touched since 2016.

The allocation record and the routing record are two different ledgers

A WHOIS-derived organisation listing for ORG-MS1-AFRINIC counts one AS number and four registered networks: 41.78.196.0/22 (MICROCOM-HUB), 41.223.104.0/22 (microcom-cd) and 196.61.72.0/22 (MICROCOOM-FIBER-SATLINK), each ALLOCATED PA, plus 2c0f:6580::/32 (Microcom-Ipv6-Net), ALLOCATED-BY-RIR (IP-FD organisation record). Three /22s is 3,072 IPv4 addresses. The registry spells one of the netnames with two O's, which is the kind of detail that tells you a human typed it.

Observed routing is the other ledger. AS37414 announces 2,048 IPv4 addresses across eight /24 prefixes — 41.223.104.0/24 through 41.223.107.0/24 and 196.61.72.0/24 through 196.61.75.0/24 — and no IPv6 prefix whatsoever, with 0.00% of its routes RPKI-valid (InternetData; IPinfo). A BGP monitor drawing on RIPE RIS and RouteViews snapshots, its latest collection shown as 15 November 2026, counts the same eight IPv4 routes and zero IPv6 routes, eight prefixes with no ROA and none invalid, an AFRINIC route object present for all eight announced prefixes, and six registered route objects for AS37414 that are not announced at all (BGP Report).

Subtract one ledger from the other and 1,024 addresses stay registered to Microcom and unannounced by its own AS — exactly one of the three /22s. That subtraction is mine, performed on the two records as they stood on 18 November 2026, and a network engineer will supply a dozen innocent readings of it: space staged for a build-out, space assigned to customers who announce it under their own autonomous system, space held for planning rather than traffic.

The same file suggests which /22 it is. The page for 41.78.196.0/24 states that the block is "Covered by 41.78.196.0/24 from AS22351 INTELSAT GLOBAL SERVICE CORPORATION", with no ROA (IP-FD, 41.78.196.0/24). Read plainly: the block is registered to a Kinshasa operator and the covering route in this extract comes from a satellite operator. Allocation and origin are separate facts, and here they point at different parties.

A filing that argues with itself, at an address that no longer answers

The only AFRINIC-hosted document connecting the man to the company is his own candidate page for the seat (Seat 4 candidate profile). It lists organisation MICROCOM and "Poste: Directeur Délégué", then calls him directeur général of Microcom RDC and says he has headed the company since 2000. It also claims the ISPA-RDC presidency, a vice-presidency of the FEC telecom committee, a 2020 seat on AFRINIC's Governance Committee and a 2022 seat on its Policy Development Appeal Committee (same page).

It contradicts itself twice inside one document. The field says Directeur Délégué; the prose says directeur général. The motivation claims "plus de 40 ans" of experience; the experience section claims "plus de 30 ans". And the address no longer answers: a direct request returned HTTP 404 on 18 November 2026, so the text above is what the page said when a search provider extracted it, not something a reader can open this afternoon.

Two forms of evidence, unequal weight

The office has a date. The operating role has a self-description, a dead link and two internal contradictions. Between them sits a registry object naming two other men and a routing table a third short of the allocation record.

None of that is a finding of wrongdoing, and the dullest explanation is also the likeliest: a founder who delegates contact handling, a /22 waiting for a customer, a French-language filing written in a hurry. The point is narrower and harder to shrug off. Anyone asking what a Central African director of AFRINIC actually runs has exactly one place to look, and that place does not print his name. The seat is checkable. The business behind it is checkable only by the man's own account of himself — and by nine figures anyone can fetch.

Here is the whole case, left in the reader's hands rather than mine: pull the RDAP object and read its two contact entities; open the 12 September 2025 announcement and the undated roster beside it; ask a routing monitor for AS37414's current prefixes and RPKI state; try the candidate URL yourself; and put 3,072 next to 2,048. Five checks, no trust required.