Summary

  • On 11 November 2026, a week before AFRINIC-38, AFRINIC published a new code of conduct and said it would test “an automated moderation mechanism” on its public mailing lists: one more rule in AFRINIC’s governance written without the members.
  • Enforcement on the members’ list lies with “the CEO or staff designated by the CEO”, though the chief executive’s post has been vacant since 4 November 2022; suspect posts may be suppressed “without warning processes”.
  • Participants on AFRINIC’s policy list objected that the community was never asked and asked for a redline, the mechanism’s rules and an appeal. By 20 November 2026 AFRINIC had published none of them.

What did AFRINIC change on 11 November 2026?

On 11 November 2026, a week before its AFRINIC-38 Public Policy Meeting in Cape Town, AFRINIC published a new code of conduct and said it would test “an automated moderation mechanism” on its public mailing lists; participants on its own policy list objected that the community was never asked.

AFRINIC announced the “AFRINIC Community Code of Conduct”, marked “Last updated: 11 November 2026”, on rpd, its public policy list, at 17:44 UTC that day: “As part of implementing the updated Code, AFRINIC will be testing an automated moderation mechanism on its public mailing lists. Further details will be shared as implementation progresses.”

The code applies “to anyone interacting, directly or indirectly, with AFRINIC”, including the registered administrative contacts who act for its members. Its new demands include “Participate authentically and as one person in good faith”, “Avoid all machine-driven automatic participation, including use of AI agent bots, or other systems” and “Act in the best interests of the AFRINIC community at all times.” Each is a judgement about the speaker; the question is who makes it.

Who enforces AFRINIC’s code of conduct?

On rpd, the elected co-chairs of the Policy Development Working Group; on the members’ and community lists, the chief executive or staff the chief executive designates, though AFRINIC has had no chief executive since 4 November 2022.

The co-chairs may ask the Secretariat for “technical information reasonably associated with the relevant messages and subscriptions (such as message headers, originating systems, and subscription records)”. For the other lists, enforcement “lies with the CEO or staff designated by the CEO. Automation of the enforcement of the code of conduct may be implemented.”

By AFRINIC’s communiqué of 24 August 2026, a chief executive designate is to take office on 1 January 2027. Until then, enforcement on the members’ list belongs to an office that has stood empty since 2022.

What happens to a member who breaches AFRINIC’s code of conduct?

A four-step ladder that can end in permanent removal, and, for a post merely suspected of automated inauthentic behaviour, suppression at once with no steps at all.

First comes a warning. After a second breach, “the subscriber’s email will be subject to moderation” for up to three months; after a third, removal from the list for three months; after a fourth, “the subscriber may be removed from the list with no possibility of return.”

Beside the ladder sits a shortcut: “In case of suspected automated inauthentic behavior, such as spam, spoofing, coordinated AI Agents or other bots, immediate manual or automated post suppression or moderation, may be enforced without warning processes as described above.”

“Suspected” is decided by whoever runs the mechanism, and its rules have not been published. By 20 November 2026 AFRINIC had published no appeal either.

Did AFRINIC’s community agree to the changes?

No: participants on AFRINIC’s own policy list say the community was never asked.

On 12 November 2026 a long-standing proposal author asked when the community had discussed the changes, for a comparison with the previous version and for the rationale for each: “I disagree in not discussing them in an open and transparent way which is the basis of our community.”

On 16 November 2026 another participant asked AFRINIC to publish, before any test, a redline against the previous version; the mechanism’s operating rules (“who operates it, who is accountable for decisions, what objective conditions trigger a hold, suppression or removal”); and confirmation that enforcement on rpd “remains with the elected PDWG Co-Chairs”. In the participant’s words: “AFRINIC must not test or enforce a mechanism capable of restricting RPD participation without published, reviewable rules, an accountable human decision-maker, notice, prompt review, an effective appeal and rollback.”

By 20 November 2026 AFRINIC had published none of these on the list.

What else happened at AFRINIC-38?

Participants reported two more restrictions, on what elected co-chairs may say and on those presenting, and AFRINIC has published no written outcome of the meeting.

On 18 November 2026, the day of the meeting, a participant wrote that AFRINIC’s reading (“organization, Board, legal counsel”) is that co-chairs, once elected, may no longer give personal opinions. Section 3.3 of the Policy Development Process says only: “The Policy Development Working Group has two Chairs to perform its administrative functions.” As the participant pointed out, the word “exclusively” is not in it.

A post of 19 November 2026 and others on the list report that AFRINIC asked people presenting at the meeting to upload identity documents; one participant wrote that they did not present that day because AFRINIC asked presenters to upload them to its servers. The author of the region’s original policy development process wrote that it contained no requirement for “an author of a policy proposal to submit identity document”. A draft update to the process, AFPUB-2026-GEN-005-DRAFT01, was under discussion.

Why does AFRINIC’s code of conduct matter to members?

Because the policy list is where AFRINIC’s members make the rules the registry applies to them, and rules on who may speak there, written without them and enforced by people they did not choose, decide whose voice counts before any proposal is debated.

Cloud Innovation’s page on AFRINIC’s governance calls AFRINIC “a members’ company run without its members”. Yet AFRINIC belongs to its members, as BTW’s report on who owns AFRINIC shows.

Lu Heng, the internet entrepreneur behind Cloud Innovation, wrote about governance that turns coordination into permission in Note 25 of 29 December 2025, on the draft revision of ICP-2, under which the regional registries are recognised: “It converts coordination into permission. And permission into power.” And: “Consent is the system.”

A registry that decides what its members may say where they make its rules has turned coordination into permission. On who should govern AFRINIC and write its rules, the answer is its members. They can ask for what participants already have: the redline, the mechanism’s rules, an accountable human decision-maker, notice and an appeal.

The wider record is on Cloud Innovation’s page on AFRINIC’s governance.

Sources