Summary

  • ARIN records three MERGER_ACQUISITION transfers from City of Ruston to Rightfiber at exactly 22:24:57 UTC on 27 October 2026: ASN 18889, IPv6 2602:fff0::/36, and IPv4 192.152.192.0/23 (512 addresses).
  • The three resources entered ARIN's source register on different dates in 2012 and 2015. The public transfer file gives them one administrative timestamp but no case document or network cutover sequence connecting that registry event to operations.

At 22:24:57 UTC, ARIN made three different pieces of a city's Internet identity travel together on paper. Its 2 November cumulative transfer file has three rows with City of Ruston as source and Rightfiber as recipient, all dated 27 October 2026 and all marked MERGER_ACQUISITION. One is an autonomous system number, AS18889. One is the IPv6 block 2602:fff0::/36. One is the IPv4 block 192.152.192.0/23, which contains 512 addresses. Both parties are coded US and ARIN. The register presents a tidy bundle. The network that gives the bundle practical meaning is messier.

These are not three copies of one row. AS18889 is the identifier used in the interdomain routing system. The IPv6 range is a large address allocation, represented in ARIN's file by its exact starting and ending addresses. The IPv4 /23 is a separate, much smaller address range. The file gives each resource its own original_set and transfer_set; the bounds match within each row. It also gives each a different source registration date: 13 July 2012 for the ASN, 4 December 2012 for IPv6, and 18 February 2015 for IPv4. The common transfer timestamp therefore joins resources that entered the register at different times and serve different technical roles.

ARIN's transfer quick guide explains the 8.2 route behind its broad merger, acquisition and reorganization category. The recipient must present evidence of acquired assets that used the number resources or of acquisition of the current registrant. The guide lists instruments such as asset purchase agreements, filed merger documents and court orders. It also places continuing maintenance work on holders: organization and contact records, address reassignments, reverse DNS and fees. The Number Resource Policy Manual supplies the governing rule. The policy framework gives a reason for ARIN to process the three rows together. The published transfer file does not identify which instrument or assets connect this city and this recipient.

One timestamp is a strong database fact and a weak operational narrative. A registry can update the holder of an ASN and address blocks as one case. Traffic may move on a different clock. Reverse DNS may have its own delegation work. Contacts may need revision; downstream assignments may need checking. Those are practical tasks identified by the categories in ARIN's own guide, not documented events in the Ruston file. The rows contain no routing cutover time, customer transition sequence or service observation. Calling 22:24:57 the moment a network changed hands in operation would add a fact the public record does not supply.

This distinction matters because all three resource classes have to remain legible after a change of registrant. A reader who sees only the IPv4 /23 misses the ASN and the IPv6 /36. A reader who sees only the ASN might assume the addresses followed automatically. ARIN's three rows let anyone assemble the administrative bundle, but they offer no shared case ID that identifies the underlying legal instrument or any public continuity record. A case file naming the acquired assets and the operational timeline would change the assessment.

Today the defensible statement is narrower and sharper: ARIN records a same-second transfer of three distinct Internet number resources from the city to Rightfiber.