Summary

  • APNIC’s 3 November cumulative transfer original records one RESOURCE_TRANSFER at 2026-11-03T05:03:43Z: 103.113.136.0–103.113.139.255 from NIXI/EXCELPL to NIXI/VNPL, both India-coded and within APNIC. Exact IP RDAP now names the full interval VNPL, registered at 05:03:51 UTC, eight seconds after the transfer row. Exact AS136334 RDAP names VNPL-AS; it was registered in 2017 and last changed in September 2025. The IP and ASN records share IRT-VNPL-IN and MD882-AP contacts.
  • RIPE NCC RIS’s 3 November 00:00 UTC /22 status and 4 November 00:00 UTC status both list 103.113.136.0/24 and 103.113.137.0/24 as more specifics with origin AS136334. Neither snapshot lists the upper .138/24 or .139/24. The exact /22 itself is at 0 of 322 full-table IPv4 peers in both snapshots.

Two routes before the ink dried

A /22 is four adjacent /24s, each with 256 IPv4 addresses. The transfer row moved all four, from .136 through .139, in one administrative act. RIS had already found the first two under AS136334 at midnight on 3 November, more than five hours before APNIC’s transfer timestamp. Its next midnight view listed the same two. The recipient’s ASN record carries the name VNPL-AS and an older registration history. The observed announcement was therefore already tied to a VNPL-named ASN when the new IP card arrived.

The eight seconds between the transfer row and IP RDAP registration are tempting drama, but they describe two registry timestamps. The real sequence is longer: a VNPL-named ASN registered in 2017; two /24s visible under it before the 2026 transfer; an APNIC receipt for the entire /22 at 05:03:43; a new full-range RDAP card at 05:03:51; and the same two /24s listed by RIS the following midnight. A dated change log or BGP history for the two /24s would pin down the earlier operational decision that put them into the network.

The upper half has its own meaning. .138/24 and .139/24 were inside the transfer. They do not appear in either /22 status response’s more-specific list. Thus the public transfer covered 1,024 addresses while the listed more-specific footprint covered 512. The exact aggregate /22 also had zero visibility in the full-table peer sample. A reader who sees a whole-block transfer and imagines a whole-block route has quietly promoted a registry inventory into a traffic map.

The source and recipient labels contain NIXI/, but the published row identifies EXCELPL and VNPL as different parties. The exact RDAP joins the recipient name to the current IP card and the ASN’s shared contacts. The commercial contract and the earlier route-authorization record are missing from this public packet. The mismatch between administrative timing and observed routing is the useful fact. The registry can tell us when it changed the name. RIS can tell us what it had already seen.