Summary

  • AFRINIC’s 3 November-named extended file lists AS328472 and 102.67.172.0/22 as allocated to the same opaque holder; its 4 November file lists both as reserved with no holder field.
  • A current query for AS328472 returns an AFRINIC RDAP object marked active under ORG-YT1-AFRINIC. The public inventory and the live registration card now display different status words for the same ASN.

The older file puts the ASN and 1,024 IPv4 addresses under the same holder code, F3658FD1, with Burkina Faso country code BF and a 19 April 2019 allocation date. Its filename says 3 November, although its internal snapshot header says 2 November. In the file dated 4 November, both exact resources have country ZZ, blank allocation dates, blank holder fields and status reserved. The paired move is visible at the row level; the files say nothing about the case action that produced it.

The ASN has another public face. AFRINIC’s live RDAP answer for AS328472 returns HTTP 200, names ORG-YT1-AFRINIC, and gives the object status as active. Its registration event still points to 19 April 2019. The response supplies no dated last-change event. An inventory row has moved to reserved while an exact registration card remains available with an active label. Neither screen joins the other with an action identifier.

AFRINIC’s own resource-management guide says its extended file includes reserved resources, but the file does not distinguish among the reasons for reservation. A dated resource-action record identifying this pair and its reservation class would settle why the row changed. Until then the useful fact is the split public presentation: a reserved inventory state and an active RDAP object for the same ASN, with the related IPv4 block on the reserved side of the ledger.

Original records: 3 November archived extended file; 4 November extended file; AS328472 RDAP; AFRINIC resource-management guide; extended-file README.