Every change the tracker has found, newest first. It covers ARIN from 2008-12-01, the RIPE NCC from 2010-04-23, APNIC from 2008-02-15, LACNIC from 2012-06-29 and AFRINIC from 2012-10-03.
2022-12-30ARIN+ AddMerger/acquisition or reorganizationConfirmed
ARIN-Issued
Add 64.112.176.0-64.112.183.255
From
netBlazr ARIN
To
GigStreem ARIN
Inventory
No effect on ARIN applicant inventory
ARIN's transfer log records a merger, acquisition or reorganization from netBlazr (ARIN) to GigStreem (ARIN) on 2022-12-30 22:32 UTC. ARIN-Issued lists it as "Add" because the registration changed hands; it is not a new allocation from ARIN.
Evidence (4) · classifier 1.4.0,
ARIN-IssuedARIN-Issued report for 2022-12-30: "Add 64.112.176.0-64.112.183.255"source · retrieved
Transfer logTransfer log: MERGER_ACQUISITION on 2022-12-30 22:32 UTC, netBlazr (ARIN) to GigStreem (ARIN); resources moved: 64.112.176.0/21source · retrieved
BeforeARIN delegated statistics 2022-12-29 (produced 2022-12-29T14:00:11+00:00), before the report: allocated (dated 2017-02-28)source · retrieved
AfterARIN delegated statistics 2022-12-31 (produced 2022-12-31T14:00:10+00:00), after the report: allocated (dated 2022-12-30)source · retrieved
Classification history for this change (4 versions)
: Merger/acquisition or reorganization, confirmed (classifier 1.3.0)
: Merger/acquisition or reorganization, confirmed (classifier 1.3.1)
: Merger/acquisition or reorganization, confirmed (classifier 1.3.2)
: Merger/acquisition or reorganization, confirmed (classifier 1.4.0) current
2017-02-28ARIN+ AddApparent reissuance of previously removed resourceStrong inference
ARIN-Issued
Add 64.112.176.0-64.112.183.255
Inventory
Likely issued from ARIN-controlled inventory
No transfer record matches. ARIN's statistics show it reserved on 2017-02-27 and allocated (dated 2017-02-28) on 2017-03-01. The tracker saw this range released from hold on 2017-02-21 (64.112.0.0-64.112.191.255), so it appears to have been issued again from ARIN's pool.
Evidence (3) · classifier 1.4.0,
ARIN-IssuedARIN-Issued report for 2017-02-28: "Add 64.112.176.0-64.112.183.255"source · retrieved
BeforeARIN delegated statistics 2017-02-27 (produced 2017-02-27T06:10:19+00:00), before the report: reservedsource · retrieved
AfterARIN delegated statistics 2017-03-01 (produced 2017-03-01T06:09:58+00:00), after the report: allocated (dated 2017-02-28)source · retrieved
Classification history for this change (4 versions)
: Apparent reissuance of previously removed resource, strong inference (classifier 1.4.0) current
2017-02-28ARIN− RemoveChange to ARIN's own pool recordStrong inference
ARIN-Issued
Remove 64.112.176.0-64.112.183.255
Inventory
Part of the issuance reported the same day
ARIN's statistics show it reserved on 2017-02-27 and allocated (dated 2017-02-28) on 2017-03-01. ARIN removed its own pool record for this range as part of issuing it: the same report adds 64.112.176.0-64.112.183.255. The issuance is explained on that line.
Evidence (3) · classifier 1.4.0,
ARIN-IssuedARIN-Issued report for 2017-02-28: "Remove 64.112.176.0-64.112.183.255"source · retrieved
BeforeARIN delegated statistics 2017-02-27 (produced 2017-02-27T06:10:19+00:00), before the report: reservedsource · retrieved
AfterARIN delegated statistics 2017-03-01 (produced 2017-03-01T06:09:58+00:00), after the report: allocated (dated 2017-02-28)source · retrieved
Classification history for this change (4 versions)
: Change to ARIN's own pool record, strong inference (classifier 1.3.0)
: Change to ARIN's own pool record, strong inference (classifier 1.3.1)
: Change to ARIN's own pool record, strong inference (classifier 1.3.2)
: Change to ARIN's own pool record, strong inference (classifier 1.4.0) current
Every record in the ARIN, RIPE NCC, APNIC, LACNIC and AFRINIC transfer logs that moved any part of this IPv4 range (ARIN's from 2009, the RIPE NCC's from 2012, APNIC's from 2010, LACNIC's from 2016, AFRINIC's from 2018). A transfer between two registries is in both logs.
RDAP lookups
Not looked up. The tracker queries RDAP for changes as they're reported (on first sight, after 24 hours and after seven days); older changes aren't looked up because today's RDAP says nothing about the past.