Summary

  • AFRINIC's 3 November 2026 cumulative transfer file has twelve MERGER_ACQUISITION resource rows with twelve distinct source names and HERO TELECOMS (PTY) LTD as recipient. Eleven are dated 24–27 January 2022; the last is dated 14 February.
  • Their nonoverlapping transfer sets contain 27 IPv4 intervals totalling 107,008 addresses, seven IPv6 /32 ranges and thirteen distinct ASNs. The rows count registry movements, not twelve proven corporate deals.

A registry log can make a sprawling transaction look like a clerical afternoon. Open AFRINIC's transfer original and filter for HERO TELECOMS (PTY) LTD in the recipient field. The first entry is dated 24 January 2022. Two follow on the 25th, five on the 26th, and three on the 27th. A twelfth appears on 14 February. Every one lists AFRINIC on both sides and carries the type MERGER_ACQUISITION. The four-day burst is eleven resource rows from eleven named sources. It is not a stopwatch for when their operations merged.

The source list is unusually revealing. Atcomm contributed one 2,048-address interval on 24 January. WIRELESS PROFESSIONELE NETWERKE and HX-Systems appear the next day. Breedenet, Xpress Wireless, Vangibuzz, Kosh Communication Services and Snowball Effect CC are among the five names on 26 January. Safricom Telecommunications, Cloudconnect Networks and LCOM CC make up 27 January. Fusion Wireless, recorded as trading as Sonic Wireless Solutions, appears on 14 February. These are the names the registry chose to publish in its source column, not an independently checked map of each company's ownership or operating footprint.

The arithmetic is where the scale stops being a slogan. The 27 IPv4 intervals in those twelve transfer_set fields do not overlap; they hold 107,008 addresses. Fusion Wireless's February row is the largest single source row at 23,552. WIRELESS PROFESSIONELE NETWERKE contributes 19,456 and Breedenet 18,432. Cloudconnect and LCOM each account for 1,024. Seven rows also carry an IPv6 range, each a /32. Across the bundle there are thirteen distinct ASNs because one source row contains two. The count comes from the transferred intervals, not from parent allocations or a rough sum of CIDR labels.

An ASN matters here because it is more than an address block in a drawer. It identifies an autonomous system in interdomain routing. AFRINIC's current RDAP record for AS37439, one of the thirteen, names the recipient's organization handle ORG-HP1-AFRINIC. That is a useful present-day identity check; the dated transfer file supplies the 2022 sequence. The public records here do not show the traffic, customers, contracts or network integration behind each number-resource move. A routing-history and corporate-document join would settle whether the twelve source rows track twelve operational integrations.

There is a temptation to turn the type field into a corporate biography. Resist it. MERGER_ACQUISITION tells us how AFRINIC classified a resource transfer. Twelve source names tell us how many separate source-labelled entries the file records. They do not reveal purchase prices, legal closing dates or whether a customer ever noticed a change. The more interesting fact is the administrative compression: a dozen differently named resource portfolios were placed under one recipient in a short dated sequence, while the public ledger preserved each origin.

That preserved origin is the ledger's value. A single current holder can make yesterday's smaller networks vanish from a casual lookup. The transfer original keeps their names, dates and exact resources visible. Anyone testing later claims about address provenance, routing control or consolidation can start with those precise ranges and ASNs instead of a company press line. The registry has supplied the join keys. It has not supplied the business story that joins them.

Registry originals: AFRINIC transfer file; AFRINIC RDAP, AS37439.