Summary

  • Three October 2026 ARIN transfer rows move three separate /24s from PF IPV4 Borrower, LLC to Full Potential Solutions, Joy Labs Ventures and a California air-quality district. Current ARIN RDAP leaves the fourth /24 with PF IPV4 Borrower.
  • The 22 October row narrows original_set to 216.52.237.0–216.52.239.255. Four days later, a row for the same source expands that field back to 216.52.236.0–216.52.239.255, including the /24 transferred on 8 October. The transfer_set fields and four current registrations tell the actual holder-by-holder story.

ARIN has put a vanished /24 back into a field labelled original_set. It did not put the addresses back under the old holder. That distinction is the entire story in three rows of ARIN's 2 November transfer snapshot, and it is why a transfer log is useful only if its columns are read as columns rather than as a substitute for the register.

Start with four adjacent slices, 216.52.236.0/24 through 216.52.239.0/24. On 8 October, the log shows PF IPV4 Borrower, LLC transferring .236/24 to Full Potential Solutions LLC. The original_set spans all four /24s, 1,024 addresses; the transfer_set is just the first 256. On 22 October, a second row sends .239/24 to Joy Labs Ventures LLC. This time original_set begins at .237.0 and ends at .239.255, a 768-address remainder. So far, a reader might treat the field as a shrinking snapshot of the source-side range.

The third row spoils that neat interpretation. On 26 October, PF IPV4 Borrower transfers .237/24 to San Joaquin Valley Unified Air Pollution Control District. Its original_set starts again at .236.0 and ends at .239.255: the full 1,024 addresses, including the .236/24 already shown as transferred on 8 October. All three rows keep the same source_registration_date, 24 August 1998, and the same named source. The specific transferred blocks remain separate and non-overlapping. The surprising movement is in the wider field, not in the destination of any of the three /24s.

Four current ARIN RDAP objects provide the independent ledger check. The .236/24 registration names Full Potential Solutions. The .239/24 object names Joy Labs Ventures. The .237/24 object names the air-quality district. The remaining .238/24 still names PF IPV4 Borrower. Three recipients have 768 addresses; the source retains 256. The transfer dates describe how that distribution was recorded. Present RDAP describes who stands behind each slice now.

The ARIN transfer-log format page describes a cumulative JSON file with original_set and transfer_set fields; it does not publish a per-row processing explanation for this apparent widening. An ARIN explanation of the source range selected for the 26 October row would settle why the earlier-transferred .236/24 appears there. The public records already settle the holder map more narrowly: the later row transfers .237/24, not .236/24, and today's .236/24 registrant is Full Potential Solutions.

That is a genuine data-interpretation stake. A spreadsheet that subtracts each transfer_set from each row's original_set could count .236/24 as available to PF IPV4 Borrower on 26 October, even though the current register says otherwise. A dashboard that treats original_set as a dated inventory could invent a reverse transfer which no transfer_set records. The column may serve another purpose in ARIN's processing, but that purpose is not specified in the published row. The right way to reconstruct this particular split is to follow each exact transferred interval and then check the live RDAP objects.

Unlike an October RealNetworks case in which one repeated /22 source range tiles cleanly into three recipient blocks, the source-range text here changes direction. The account name adds a certain market flavour, but the record gives no loan terms, price or financing instrument. The publishable fact is plainer and more useful: three completed /24 moves, a fourth /24 retained, and a public field whose apparent range should not be promoted into a historical holder claim without a registry explanation.