Summary

  • ARIN's transfer log records REALNETWORKS LLC sending 207.188.16.0/24 to Federal Home Loan Bank of Indianapolis on 9 October, 207.188.17.0/24 to AmayaCloud Inc on 26 October, and 207.188.18.0/23 to Reliance Standard Life Insurance Company on 30 October 2026.
  • The three recipient ranges exactly cover the 1,024 addresses in 207.188.16.0/22. Current ARIN RDAP objects register those same three ranges to the named recipients.

The old block had one name. By the end of October, its four quarters had three registrants. The ARIN transfer snapshot dated 2 November gives the division to the last address. On 9 October, REALNETWORKS LLC transferred 207.188.16.0–207.188.16.255 to Federal Home Loan Bank of Indianapolis. On 26 October, 207.188.17.0–207.188.17.255 went to AmayaCloud Inc. On 30 October, 207.188.18.0–207.188.19.255 went to Reliance Standard Life Insurance Company. A bank, a cloud company and an insurer now appear where one /22 once appeared in the registry.

The arithmetic is unusually clean. The first two recipients each took 256 addresses, or a /24. The third took 512, or a /23. Together they account for every address from 207.188.16.0 through 207.188.19.255: 1,024 addresses, with no gap and no overlap. Each October row repeats that full /22 in original_set, then names its own smaller range in transfer_set. ARIN's description of the common transfer-log format identifies the file as the registry's published transfer record. In this instance the two set fields let a reader separate lineage from the addresses actually transferred on each date.

The live registry gives the second half of the story. ARIN's RDAP record for the first /24 names Federal Home Loan Bank of Indianapolis as registrant. The next /24 names AmayaCloud Inc. The remaining /23 names Reliance Standard Life Insurance Company. Each object's registration timestamp matches its corresponding transfer row after the local time offset is converted to UTC. The file records three handovers; the present objects record three resulting assignments.

The longer lineage sharpens the point. A February 2023 transfer row moved the full 207.188.16.0/22 from RealNetworks, Inc. to REALNETWORKS LLC. The three October 2026 rows then partitioned that inherited block. A dashboard that reads only the repeated original_set could present three sales of the same thousand addresses. The transfer_set values say exactly what moved: one quarter, another quarter, then the remaining half. Registry accounting becomes intelligible when the set boundaries are treated as facts rather than decoration.

The public file does not name prices or a shared contract among the three recipients; those documents would establish the commercial arrangement. The record already answers the narrower, consequential question: which registered organisation holds each address now. It is an odd little cast for one former block, but the registry's job is not to make the cast look tidy. Its job is to keep the boundaries right.