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.
ARIN's transfer log records a transfer from Thesys Technologies, LLC (ARIN) to LeveLATS (ARIN) on 2019-06-24 19:53 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 2019-06-24: "Add 204.76.204.0-204.76.205.255"source · retrieved
Transfer logTransfer log: RESOURCE_TRANSFER on 2019-06-24 19:53 UTC, Thesys Technologies, LLC (ARIN) to LeveLATS (ARIN); resources moved: 204.76.204.0/23source · retrieved
BeforeARIN delegated statistics 2019-06-23 (produced 2019-06-23T14:00:16+00:00), before the report: assigned (dated 2017-09-21)source · retrieved
AfterARIN delegated statistics 2019-06-25 (produced 2019-06-25T14:00:16+00:00), after the report: assigned (dated 2019-06-24)source · retrieved
Classification history for this change (4 versions)
: Intra-ARIN transfer, confirmed (classifier 1.4.0) current
2017-09-21ARIN+ AddApparent reissuance of previously removed resourceObserved only
ARIN-Issued
Add 204.76.204.0-204.76.205.255
Inventory
Likely issued from ARIN-controlled inventory
No transfer record matches. ARIN's statistics show it reserved on 2017-09-20 and assigned (dated 2017-09-21) on 2017-09-22. The tracker saw this range released from hold on 2017-09-20 (204.76.204.0-204.76.205.255), so it appears to have been issued again from ARIN's pool. Another change to this range was reported the day before or after (2017-09-20: Remove 204.76.204.0-204.76.205.255), so the before-and-after statistics may include it.
Evidence (3) · classifier 1.4.0,
ARIN-IssuedARIN-Issued report for 2017-09-21: "Add 204.76.204.0-204.76.205.255"source · retrieved
BeforeARIN delegated statistics 2017-09-20 (produced 2017-09-20T05:10:46+00:00), before the report: reservedsource · retrieved
AfterARIN delegated statistics 2017-09-22 (produced 2017-09-22T05:10:47+00:00), after the report: assigned (dated 2017-09-21)source · retrieved
Classification history for this change (4 versions)
: Apparent reissuance of previously removed resource, observed only (classifier 1.3.0)
: Apparent reissuance of previously removed resource, observed only (classifier 1.3.1)
: Apparent reissuance of previously removed resource, observed only (classifier 1.3.2)
: Apparent reissuance of previously removed resource, observed only (classifier 1.4.0) current
2017-09-21ARIN− RemoveChange to ARIN's own pool recordObserved only
ARIN-Issued
Remove 204.76.204.0-204.76.205.255
Inventory
Part of the issuance reported the same day
ARIN's statistics show it reserved on 2017-09-20 and assigned (dated 2017-09-21) on 2017-09-22. ARIN removed its own pool record for this range as part of issuing it: the same report adds 204.76.204.0-204.76.205.255. The issuance is explained on that line. Another change to this range was reported the day before or after (2017-09-20: Remove 204.76.204.0-204.76.205.255), so the before-and-after statistics may include it.
Evidence (3) · classifier 1.4.0,
ARIN-IssuedARIN-Issued report for 2017-09-21: "Remove 204.76.204.0-204.76.205.255"source · retrieved
BeforeARIN delegated statistics 2017-09-20 (produced 2017-09-20T05:10:46+00:00), before the report: reservedsource · retrieved
AfterARIN delegated statistics 2017-09-22 (produced 2017-09-22T05:10:47+00:00), after the report: assigned (dated 2017-09-21)source · retrieved
Classification history for this change (4 versions)
: Change to ARIN's own pool record, observed only (classifier 1.3.0)
: Change to ARIN's own pool record, observed only (classifier 1.3.1)
: Change to ARIN's own pool record, observed only (classifier 1.3.2)
: Change to ARIN's own pool record, observed only (classifier 1.4.0) current
2017-09-20ARIN− RemoveNo substantive resource change foundObserved only
ARIN-Issued
Remove 204.76.204.0-204.76.205.255
Inventory
No effect on ARIN applicant inventory
ARIN-Issued lists it as "Remove", but ARIN's statistics show the same record before and after (reserved). Another change to this range was reported the day before or after (2017-09-21: Remove 204.76.204.0-204.76.205.255; 2017-09-21: Add 204.76.204.0-204.76.205.255), so the before-and-after statistics may include it.
Evidence (3) · classifier 1.4.0,
ARIN-IssuedARIN-Issued report for 2017-09-20: "Remove 204.76.204.0-204.76.205.255"source · retrieved
BeforeARIN delegated statistics 2017-09-19 (produced 2017-09-19T05:11:22+00:00), before the report: reservedsource · retrieved
AfterARIN delegated statistics 2017-09-21 (produced 2017-09-21T05:11:33+00:00), after the report: reservedsource · retrieved
Classification history for this change (4 versions)
: No substantive resource change found, observed only (classifier 1.3.0)
: No substantive resource change found, observed only (classifier 1.3.1)
: No substantive resource change found, observed only (classifier 1.3.2)
: No substantive resource change found, observed only (classifier 1.4.0) current
2016-11-08ARINNot in ARIN-IssuedRemoved (return, revocation or reclamation not publicly distinguishable)Strong inference
Inventory
Possible future reissue candidate after hold
Hold estimate
Estimated hold end 2017-01-07. 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 assigned (dated 2011-08-10) on 2016-11-07 and reserved on 2016-11-09. 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 2017-01-07. This does not confirm availability.
Evidence (3) · classifier 1.4.0,
StatisticsNot listed in ARIN-Issued; found by comparing ARIN's daily statistics: 204.76.204.0/23 assigned on 2016-11-08, reserved on 2016-11-09source · retrieved
BeforeARIN delegated statistics 2016-11-07 (produced 2016-11-07T06:08:47+00:00), before the report: assigned (dated 2011-08-10)source · retrieved
AfterARIN delegated statistics 2016-11-09 (produced 2016-11-09T06:09:28+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
2011-08-10ARIN+ AddApparent new issuanceStrong inference
ARIN-Issued
Add 204.76.204.0-204.76.205.255
Inventory
Likely issued from ARIN-controlled inventory
No transfer record matches. ARIN's statistics show it not issued on 2011-08-09 and assigned (dated 2011-08-10) on 2011-08-11. (Until 2013-03-05, ARIN's statistics list only what's issued.) It moved from ARIN's unissued pool to an active registration dated around the report, so it appears to be newly issued by ARIN.
Evidence (3) · classifier 1.4.0,
ARIN-IssuedARIN-Issued report for 2011-08-10: "Add 204.76.204.0-204.76.205.255"source · retrieved
BeforeARIN delegated statistics 2011-08-09, before the report: not issuedsource · retrieved
AfterARIN delegated statistics 2011-08-11, after the report: assigned (dated 2011-08-10)source · retrieved
Classification history for this change (4 versions)
: Apparent new issuance, strong inference (classifier 1.3.2)
: Apparent new issuance, strong inference (classifier 1.4.0) current
Transfer records (1)
Date (UTC)
Log
Type
Range moved
From
To
ARIN
Resource transfer
204.76.204.0/23
Thesys Technologies, LLC ARIN
LeveLATS ARIN
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.