Summary

  • AFRINIC’s 26 September IPv6 allocation records sum to 273.00058 /32 equivalents; one /24 accounts for 256, or 93.8% of that volume.
  • IANA reports 984,729 /32s available and 477 needed for the next nine months. Its current “Not Eligible” result remains well clear of either allocation trigger.

A monthly total with one outsized component

The September bar on IANA’s AFRINIC IPv6 page is conspicuous: 273, against 10 in August and 11 in July. The page, updated on 12 October from AFRINIC data published the day before, also gives a six-month monthly average of 53. The underlying delegated-statistics file makes the jump easier to interpret. It contains 26 IPv6 rows dated in September. Converting each prefix to /32-equivalent units produces a total of 273.0005798339844. One row, a /24 recorded on 22 September, contributes 256 units. The other 25 rows together contribute just over 17.

This is a large allocation inside a small monthly window, not evidence that 26 separate networks or customers arrived. The file’s rows describe resource allocations or assignments; they do not count unique organisations, active subscribers or deployed networks. A /24 contains 256 /32s because the prefix-length difference is eight bits. That unit conversion, rather than the row count, explains why one line dominates the month.

Flow and inventory answer different questions

The IANA page places the monthly series beside a separate eligibility panel. It currently lists 984,729 /32s of available space, 477 /32s of “necessary space,” a displayed availability of 94% of AFRINIC’s /12, and “Not Eligible.” Under the global IPv6 allocation policy, an RIR can qualify for another allocation if its available space is below half of a /12, or if available space is below its established requirement for the coming nine months.

A /12 contains 1,048,576 /32-equivalent units, so half is 524,288. The displayed AFRINIC inventory is 460,441 units above that mark. It is 984,252 units above the displayed nine-month requirement of 477. Those distances make the present result legible without treating the September chart as a shortage alarm. One /24 is about 0.026% of the currently displayed available inventory.

The figures should not be collapsed into one story. September’s 273 describes outward allocation flow over a month; 984,729 is the remaining-stock figure used in the upstream test; 477 is a forward-looking need estimate under the policy. The IANA page says its longer forecast uses the current average allocation rate, so an unusually large month can affect a short rolling-rate input. It does not turn that input into a measure of IPv6 adoption, and this record alone cannot isolate how much any one allocation changed the current stock figure.

What the registry record can establish

The 30 September and 11 October AFRINIC snapshots contain the same September entries, and their prefix-size arithmetic reproduces IANA’s rounded monthly value. That agreement is useful: it ties the bar to dated registry records rather than to a deployment survey. It still stops at the boundary of the records. The row does not establish that a route was announced, accepted or propagated; that a network carries traffic over IPv6; or that customers can use an IPv6 service.

Nor does 273 mean that AFRINIC made 273 allocations. It is a rounded address-volume measure in /32 units. Twenty-six rows are not twenty-six members. The country code present in a registry row is not a user, operator or service outcome. Nothing in these files gives a reason for the /24, so the article makes no claim about motive or demand.

The most useful next observation is not a prediction from September. It is the next dated IANA update, read alongside the source snapshot: did the monthly series remain elevated, what value did the page use for its average, and how did available space and nine-month necessary space move? If the published figures change, the calculation can be repeated with the same units and the source rows checked for revisions. Until then, the defensible conclusion is narrow: one /24 explains nearly all of a striking month, while IANA’s published inventory remains far from either stated threshold.

Sources: IANA AFRINIC IPv6 allocation and eligibility data; AFRINIC delegated statistics; RIR Statistics Exchange Format; IANA IPv6 allocation procedure.