Summary

Two deeds, one engine number

ARIN did not bury the handoff in a single vague corporate update. The transfer file has a row for the autonomous system number and another for the 256 IPv4 addresses. Both carry the same source, recipient and second. The source registration dates differ: 17 September 2008 for the ASN, 14 September 2009 for the /24. At the moment of transfer, two assets with separate histories moved as a pair.

The current directory mirrors the receipts. AS46429 has the name ONVIS-6-46429; 74.117.189.0/24 has the name ONVIS-6. Both point to ONVIS-6, the ARIN entity for OnviSource, Inc. Both show registration and last change at 17:43:47-05:00 on 3 November, exactly 22:43:47 UTC. The paper trail is unusually neat: two transfer rows, two exact resource objects and one organization card meet at the same second.

The route tells a more interesting story than a tidy registry alone. RIS’s routing-history output for the exact /24 shows AS46429 as the origin across its 2–4 November sampled timeline. Its scheduled status snapshots bracket the transfer: 321 of 322 full-table IPv4 peers saw the /24 before it; 323 of 323 saw it afterward. The denominator changed, so those fractions are observations, not a claim that the transfer improved reachability. The origin string stayed the same.

That matters because a number-resource transfer can change legal and registry responsibility while users keep seeing packets flow under the familiar ASN. If an incident response database keyed contacts only to AS46429, it might miss that the registrant changed. If it keyed only to OnviSource’s new name, it might misread a pre-transfer routing trace as evidence of a new network. ARIN’s timestamp tells who held the resources after the handoff; RIS preserves what its collectors saw before and after.

A high-frequency BGP trace or operator change log would show whether there was any brief cutover inside the eight-hour RIS sampling interval. The published snapshots already establish the narrower, useful result: same exact /24, same observed origin, separate registrant after an explicit paired transfer.

The strange part is not that a route survived a paperwork change. The strange part is how often public inventories force one date to do three jobs. The source registration dates are 2008 and 2009. The route has its own history. The transfer takes one second in ARIN’s log. Treating those clocks as interchangeable erases the reason to keep a registry in the first place.