Summary

The arithmetic is unusually clean. The 3 November row begins at 202.36.164.0, counts 1,024 addresses and says available. In the 4 November file, 202.36.164.0/24 and 202.36.165.0/24 each take 256 addresses under country code ID; 202.36.166.0/23 takes the remaining 512 under IN. There is no fourth fragment hiding at the edge. Three non-overlapping records consume the old /22 exactly.

The two Indonesian entries are assigned, dated 3 November, and carry different opaque holder IDs. The Indian /23 is allocated, dated 2 November, with a third ID. APNIC's status guide treats both assigned and allocated as delegated, while available space remains in its pool. Its exchange-format specification says the country code identifies the organization at allocation or assignment, not the place where packets travel. This file records administrative distribution, not a traffic map.

The exact APNIC RDAP record for the Indian /23 names handle DCPLIND and dates registration to 2 November at 22:59:38 UTC. The daily rows do not explain why that registration date precedes the two Indonesian row dates, or identify a common decision tying the three entries together. A dated APNIC allocation and assignment record would settle the sequence. For now, the public result is sharp: one free /22 became three delegations across two country codes, and not one address remained available in that interval.

Official records: APNIC address states; APNIC statistics format; exact /23 RDAP.