ARIN's 206.179.0.0/16 transfer changed the delegated date

ARIN Put a 2026 Date on a 1995 Address Block

Why it matters

A full /16 changed hands inside ARIN. The address range stayed intact; the date on its public daily ledger jumped forward thirty-one years. The older clock survived in another ARIN file.

Theo March13 November 2026Reading Time 2 minLast update: 13 November 2026

ARIN’s delegated row for the same 65,536-address block changed from a 1995 date to a 2026 date after the 5 November transfer; its transfer log retains the older registration date.

Summary

ARIN's 4 November delegated file lists 206.179.0.0/16 under Canada with a 30 October 1995 date. Its 12 November file lists the same 65,536 addresses under the United States with a 5 November 2026 date.
ARIN's transfer log records a complete move from 915498 Ontario Inc to Clearwave Fiber on 5 November and retains 30 October 1995 as the source registration date.

The block stayed put; the date took a leap

An address ledger can make old stock look freshly minted with one column. In ARIN's 4 November extended statistics file, the row beginning at 206.179.0.0 covers 65,536 IPv4 addresses. Its country code is CA and its date is 19951030. In the 12 November file, the start and count are identical. The country code is US and the date is 20261105. That date is the day of a holder transfer, thirty-one years after the earlier row's date.

The missing bridge sits in ARIN's 12 November transfer snapshot. It records a RESOURCE_TRANSFER at 16:20:50 UTC on 5 November from 915498 Ontario Inc, marked CA, to Clearwave Fiber, marked US. Both the original_set and transfer_set run from 206.179.0.0 through 206.179.255.255. No slice is missing from the logged transfer. The same record keeps source_registration_date at 30 October 1995.

This is a reporting problem with a very practical audience. A broker, buyer, operator or researcher who takes the current delegated row as the whole biography sees a 2026 date beside an old /16. ARIN's extended-statistics format calls that field an allocation or assignment date; its country field names the holder organisation's country. The transfer record supplies the provenance that the single daily row cannot carry. The files are each intelligible alone, but only together do they show why the date moved.

The published records say nothing about the deal price, routing, the block's current use or a change in operational control. A dated ARIN explanation of how same-registry transfers populate the delegated date field would settle whether this is deliberate convention or a data-quality defect. Until then, the observable fact is sharp enough: the daily date was refreshed while the source registration remained in the historical log.