ARIN moved 11 HugeServer resources to Xitoring; ASN kept old name

ARIN Moved 11 HugeServer Resources in One Second. AS25780 Kept the Old Name.

Why it matters

The 3 November transfer file puts five IPv4 ranges, five IPv6 ranges and one ASN under Xitoring LLC at the same instant. ARIN’s current ASN record names the new registrant while its network label still says HUGESERVER-NETWORKS.

Theo March3 November 2026Reading Time 2 minLast update: 3 November 2026

ARIN’s 3 November transfer file lists eleven HugeServer-to-Xitoring resources at the same second; AS25780 RDAP still displays the old network name.

Summary

ARIN added 11 HugeServer Networks → Xitoring LLC merger/acquisition rows at 00:40:46 UTC on 3 November: five IPv4 ranges, five IPv6 ranges and AS25780.
AS25780’s current RDAP identifies Xitoring as registrant and records the same change instant, but its name field remains HUGESERVER-NETWORKS.

A corporate transfer can take one second in a public ledger and years in its labels. ARIN’s 2 November cumulative file held 46,031 transfers. Its 3 November file contains 46,050, including 11 new rows from HugeServer Networks, LLC to Xitoring LLC. Every one carries the same MERGER_ACQUISITION type and 03 November 00:40:46 UTC timestamp. Five rows cover 3,072 IPv4 addresses, five cover IPv6 ranges, and the last carries AS25780. On each row, the original and transferred range are equal.

The ASN’s live RDAP object captures the distinction the spreadsheet cannot. Its registrant is Xitoring LLC and its last-change time is 2 November 19:40:46 Eastern, the same instant as the UTC transfer. Yet the resource name is still HUGESERVER-NETWORKS. A 23.186.176.0/24 record also gives Xitoring as registrant, although its name is MIAMI-FLORIDA; the 2605:8680:: range lists Xitoring alongside HSN-IPV6. Name is a historical identifier here, not a reliable shortcut to the present registrant.

ARIN’s transfer guide says its merger and acquisition route requires evidence of acquired assets or the existing registrant, and assigns record-maintenance duties to holders. The public transfer file contains no asset instrument or cutover schedule. Some starting-address RDAP queries also reach more specific reassignment objects, so eleven transfer rows must not be mistaken for eleven identical live lookup results. The log establishes a registry change, not the operational moment a customer’s packets changed course.