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.
2024-05-22ARINTransfer logMerger/acquisition or reorganizationConfirmed
Transfer log
Merger/acquisition: KW Datacenter (ARIN) to KW Datacenter (ARIN)
From
KW Datacenter ARIN
To
KW Datacenter ARIN
Inventory
No effect on ARIN applicant inventory
ARIN's transfer log records a merger, acquisition or reorganization from KW Datacenter (ARIN) to KW Datacenter (ARIN) on 2024-05-22 21:04 UTC. The registration changed hands; it is not a new allocation from ARIN. ARIN-Issued and ARIN's statistics don't show this change; only the transfer log records it.
Evidence (3) · classifier 1.4.0,
Transfer logTransfer log: MERGER_ACQUISITION on 2024-05-22 21:04 UTC, KW Datacenter (ARIN) to KW Datacenter (ARIN); resources moved: 45.62.192.0/18source · retrieved
BeforeARIN delegated statistics 2024-05-21 (produced 2024-05-21T13:00:47+00:00), before the report: allocated (dated 2015-03-05)source · retrieved
AfterARIN delegated statistics 2024-05-23 (produced 2024-05-23T13:00:47+00:00), after the report: allocated (dated 2015-03-05)source · retrieved
2024-03-11ARINNot in ARIN-IssuedRemoved (return, revocation or reclamation not publicly distinguishable)Strong inference
Inventory
Possible future reissue candidate after hold
Hold estimate
Estimated hold end 2024-05-10. Possible reissue candidate after this date; not confirmed available.
Removed from active registration. ARIN-Issued didn't list this; the tracker found it by comparing ARIN's daily statistics. ARIN's statistics show it allocated (dated 2015-03-05) on 2024-03-10 and reserved on 2024-03-12. Public sources do not distinguish a voluntary return, revocation, or reclamation. ARIN holds returned, revoked and reclaimed IPv4 space for 60 days before reissuing it, so the estimated hold end is 2024-05-10. This does not confirm availability.
Evidence (3) · classifier 1.4.0,
StatisticsNot listed in ARIN-Issued; found by comparing ARIN's daily statistics: 45.62.192.0/18 allocated on 2024-03-11, reserved on 2024-03-12source · retrieved
BeforeARIN delegated statistics 2024-03-10 (produced 2024-03-10T13:00:44+00:00), before the report: allocated (dated 2015-03-05)source · retrieved
AfterARIN delegated statistics 2024-03-12 (produced 2024-03-12T13:00:43+00:00), after the report: reservedsource · retrieved
Classification history for this change (4 versions)
: Removed (return, revocation or reclamation not publicly distinguishable), strong inference (classifier 1.3.0)
: Removed (return, revocation or reclamation not publicly distinguishable), strong inference (classifier 1.3.1)
: Removed (return, revocation or reclamation not publicly distinguishable), strong inference (classifier 1.3.2)
: Removed (return, revocation or reclamation not publicly distinguishable), strong inference (classifier 1.4.0) current
2015-03-05ARIN+ AddApparent reissuance of previously removed resourceStrong inference
ARIN-Issued
Add 45.62.192.0-45.62.255.255
Inventory
Likely issued from ARIN-controlled inventory
No transfer record matches. ARIN's statistics show it available on 2015-03-04 and allocated (dated 2015-03-05) on 2015-03-06. The tracker saw this range released from hold on 2011-08-03 (45.2.0.0-45.255.255.255), so it appears to have been issued again from ARIN's pool.
Evidence (3) · classifier 1.4.0,
ARIN-IssuedARIN-Issued report for 2015-03-05: "Add 45.62.192.0-45.62.255.255"source · retrieved
BeforeARIN delegated statistics 2015-03-04 (produced 2015-03-04T06:05:32+00:00), before the report: availablesource · retrieved
AfterARIN delegated statistics 2015-03-06 (produced 2015-03-06T06:05:17+00:00), after the report: allocated (dated 2015-03-05)source · retrieved
Classification history for this change (4 versions)
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.