rirtracker

IPv4 range · 1,024 addresses

204.16.56.0/22

Now

ARIN statistics
Allocated (dated 2017-01-26), allocated (dated 2017-02-09) (CA, US), in the latest file
Registry
ARIN
Holder
Not looked up
From
ARIN's latest statistics

Latest change

− Remove Change to ARIN's own pool record

Reported
2017-01-25 (ARIN)
Confidence
Observed only
Inventory
No effect on ARIN applicant inventory

Timeline (3)

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.

2017-01-25 ARIN − Remove Change to ARIN's own pool record Observed only
ARIN-Issued
Remove 204.16.56.0-204.16.59.255
Inventory
No effect on ARIN applicant inventory

ARIN's statistics show it reserved on 2017-01-24 and available, reserved on 2017-01-26. ARIN re-cut its own reserved records for this range; nothing was issued or returned. Another change to this range was reported the day before or after (2017-01-26: Remove 204.16.58.0-204.16.59.255; 2017-01-26: Add 204.16.58.0-204.16.59.255), so the before-and-after statistics may include it.

Evidence (3) · classifier 1.4.0,
  1. ARIN-Issued ARIN-Issued report for 2017-01-25: "Remove 204.16.56.0-204.16.59.255" source · retrieved
  2. Before ARIN delegated statistics 2017-01-24 (produced 2017-01-24T06:09:15+00:00), before the report: reserved source · retrieved
  3. After ARIN delegated statistics 2017-01-26 (produced 2017-01-26T06:09:58+00:00), after the report: available, reserved source · retrieved
Classification history for this change (4 versions)
  1. : Change to ARIN's own pool record, observed only (classifier 1.3.0)
  2. : Change to ARIN's own pool record, observed only (classifier 1.3.1)
  3. : Change to ARIN's own pool record, observed only (classifier 1.3.2)
  4. : Change to ARIN's own pool record, observed only (classifier 1.4.0) current
2014-11-04 ARIN Not in ARIN-Issued Removed (return, revocation or reclamation not publicly distinguishable) Strong inference
Inventory
Possible future reissue candidate after hold
Hold estimate
Estimated hold end 2015-01-03. 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 2011-08-04) on 2014-11-03 and reserved on 2014-11-05. 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 2015-01-03. This does not confirm availability.

Evidence (3) · classifier 1.4.0,
  1. Statistics Not listed in ARIN-Issued; found by comparing ARIN's daily statistics: 204.16.56.0/22 allocated on 2014-11-04, reserved on 2014-11-05 source · retrieved
  2. Before ARIN delegated statistics 2014-11-03 (produced 2014-11-03T06:03:55+00:00), before the report: allocated (dated 2011-08-04) source · retrieved
  3. After ARIN delegated statistics 2014-11-05 (produced 2014-11-05T06:04:34+00:00), after the report: reserved source · retrieved
Classification history for this change (4 versions)
  1. : Removed (return, revocation or reclamation not publicly distinguishable), strong inference (classifier 1.3.0)
  2. : Removed (return, revocation or reclamation not publicly distinguishable), strong inference (classifier 1.3.1)
  3. : Removed (return, revocation or reclamation not publicly distinguishable), strong inference (classifier 1.3.2)
  4. : Removed (return, revocation or reclamation not publicly distinguishable), strong inference (classifier 1.4.0) current
2011-08-04 ARIN + Add Unresolved change Observed only
ARIN-Issued
Add 204.16.56.0-204.16.59.255
Inventory
Inventory effect unknown

No transfer record matches. ARIN's statistics show it allocated (dated 2005-10-17) on 2011-08-03 and allocated (dated 2011-08-04) on 2011-08-05. (Until 2013-03-05, ARIN's statistics list only what's issued.) The registration was replaced with one for a different holder record, and public sources don't say why (a transfer not yet logged, a return and reissue, or an organization record change).

Evidence (3) · classifier 1.4.0,
  1. ARIN-Issued ARIN-Issued report for 2011-08-04: "Add 204.16.56.0-204.16.59.255" source · retrieved
  2. Before ARIN delegated statistics 2011-08-03, before the report: allocated (dated 2005-10-17) source · retrieved
  3. After ARIN delegated statistics 2011-08-05, after the report: allocated (dated 2011-08-04) source · retrieved
Classification history for this change (4 versions)
  1. : Unresolved change, observed only (classifier 1.3.0)
  2. : Unresolved change, observed only (classifier 1.3.1)
  3. : Unresolved change, observed only (classifier 1.3.2)
  4. : Unresolved change, observed only (classifier 1.4.0) current

Changes to overlapping ranges

DateRegistryRangeRecorded asWhat happened
2017-02-09ARIN204.16.56.0/23+ AddApparent reissuance
2017-02-09ARIN204.16.56.0/23− RemoveARIN pool record
2017-01-26ARIN204.16.58.0/23+ AddApparent reissuance
2017-01-26ARIN204.16.58.0/23− RemoveARIN pool record

Transfer records

No transfer log has a transfer of any part of this IPv4 range.

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.

This page as data: ip/204.16.56.0-204.16.59.255.json