Summary

  • APNIC’s 2 November transfer file contains 21 RESOURCE_TRANSFER rows to NIXI/YOTTA from 20 different literal NIXI/... source names between April 2022 and October 2026. Those rows carry 27 disjoint IPv4 ranges, 25,600 addresses in all.
  • All 27 exact ranges now return YOTTA in APNIC RDAP. The common NIXI/ prefix is a registry layer worth reading through, not a substitute for the distinct source suffixes or the present resource objects.

A slash can swallow twenty senders if the accountant stops reading at it. Search APNIC’s official transfer file for NIXI/YOTTA, and one receiving label appears 21 times. Search only for NIXI, and the source side appears to repeat the same name as well. Look after the slash. APNIC recorded NIXI/SUPERPHONEENTERPRISE, NIXI/SPACENETINDIA-IN, NIXI/TRACKNET, NIXI/APEXNETW and sixteen other distinct source strings. The oldest of these rows is 20 April 2022; the newest is 26 October 2026. They are not a single handoff broken into 21 lines on one afternoon.

The raw counts are more revealing than the shared prefix. The 21 rows name 20 distinct exact source strings; NIXI/SPACENETINDIA-IN appears twice. Three rows are dated 2022, seven 2023, five 2024, four 2025 and two 2026. All are labelled RESOURCE_TRANSFER, APNIC to APNIC, India to India. APNIC’s transfer guide defines a transfer as a movement of number resources between legal entities and says it updates Whois accordingly. The JSON exposes names and resource intervals, not a corporate identifier joining or separating every suffix. That distinction matters before anyone calls this one company shuffling cards inside itself.

One row can carry more than one address range. Here the 21 rows contain 27 nonoverlapping IPv4 intervals: twenty-four /22s of 1,024 addresses each, two /24s of 256 and one /23 of 512. Together they make 25,600 addresses. Counting rows as blocks would miss six intervals; counting all intervals as /22s would miss the two smaller sizes. Every exact start address in this 27-range set was checked against APNIC RDAP. Each lookup returned matching start and end bounds and the current name YOTTA. For example, the newest /22, the May 2026 /22 and an April 2022 /22 all lead to that name. This is a checked set of transferred ranges, not an inventory of every address YOTTA may hold.

The newest entry is a clean illustration. At 04:45:32 UTC on 26 October, NIXI/APEXNETW transferred 103.110.12.0–103.110.15.255 to NIXI/YOTTA. The prior 2026 row, on 15 May, moved 182.255.56.0–182.255.59.255 from NIXI/TRACKNET to the same recipient string. Two dates, two source suffixes, two separate /22s. One common recipient does not erase the sources.

Why does APNIC’s label carry a national-looking wrapper? APNIC’s National Internet Registries page lists IRINN for India among seven NIRs and explains that these registries have their own members and perform registrations under APNIC’s regional policies. Its NIR operations policy describes the national registry’s management of member records. The NIXI/ strings in this transfer set are the literal public labels; the page does not supply a legal-entity map for the 20 suffixes. A current member-to-legal-entity mapping would settle that classification.

The practical stake is source attribution. A reader who reports “21 NIXI transfers” has preserved the count but discarded the part of each name that distinguishes the senders. A reader who reports “21 address blocks” has discarded six exact resource intervals. APNIC’s event log, its national-registry framework and current RDAP together permit a better account: 20 literal source labels across five calendar years, 21 completed transfers, 27 currently matching YOTTA range objects and 25,600 IPv4 addresses. That account says exactly what the public record can bear.