Summary

The paperwork took seconds. The network observation took a day. APNIC's transfer row covers one Philippine /23, 512 IPv4 addresses, and names the old and new registrants. Its timestamp is 27 October, 00:54:39 UTC. The exact RDAP object for 103.153.234.0/23 carries the same bounds, active status and recipient handle ORG-DUSV1-AP; its registration event is 00:55:14. Thirty-five seconds separate the two public records. The registrant card spells out Dagupan Urban Satellite Vision Inc.

RIPE's routing collectors tell the next part with less convenient timing. At 08:00 UTC on 28 October the precise /23 registered zero of 323 RIS IPv4 peers. At 16:00 it registered 323 of 323, with AS56262 as origin. The APNIC object for AS56262 names the same Dagupan registrant; the ASN's own registration dates back to 2011. APNIC's transfer row moves the address block, while the route appears under a previously registered AS. The next 00:00 RIS sample still has complete coverage, 322 of 322 peers; the 3 November 08:00 sample shows 323 of 323.

That is a useful split in the evidence. A recipient or network operator relying on the APNIC holder timestamp could mark custody settled while an exact-route check still returned no RIS peers the next morning. By that afternoon, the same prefix was visible to every peer in the sample. The registry's fast administrative receipt and the routing system's later public observation are two different milestones, even when both end with a clean answer.