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.
2025-03-20LACNIC+ RegisteredRestored to the same holderStrong inference
Statistics
192.141.144.0/22 reserved on 2025-03-19, allocated on 2025-03-20
Inventory
No effect on LACNIC applicant inventory
No transfer record matches. LACNIC's statistics show it reserved on 2025-03-19 and allocated (dated 2017-08-29) on 2025-03-20. The tracker saw it removed from registration on 2025-03-11 (9 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 LACNIC's daily statistics: 192.141.144.0/22 reserved on 2025-03-19, allocated on 2025-03-20source · retrieved
BeforeLACNIC delegated statistics 2025-03-19, before the change: reservedsource · retrieved
AfterLACNIC delegated statistics 2025-03-20, after the change: allocated (dated 2017-08-29)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-03-11LACNIC− DeregisteredRemoved (return, revocation or reclamation not publicly distinguishable)Strong inference
Statistics
192.141.144.0/22 allocated on 2025-03-10, reserved on 2025-03-11
Inventory
Possible future reissue candidate after hold
Hold estimate
Estimated hold end 2025-09-11. Possible reissue candidate after this date; not confirmed available.
Removed from active registration. The tracker found it by comparing LACNIC's daily statistics. LACNIC's statistics show it allocated (dated 2017-08-29) on 2025-03-10 and reserved on 2025-03-11. Public sources do not distinguish a voluntary return, revocation, or reclamation. LACNIC holds returned, revoked and reclaimed IPv4 space for 6 calendar months before reissuing it, so the estimated hold end is 2025-09-11. This does not confirm availability.
Evidence (3) · classifier 1.4.0,
StatisticsFound by comparing LACNIC's daily statistics: 192.141.144.0/22 allocated on 2025-03-10, reserved on 2025-03-11source · retrieved
BeforeLACNIC delegated statistics 2025-03-10, before the change: allocated (dated 2017-08-29)source · retrieved
AfterLACNIC delegated statistics 2025-03-11, 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-08-29LACNIC+ RegisteredApparent new issuanceStrong inference
Statistics
192.141.144.0/22 reserved on 2017-08-28, allocated on 2017-08-29
Inventory
Likely issued from LACNIC-controlled inventory
No transfer record matches. LACNIC's statistics show it reserved on 2017-08-28 and allocated (dated 2017-08-29) on 2017-08-29. It moved from LACNIC's unissued pool to an active registration dated around that day, so it appears to be newly issued by LACNIC.
Evidence (3) · classifier 1.4.0,
StatisticsFound by comparing LACNIC's daily statistics: 192.141.144.0/22 reserved on 2017-08-28, allocated on 2017-08-29source · retrieved
BeforeLACNIC delegated statistics 2017-08-28, before the change: reservedsource · retrieved
AfterLACNIC delegated statistics 2017-08-29, after the change: allocated (dated 2017-08-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.