Possible reissue candidate; not confirmed available.
Timeline (4)
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-20RIPE NCC− DeregisteredRemoved (return, revocation or reclamation not publicly distinguishable)Strong inference
Statistics
151.216.40.0/21 assigned on 2017-01-19, reserved on 2017-01-20
Inventory
Possible future reissue candidate after hold
Hold estimate
Estimated hold end 2017-07-19. Possible reissue candidate after this date; not confirmed available.
Removed from active registration. The tracker found it by comparing the RIPE NCC's daily statistics. The RIPE NCC's statistics show it assigned (dated 2016-12-14) on 2017-01-19 and reserved on 2017-01-20. Public sources do not distinguish a voluntary return, revocation, or reclamation. The RIPE NCC holds returned, revoked and reclaimed IPv4 space for 180 days (six months), or longer while still routed, before reissuing it, so the estimated hold end is 2017-07-19. This does not confirm availability.
Evidence (3) · classifier 1.4.0,
StatisticsFound by comparing the RIPE NCC's daily statistics: 151.216.40.0/21 assigned on 2017-01-19, reserved on 2017-01-20source · retrieved
BeforeRIPE NCC delegated statistics 2017-01-19 (produced 2017-01-19T22:59:59+00:00), before the change: assigned (dated 2016-12-14)source · retrieved
AfterRIPE NCC delegated statistics 2017-01-20 (produced 2017-01-20T22:59:59+00:00), after the change: 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
2016-12-14RIPE NCC+ RegisteredApparent reissuance of previously removed resourceStrong inference
Statistics
151.216.40.0/21 reserved on 2016-12-13, assigned on 2016-12-14
Inventory
Likely issued from RIPE NCC-controlled inventory
No transfer record matches. The RIPE NCC's statistics show it reserved on 2016-12-13 and assigned (dated 2016-12-14) on 2016-12-14. The tracker saw this range removed from registration on 2016-09-09 (151.216.40.0/21), so it appears to have been issued again from the RIPE NCC's pool.
Evidence (3) · classifier 1.4.0,
StatisticsFound by comparing the RIPE NCC's daily statistics: 151.216.40.0/21 reserved on 2016-12-13, assigned on 2016-12-14source · retrieved
BeforeRIPE NCC delegated statistics 2016-12-13 (produced 2016-12-13T22:59:59+00:00), before the change: reservedsource · retrieved
AfterRIPE NCC delegated statistics 2016-12-14 (produced 2016-12-14T22:59:59+00:00), after the change: assigned (dated 2016-12-14)source · retrieved
Classification history for this change (4 versions)
: Apparent reissuance of previously removed resource, strong inference (classifier 1.4.0) current
2016-09-09RIPE NCC− DeregisteredRemoved (return, revocation or reclamation not publicly distinguishable)Strong inference
Statistics
151.216.40.0/21 assigned on 2016-09-08, reserved on 2016-09-09
Inventory
Possible future reissue candidate after hold
Hold estimate
Estimated hold end 2017-03-08. Possible reissue candidate after this date; not confirmed available.
Removed from active registration. The tracker found it by comparing the RIPE NCC's daily statistics. The RIPE NCC's statistics show it assigned (dated 2016-06-29) on 2016-09-08 and reserved on 2016-09-09. Public sources do not distinguish a voluntary return, revocation, or reclamation. The RIPE NCC holds returned, revoked and reclaimed IPv4 space for 180 days (six months), or longer while still routed, before reissuing it, so the estimated hold end is 2017-03-08. This does not confirm availability.
Evidence (3) · classifier 1.4.0,
StatisticsFound by comparing the RIPE NCC's daily statistics: 151.216.40.0/21 assigned on 2016-09-08, reserved on 2016-09-09source · retrieved
BeforeRIPE NCC delegated statistics 2016-09-08 (produced 2016-09-08T21:59:59+00:00), before the change: assigned (dated 2016-06-29)source · retrieved
AfterRIPE NCC delegated statistics 2016-09-09 (produced 2016-09-09T21:59:59+00:00), after the change: 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
2016-06-29RIPE NCC+ RegisteredApparent reissuance of previously removed resourceStrong inference
Statistics
151.216.40.0/21 reserved on 2016-06-28, assigned on 2016-06-29
Inventory
Likely issued from RIPE NCC-controlled inventory
No transfer record matches. The RIPE NCC's statistics show it reserved on 2016-06-28 and assigned (dated 2016-06-29) on 2016-06-29. The tracker saw this range removed from registration on 2016-06-01 (151.216.40.0/22), so it appears to have been issued again from the RIPE NCC's pool.
Evidence (3) · classifier 1.4.0,
StatisticsFound by comparing the RIPE NCC's daily statistics: 151.216.40.0/21 reserved on 2016-06-28, assigned on 2016-06-29source · retrieved
BeforeRIPE NCC delegated statistics 2016-06-28 (produced 2016-06-28T21:59:59+00:00), before the change: reservedsource · retrieved
AfterRIPE NCC delegated statistics 2016-06-29 (produced 2016-06-29T21:59:59+00:00), after the change: assigned (dated 2016-06-29)source · retrieved
Classification history for this change (4 versions)
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.