Summary

  • APNIC’s 31 October cumulative transfer file has two 27 October rows from Sk Kawsar Ahmad to Sardar Neamul Haque: AS134479 and 103.160.252.0/23, a block of 512 IPv4 addresses.
  • Grouping the October rows by exact source name, recipient name and transfer date yields thirty groups. This is the only group containing both an ASN and an IPv4 prefix. The file supplies no joint transaction identifier or routing timeline.

An address block and an autonomous system number can each be transferred. APNIC put one of each in adjacent parts of its public history on 27 October. The 31 October cumulative transfer file lists AS134479 and 103.160.252.0/23 leaving Sk Kawsar Ahmad for Sardar Neamul Haque. Both entries name APNIC as source and destination RIR and BD as both economies. They share the recipient date. The log treats the resources as two lines. A reader has to perform the join.

The two resources do different jobs. AS134479 is an autonomous system number, a registered identifier used in interdomain routing. The /23 is a set of 512 IPv4 addresses. Holding both makes a plausible network portfolio, but the register records custody, not a packet's path. APNIC says a transfer moves Internet number resources from one legal entity to another and that it updates Whois when the request is processed. The public rows establish a common administrative handoff date for two resource types. They do not timestamp a router change, a ROA change or a customer migration.

The dates before the handoff offer a second clue and a second limit. The ASN row gives 24 December 2020 as its previous delegation date. The IPv4 row gives 28 December 2020. Four days apart at the source, they emerge again under the same recipient on 27 October 2026.

The archive does not say whether the two original delegations were one network launch; that would need an operating record. It does show that the resources were separate registry objects long before the paired transfer.

The pairing is not a casual pattern picked from one page. APNIC’s archive is cumulative, and its published MD5 file matches the captured 31 October file. Filtering all October 2026 rows by exact source name, exact recipient name and date produces thirty groups. Only the Ahmad-to-Haque group contains both asn and ipv4 resource types. That makes this a specific October event, not a claim about how frequently APNIC transfers networks in general. The file is also an older ten-column layout without a transfer_type field, so it supplies no policy-category label for these two entries.

Current registry snapshots add texture without filling the hole. APNIC’s RDAP object for the /23 and RDAP object for AS134479 both identify registrant entity handle ORG-DA42-AP, displayed as DNSBD. The transfer-time recipient in the cumulative file is Sardar Neamul Haque. The two RDAP entities have a last changed date in September 2026, before the listed October transfer. A current object and an event log answer different questions; the cited records do not explain the relationship between the person's name and the DNSBD label. The fact that both resources share the current handle is still useful: it gives an exact present-day registry join without pretending to reconstruct a 27 October business agreement.

What would make the story operational is a timestamped route-origin history for 103.160.252.0/23, any relevant ROA history and a record of who controlled AS134479 at the same moments. APNIC’s transfer guidance allows IPv4 addresses and AS numbers to move as different resource types. Registration can change on one date while network announcements change on another. The public file establishes the former. It has no shared case ID to tell a future auditor that these two rows were one request, nor an operational timestamp that would settle the latter.

That is the stake in two small lines. An ASN names a routing domain; a prefix supplies addresses it may announce. The registry can move both to the same recipient on the same day and leave their relationship implicit in the public archive. For anyone tracing authorization after another holder change, a linkable, versioned receipt joining AS134479 and 103.160.252.0/23 would preserve the administrative story. Routing history would then test the separate question of whether the network followed the paperwork.