AFRINIC

The entity sits on the left and its connections fan out by role on the right; the graph shows each group’s most confident connections, and the full list below carries every relationship.

Full list

• Botswana’s IPv6 Plan Sets a 2026 Target. What Counts Toward 100%?

  BOCRA’s roadmap assigns IPv6 targets through 2026, while Botswana’s accelerator records engineers trained and projects chartered. The missing public question is not whether work began; it is how a reader can distinguish readiness from measured deployment without exposing confidential operator submissions.

  Primary articlePublished 2026-10-07
• AFRINIC ratifies three policies, but each now faces a different implementation clock

  The 25 September approvals cover recovered IPv4 space, utilisation exceptions and new AS-SET names. AFRINIC’s own documents show why “ratified” is not the same as “in force.”

  Primary articlePublished 2026-10-07
• AFRINIC Logs Four Fliber Blocks to Level 7; BGP’s Origin Shifts Later

  AFRINIC records a 24 September transfer event involving four IPv4 prefixes. RIPE NCC’s route collectors later observed a different origin for those prefixes, but the two records do not establish that the transfer caused the routing change.

  Primary articlePublished 2026-09-28
• AFRINIC’s New IPv6 Tally Is 120 Below Its 2023 Figure. The Bases Differ.

  AFRINIC’s September invitation reports 257 deployment milestones. A 2023 blog reported 377 across Deployathons and DO Helpdesk. The numerical gap is real; a like-for-like decline is not established.

  Primary articlePublished 2026-09-27
• AFRINIC Asked Quiet French Readers to Speak. The Survey Opens in English

  AFRINIC wants its next policy webinars to answer the barriers that stop people from posting to RPD or taking a PPM microphone. The 23 September invitation is unusually direct about seeking those quiet voices. Yet the advertised French route returned the English landing page, while both language versions told readers to respond by `[date]`. Before silence becomes evidence about reluctance, the intake needs to show which door actually opened and how long it remained open.

  Primary articlePublished 2026-09-24
• AFRINIC Can Fund the Trip. It Cannot Replace the Policy Record

  An engineer from Malawi arrived at AFRINIC-37 on a ticket enabled by a new member-support programme, learned the room and spoke from her own network experience. That is a real opening. It is also a limited kind of evidence. The more exact test of AFRINIC's experiment is whether a funded presence can be distinguished from the wider, open policy process—and whether the useful part of that presence remains inspectable after the meeting ends.

  Primary articlePublished 2026-09-24
• AFRINIC’s IPv6 Draft Changed What 95% Means

  Draft 3 keeps the comfort of a familiar percentage while changing the thing being counted. A future result can be comparable only if it travels with the policy version, denominator and measurement method that produced it.

  Primary articlePublished 2026-09-24
• AFRINIC's Resource Certificate Can Be Valid Without Naming the Member

  A resource certificate with a generated, apparently meaningless Common Name can be doing its job perfectly. AFRINIC’s own practice statement shows why: the public certificate proves a bounded resource authorization, while a different chain connects the request key to a representative, a member record and a set of number resources. The missing operational object is not a more revealing certificate. It is a privacy-safe receipt for the handoffs.

  Primary articlePublished 2026-09-19
• AFRINIC’s Merge Question Could Bind Two Section 3 Decisions Together

  The co-chairs asked whether a meeting-calendar rule and a broad rewrite of the policy working group should become one draft. Before that happens, the community needs to know what would be combined—and what it would still be allowed to decide separately.

  Primary articlePublished 2026-09-19
• AFRINIC’s Holiday Notice Appeared One Day Before Closure. That Is Not a 72-Hour Verdict

  AFRINIC’s public record shows a 14 September notice for a 15 September office closure. Its service commitment speaks of seventy-two hours, but on a different channel: announcement mail. The right audit separates the website, the mail record, human response time and always-on systems before it judges any of them.

  Primary articlePublished 2026-09-15
• AFRINIC’s Uganda Anycast Node Is Two Services, Not One

  Two adjacent rows in the Uganda Internet eXchange Point directory look like one institutional arrival. They are not one service. One row belongs to AFRINIC’s NS2 secondary-DNS platform under AS37177; the other belongs to its DotARPA reverse-DNS platform under AS37181. Each has its own IPv4 prefix, IPv6 prefix, peering address and operational purpose. The split is useful because it shows exactly where public evidence stops: connection to an exchange is visible, but local query landing, application health and performance still require separate receipts.

  Primary articlePublished 2026-09-14
• AFRINIC's RRDP Lists 32 Deltas. That Is Not a Recovery Window.

  AFRINIC's live RPKI notification showed a neat chain of 32 incremental updates. The number is useful, but it does not tell a network operator how long a validator may be offline before recovery changes from a small replay to a full snapshot.

  Primary articlePublished 2026-09-14
• AFRINIC’s Hash Tool Is Also a Password-Receiving Surface

  AFRINIC’s public generator returns a BCRYPT value, but its current form first asks a browser to send a field called `plaintextpassword`; the missing operational object is a receipt for who can see that source value before the hash exists.

  Primary articlePublished 2026-09-14
• AFRINIC’s Gold Blueprint Leaves 10% Unassigned

  The public certi::6 Gold outline lists six domain weights totalling 90%; Silver’s nine total 100%. That is a preparation-document gap, not evidence of missing exam questions.

  Primary articlePublished 2026-09-14
• AFRINIC’s Duplicate nserver Row Is Gone. Redundancy Is Not a Row Count

  A February discussion exposed two identical nameserver entries that produced only one DNS referral. The named example is now corrected. What remains useful is the distinction between an avoidable input mistake, an answering server and infrastructure that can survive a failure.

  Primary articlePublished 2026-09-14
• AFRINIC’s ccTLD Test Cannot Set a Country’s IPv6 Ceiling

  The deployment monitor makes a useful check of registry nameservers, then draws a conclusion about every site below them. A recursive resolver can cross a transport boundary that the wording leaves out.

  Primary articlePublished 2026-09-14
• AFRINIC’s Daily Filenames Advance. The Dataset Still Says 10 September

  Three consecutive archive names deliver the same 491,382 bytes, the same internal serial and the same period end date. That proves repeated public content, not a registry outage. The missing distinction is between a fresh no-change release and an older result served again.

  Primary articlePublished 2026-09-14
• AFRINIC's Bylaws Chair Is Also CEO Designate. The Review Needs a Role-Transition Record

  Mike Silber will not take office as AFRINIC’s chief executive until 1 January 2027. But the constitutional review he was appointed to chair was still working one day after his designation was announced. That overlap is not proof of a conflict. It is a reason to publish the small procedural record that would let members distinguish useful continuity from unrecorded influence.

  Primary articlePublished 2026-09-13
• AFRINIC’s Transfer Log Reaches 13 September. Its Last Event Is 18 June

  AFRINIC’s cumulative transfer file carries a production time and coverage end from 13 September 2026, while its newest transfer event is dated 18 June. Both dates can be correct; the missing evidence is what advancing the first clock proves about the second.

  Primary articlePublished 2026-09-13
• AFRINIC’s Draft Keeps the Community in the Fee Notice, Not the Fee Consultation

  The same sixty days can protect two very different things. AFRINIC’s current Constitution gives Members and the community time to comment while a fee decision is still open. Its August draft keeps sixty days for the community after finalisation, but no longer names that community in the consultation before it.

  Primary articlePublished 2026-09-13
• AFRINIC's 2026 Closure Data Spells Voluntary Two Ways

  AFRINIC has done the useful thing by publishing reproducible statistics on closed memberships and returned number resources. But its current 2026 data place `VOLUNTARY` beside `VOLUNTART`, and the dashboard treats the two strings as different categories. That one-character split is small enough to repair and important enough to repair transparently.

  Primary articlePublished 2026-09-13
• AFRINIC-38 Has a Named Safety Concern. A Hybrid Format Is Not a Risk Assessment.

  A public message from an experienced Malawian operator does not prove that Cape Town is unsafe. It does something more precise: it puts a concrete delegate concern into AFRINIC-38’s record. AFRINIC’s own meeting guide already treats security as a location-selection input. The proportionate answer is a dated risk-and-access note, not a contest between reassurance and alarm.

  Primary articlePublished 2026-09-12
• AFRINIC Calls 122 New Members a 4% Increase. The Baseline Is Missing.

  AFRINIC’s statistics portal compresses five year-to-date counts into five whole-number growth labels. The figures look self-explanatory until one asks the ordinary questions behind any percentage: compared with what, at what time, under which inclusion rules, and rounded how? The raw downloads make two counts reproducible. They do not supply the missing receipt for the word “Increase.”

  Primary articlePublished 2026-09-12
• AFRINIC’s ccTLD Map Counts 27. Three Require an Address Join.

  AFRINIC’s new DNS surface gets the total right, but it does not show the work behind the number. Twenty-four of its 27 ccTLD rows name the registry in a delegated hostname. Somalia, Nigeria and Mali become legible only when their nameserver addresses are joined to AFRINIC’s published anycast prefixes.

  Primary articlePublished 2026-09-12
• AFRINIC's Prefix Checker Can Supply the ASN From BGP. The Verdict Keeps Only the RPKI Time.

  AFRINIC’s public checker can turn a prefix into a route-origin question without asking the user to type an ASN. That convenience joins a BGP observation to an RPKI judgment—but the saved result does not join their clocks. The missing record is small, and operationally consequential.

  Primary articlePublished 2026-09-12
• AFRINIC Can Close a Support Ticket After About Ten Working Days. It Never Ranks the Risk.

  A registry is right to ask who is touching its records. AFRINIC's public Contractual Obligations Check makes that defence concrete: the sender must be registered, the member must be in good standing and a signed agreement must be on file. The problem begins after a check fails. One public sequence covers three operational queues, gives roughly ten working days to cure, then closes the ticket and makes the member start again. The rule never says whether the ticket is routine bookkeeping or a time-sensitive correction to data that other networks may use.

  Primary articlePublished 2026-09-11
• AIRRS Sends “amp;profile”. RIPEstat’s Real AFRINIC Profile Returns 500

  A regional statistics portal can look complete while the choice that is supposed to make it regional never reaches the service under the expected name. AIRRS currently demonstrates that uncomfortable distinction: seven tabs can arrive, yet the evidence says they came through RIPEstat’s default path, not through a successfully selected AFRINIC profile.

  Primary articlePublished 2026-09-11