Summary

  • APNIC’s 4 November extended file records AS155078, the 512-address IPv4 block 202.50.60.0/23, and 2001:df7:cdc0::/48 with 3 November dates and the same holder identifier A91AA7E7. The prior daily file placed the corresponding space and number inside available pools.
  • Exact APNIC RDAP for all three names ORG-APHL2-AP as registrant, ArcNode (Asia Pacific) Holdings Limited. Its registration events run from 02:36:47 to 03:41:48 UTC on 3 November, a 65-minute-and-one-second span.

Three fresh registry entries make a better opening than a slogan about “digital transformation.” The 4 November APNIC extended file places one ASN, one IPv4 block and one IPv6 block under the identical opaque holder ID A91AA7E7: AS155078, 202.50.60.0 plus 512 addresses, and 2001:df7:cdc0::/48. Every row is dated 3 November. The status words differ for a reason: the ASN and IPv4 block are allocated; the IPv6 /48 is assigned. The file records three kinds of delegation, not three copies of one event.

The previous day’s original adds a useful before image. 202.50.56.0 plus 2,048 addresses was available as one /21. In the 4 November file, the interval becomes an available 202.50.56.0/22 of 1,024 addresses, ArcNode’s allocated 202.50.60.0/23 of 512, and an available 202.50.62.0/23 of 512. The arithmetic closes exactly at 2,048. The IPv6 /48 and ASN had likewise been inside available ranges, with no exact delegated rows in the old snapshot. APNIC’s statistics specification calls these files current-state snapshots without transaction history; the comparison identifies a changed public state, not the approval sequence inside APNIC.

The holder link is stronger than the shared account code alone. ASN RDAP, IPv4 RDAP and IPv6 RDAP each list ORG-APHL2-AP as registrant and spell out ArcNode (Asia Pacific) Holdings Limited. The ASN object is named APHL-AS-AP; both address objects use APHL-HK. Their registration event stamps are 02:36:47, 03:40:09 and 03:41:48 UTC. That is 65 minutes and one second from first record to last. Their later “last changed” stamps differ; the registration clock is a public database clock, not a licence to invent one simultaneous approval meeting.

This three-part receipt matters to anyone who must verify a network’s administrative identifiers. An ASN names a routing-policy identity; IPv4 and IPv6 records locate distinct address resources. A counterparty checking one of those records in isolation may miss that the other two point to the same registered organization. Here the join is reproducible: exact objects, exact registrant handle, exact dates, and one holder ID in the daily file. APNIC’s status guide explains the difference between delegated and available address space; it does not turn the RDAP package into a traffic measurement.

The missing public facts are the dated APNIC case action and independent routing or RPKI records for the new identifiers. Those would establish the decision path and what later became operational. The current evidence already establishes the important administrative result: the registry made one named organization visible across an ASN, a 512-address IPv4 /23 and an IPv6 /48 on one date. A ledger can grant a coherent public identity in three rows. Someone still has to check the network separately.

APNIC originals