Summary

  • APNIC's transfer file records 111.223.192.0/19, 8,192 IPv4 addresses, moving from Ace, Inc. to Japan Network Information Center/SORACOM at 06:30:25 UTC on 6 November 2026. APNIC RDAP names SORACOM at 06:30:36.
  • RIPE NCC RIS saw the exact /19 at zero of 321 full-table IPv4 peers immediately before the transfer and at its 8 November 16:00 UTC post-transfer observation. The last sighting recorded for that exact route was 2 September 2025.

The registry clock ran in seconds

At 06:30:25 UTC, one registry entry changed custodians. APNIC's cumulative transfer original lists Ace, Inc. as the Japanese source and Japan Network Information Center/SORACOM as the Japanese recipient. The type is RESOURCE_TRANSFER; APNIC appears on both sides as the RIR. The range starts at 111.223.192.0 and ends at 111.223.223.255. That is one intact /19, not a loose pile of small prefixes: 8,192 IPv4 addresses.

Eleven seconds later, the exact APNIC RDAP entry shows SORACOM as the name on the same interval. Its registration and last-change timestamps both read 06:30:36 UTC. The APNIC Whois view carries the JPNIC namespace and SORACOM name. The transfer row does not list an ASN or IPv6 resource. It records the custody of this IPv4 block, not an entire network business.

Those eleven seconds matter because they show what the registry is good at measuring: who the public record says holds the addresses, and when the record changed. A transfer can be crisp in the ledger even when the operator's deployment plan remains private. For a market in scarce IPv4 space, a verifiable change of registration is a real event. It makes the block identifiable to counterparties, network operators and anyone checking the public directory.

The routing clock refused to follow

The other clock is measured by RIPE NCC RIS before the transfer and after it. Both responses say zero of 321 full-table IPv4 peers saw the exact /19. Neither returned an origin or a more-specific route at those observations. The later request resolves to an actual data time of 8 November at 16:00 UTC. RIS lists the last historical sighting of the exact /19 on 2 September 2025, then under AS56291.

There is a temptation to make the receipt sound like an activation. It is a receipt for custody. The block had already been absent from these RIS views for more than a year before SORACOM's name arrived. The new holder may announce it later, divide it, use it in a different architecture or keep it idle. The APNIC record chooses none of those paths. The RIS observations only date what its full-table peers saw at the queried times.

That separation is the story. In one system, the /19 changed names almost at once. In another, the public route did not appear by the latest observed point. The registry's precision does not make the network clock run faster. IPv4 can sit as an address asset before becoming a visible path for traffic.