Summary

  • APNIC's 3 November transfer original records two disjoint Bangladeshi /24s, 103.152.147.0/24 and 103.153.66.0/24, in one transfer at 08:01:40 UTC from Mihir Kumar Datta to Khadija Kabir Pinki. Together they contain 512 IPv4 addresses.
  • Both exact current RDAP objects were registered at 08:02:15 UTC, 35 seconds later. Each uses WSCL-BD and the same registrant handle, ORG-WSCL2-AP, whose organisation record names Windstream Communication Ltd. APNIC's published records give the two names and the clock but no public link between them.

APNIC has two receipts for the same administrative moment, and they answer different identity questions. Its transfer file records a named recipient. Its current registry answers an exact query for each transferred /24 with a company. The records are precise about addresses and seconds. The bridge from the person in the first record to the company in the second is left to the reader.

The dated cumulative transfer original has one RESOURCE_TRANSFER row at 2026-11-03T08:01:40Z. It gives Mihir Kumar Datta as source and Khadija Kabir Pinki as recipient, with BD in both country-code fields and APNIC on both sides of the RIR path. Its transfer_set has 103.152.147.0–103.152.147.255 and 103.153.66.0–103.153.66.255. Each range is one /24 of 256 addresses. They are far apart in address space; a convenient single /23 does not cover them. One line in the transfer log is two exact registry objects.

Ask RDAP for the first /24 and RDAP for the second. Both return exact start and end addresses. Both use network name WSCL-BD. Both carry registration and last changed events at 2026-11-03T08:02:15Z: the same second, 35 seconds after the transfer timestamp. Both name the same registrant organisation handle, ORG-WSCL2-AP, displayed as Windstream Communication Ltd. These are not a broad parent response and a child response accidentally compared as equals. Each query matches the transferred /24 exactly.

The organisation object adds one useful fact. Windstream Communication Ltd's registry entity was registered on 28 December 2020 and last changed on 5 September 2023. The company record was already there when these two IP objects were registered in November 2026. APNIC did not need to invent a new organisation entry to produce the two current /24 answers.

What does APNIC mean when it publishes a recipient name? Its transfer-log format document describes the to_organisation field as the organisation name to which a resource was transferred, and says a reader may test the recipient's holding by querying Whois. That document specifies the legacy pipe-separated log; the present original is JSON with recipient_organization.name and transfer_set. The identity question survives the format change: the row says a person received the resource, while the exact live resource records say a preexisting company is the registrant.

An APNIC transfer decision or account-holder relationship record would show how the named recipient relates to Windstream Communication Ltd. The public surfaces here do not contain that join. For a buyer, lender or operator checking continuity, it matters more than a neat label. The route to a verified chain begins with the exact transfer row, then the exact resource objects, then the entity behind those objects. Skipping the middle step turns 512 addresses into a vague name search; stopping after the first step leaves the current registration out of view.

The source name and recipient name are people, but the reporting target is the institution that publishes the evidence. APNIC records the transfer and the two registration events 35 seconds apart across noncontiguous prefixes. Its records make that timing visible. They also present a transfer-recipient field and a current registrant field without a public relationship key. A registry that wants its data to serve as an authority for resource control has to make that join legible, or leave every serious reader to reconstruct it by hand.

APNIC originals