rirtracker

IPv4 range · 512 addresses

170.83.56.0/23

Now

LACNIC statistics
Reserved, in the latest file
Registry
LACNIC
Holder
None: it's in the registry's own pool
From
LACNIC's latest statistics

Latest change

− Deregistered Removed (return, revocation or reclamation not publicly distinguishable)

Reported
2026-08-20 (LACNIC)
Confidence
Strong inference
Inventory
Possible future reissue candidate after hold

Hold

Removed
2026-08-20 (LACNIC)
Estimated hold end
2027-02-20 (from LACNIC's published rule)
Now
Possible reissue candidate; not confirmed available.

Timeline (2)

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-08-20 LACNIC − Deregistered Removed (return, revocation or reclamation not publicly distinguishable) Strong inference
Statistics
170.83.56.0/23 assigned on 2026-08-19, reserved on 2026-08-20
Inventory
Possible future reissue candidate after hold
Hold estimate
Estimated hold end 2027-02-20. 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 assigned (dated 2017-01-10) on 2026-08-19 and reserved on 2026-08-20. 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 2027-02-20. This does not confirm availability.

Evidence (3) · classifier 1.4.0,
  1. Statistics Found by comparing LACNIC's daily statistics: 170.83.56.0/23 assigned on 2026-08-19, reserved on 2026-08-20 source · retrieved
  2. Before LACNIC delegated statistics 2026-08-19, before the change: assigned (dated 2017-01-10) source · retrieved
  3. After LACNIC delegated statistics 2026-08-20, after the change: reserved source · retrieved
Classification history for this change (5 versions)
  1. : Removed (return, revocation or reclamation not publicly distinguishable), strong inference (classifier 1.2.0)
  2. : Removed (return, revocation or reclamation not publicly distinguishable), strong inference (classifier 1.3.0)
  3. : Removed (return, revocation or reclamation not publicly distinguishable), strong inference (classifier 1.3.1)
  4. : Removed (return, revocation or reclamation not publicly distinguishable), strong inference (classifier 1.3.2)
  5. : Removed (return, revocation or reclamation not publicly distinguishable), strong inference (classifier 1.4.0) current
2017-01-10 LACNIC + Registered Apparent new issuance Strong inference
Statistics
170.83.56.0/23 reserved on 2017-01-09, assigned on 2017-01-10
Inventory
Likely issued from LACNIC-controlled inventory

No transfer record matches. LACNIC's statistics show it reserved on 2017-01-09 and assigned (dated 2017-01-10) on 2017-01-10. 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,
  1. Statistics Found by comparing LACNIC's daily statistics: 170.83.56.0/23 reserved on 2017-01-09, assigned on 2017-01-10 source · retrieved
  2. Before LACNIC delegated statistics 2017-01-09, before the change: reserved source · retrieved
  3. After LACNIC delegated statistics 2017-01-10, after the change: assigned (dated 2017-01-10) source · retrieved
Classification history for this change (4 versions)
  1. : Apparent reissuance of previously removed resource, strong inference (classifier 1.3.0)
  2. : Apparent reissuance of previously removed resource, strong inference (classifier 1.3.1)
  3. : Apparent reissuance of previously removed resource, strong inference (classifier 1.3.2)
  4. : Apparent new issuance, strong inference (classifier 1.4.0) current

Changes to overlapping ranges

DateRegistryRangeRecorded asWhat happened
2014-04-23LACNIC170.80.0.0/14ReleasedHold released

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/170.83.56.0-170.83.57.255.json