2027-05-15 (from what APNIC's statistics show; it publishes no period)
Now
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.
2026-05-15APNIC− DeregisteredRemoved (return, revocation or reclamation not publicly distinguishable)Strong inference
Statistics
116.206.164.0/22 allocated on 2026-05-15, reserved on 2026-05-16
Inventory
Possible future reissue candidate after hold
Hold estimate
Estimated hold end 2027-05-15. Possible reissue candidate after this date; not confirmed available.
Removed from active registration. The tracker found it by comparing APNIC's daily statistics. APNIC's statistics show it allocated (dated 2017-03-30) on 2026-05-15 and reserved on 2026-05-16. Public sources do not distinguish a voluntary return, revocation, or reclamation. APNIC publishes no hold period, but its statistics have released returned IPv4 space a year after the removal or later since 2014, so the tracker estimates the hold ends on 2027-05-15. That is what APNIC has done, not a rule it states. This does not confirm availability.
Evidence (3) · classifier 1.4.0,
StatisticsFound by comparing APNIC's daily statistics: 116.206.164.0/22 allocated on 2026-05-15, reserved on 2026-05-16source · retrieved
BeforeAPNIC delegated statistics 2026-05-15, before the change: allocated (dated 2017-03-30)source · retrieved
AfterAPNIC delegated statistics 2026-05-16, after the change: reservedsource · retrieved
Classification history for this change (5 versions)
: Removed (return, revocation or reclamation not publicly distinguishable), strong inference (classifier 1.2.0)
: 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
2025-07-04APNIC+ RegisteredRestored to the same holderStrong inference
Statistics
116.206.164.0/22 reserved on 2025-07-04, allocated on 2025-07-05
Inventory
No effect on APNIC applicant inventory
No transfer record matches. APNIC's statistics show it reserved on 2025-07-04 and allocated (dated 2017-03-30) on 2025-07-05. The tracker saw it removed from registration on 2025-02-19 (135 days earlier), and it is back with the same holder record it had before, so it went back to its previous holder rather than to a new one: most likely a suspension lifted, a reinstatement or a correction.
Evidence (3) · classifier 1.4.0,
StatisticsFound by comparing APNIC's daily statistics: 116.206.164.0/22 reserved on 2025-07-04, allocated on 2025-07-05source · retrieved
BeforeAPNIC delegated statistics 2025-07-04, before the change: reservedsource · retrieved
AfterAPNIC delegated statistics 2025-07-05, after the change: allocated (dated 2017-03-30)source · retrieved
Classification history for this change (4 versions)
: Restored to the same holder, strong inference (classifier 1.3.0)
: Restored to the same holder, strong inference (classifier 1.3.1)
: Restored to the same holder, strong inference (classifier 1.3.2)
: Restored to the same holder, strong inference (classifier 1.4.0) current
2025-02-19APNIC− DeregisteredRemoved (return, revocation or reclamation not publicly distinguishable)Strong inference
Statistics
116.206.164.0/22 allocated on 2025-02-19, reserved on 2025-02-20
Inventory
Possible future reissue candidate after hold
Hold estimate
Estimated hold end 2026-02-19. Possible reissue candidate after this date; not confirmed available.
Removed from active registration. The tracker found it by comparing APNIC's daily statistics. APNIC's statistics show it allocated (dated 2017-03-30) on 2025-02-19 and reserved on 2025-02-20. Public sources do not distinguish a voluntary return, revocation, or reclamation. APNIC publishes no hold period, but its statistics have released returned IPv4 space a year after the removal or later since 2014, so the tracker estimates the hold ends on 2026-02-19. That is what APNIC has done, not a rule it states. This does not confirm availability.
Evidence (3) · classifier 1.4.0,
StatisticsFound by comparing APNIC's daily statistics: 116.206.164.0/22 allocated on 2025-02-19, reserved on 2025-02-20source · retrieved
BeforeAPNIC delegated statistics 2025-02-19, before the change: allocated (dated 2017-03-30)source · retrieved
AfterAPNIC delegated statistics 2025-02-20, 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
2017-03-30APNIC+ RegisteredApparent reissuance of previously removed resourceStrong inference
Statistics
116.206.164.0/22 available on 2017-03-30, allocated on 2017-03-31
Inventory
Likely issued from APNIC-controlled inventory
No transfer record matches. APNIC's statistics show it available on 2017-03-30 and allocated (dated 2017-03-30) on 2017-03-31. The tracker saw this range released from hold on 2017-02-01 (116.206.0.0/16), so it appears to have been issued again from APNIC's pool.
Evidence (3) · classifier 1.4.0,
StatisticsFound by comparing APNIC's daily statistics: 116.206.164.0/22 available on 2017-03-30, allocated on 2017-03-31source · retrieved
BeforeAPNIC delegated statistics 2017-03-30, before the change: availablesource · retrieved
AfterAPNIC delegated statistics 2017-03-31, after the change: allocated (dated 2017-03-30)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.