rirtracker

IPv4 range · 4,096 addresses

200.24.96.0/20

Now

LACNIC statistics
Allocated (dated 2022-11-16), allocated (dated 2022-12-07), allocated (dated 2023-01-24), allocated (dated 2023-06-27) (BR, VE), in the latest file
Registry
LACNIC
Holder
Not looked up
From
LACNIC's latest statistics

Latest change

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

Reported
2022-04-19 (LACNIC)
Confidence
Strong inference
Inventory
Possible future reissue candidate after hold

Timeline (1)

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.

2022-04-19 LACNIC − Deregistered Removed (return, revocation or reclamation not publicly distinguishable) Strong inference
Statistics
200.24.96.0/20 allocated on 2022-04-18, reserved on 2022-04-19
Inventory
Possible future reissue candidate after hold
Hold estimate
Estimated hold end 2022-10-19. 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 2000-11-22) on 2022-04-18 and reserved on 2022-04-19. 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 2022-10-19. This does not confirm availability.

Evidence (3) · classifier 1.4.0,
  1. Statistics Found by comparing LACNIC's daily statistics: 200.24.96.0/20 allocated on 2022-04-18, reserved on 2022-04-19 source · retrieved
  2. Before LACNIC delegated statistics 2022-04-18, before the change: allocated (dated 2000-11-22) source · retrieved
  3. After LACNIC delegated statistics 2022-04-19, after the change: 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

Changes to overlapping ranges

DateRegistryRangeRecorded asWhat happened
2026-04-17LACNIC200.24.96.0/22Transfer logIntra-LACNIC transfer
2023-06-27LACNIC200.24.104.0/22+ RegisteredApparent reissuance
2023-01-24LACNIC200.24.108.0/22+ RegisteredApparent reissuance
2022-12-07LACNIC200.24.100.0/22+ RegisteredApparent reissuance
2022-11-16LACNIC200.24.96.0/22+ RegisteredApparent reissuance
2022-10-26LACNIC200.24.96.0/22ReleasedHold released
2022-10-19LACNIC200.24.104.0/22ReleasedHold released

Transfer records (1)

Date (UTC)LogTypeRange movedFromTo
LACNICResource transfer200.24.96.0/22 M B Telecom M. H. Beltrami LTDA LACNICL3 NETWORKS E TELECOMUNICACOES LTDA - ME LACNIC

Every record in the ARIN, RIPE NCC, APNIC, LACNIC and AFRINIC transfer logs that moved any part of this IPv4 range (ARIN's from 2009, the RIPE NCC's from 2012, APNIC's from 2010, LACNIC's from 2016, AFRINIC's from 2018). A transfer between two registries is in both logs.

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/200.24.96.0-200.24.111.255.json