rirtracker

IPv4 range · 2 prefixes · 12,288 addresses

24.143.128.0 - 24.143.175.255

24.143.128.0/19, 24.143.160.0/20

Now

ARIN statistics
Allocated (dated 2014-12-17), allocated (dated 2015-01-12) (CA), in the latest file
Registry
ARIN
Holder
Not looked up
From
ARIN's latest statistics

Latest change

− Remove Unresolved change

Reported
2010-06-11 (ARIN)
Confidence
Observed only
Inventory
Inventory effect unknown

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.

2010-06-11 ARIN − Remove Unresolved change Observed only
ARIN-Issued
Remove 24.143.128.0-24.143.175.255
Inventory
Inventory effect unknown

ARIN-Issued says "Remove", but ARIN's statistics show it not issued on 2010-06-10 and not issued on 2010-06-12. (Until 2013-03-05, ARIN's statistics list only what's issued.) The registry's pool records from that time aren't public, so the tracker can't tell what was removed.

Evidence (3) · classifier 1.4.0,
  1. ARIN-Issued ARIN-Issued report for 2010-06-11: "Remove 24.143.128.0-24.143.175.255" source · retrieved
  2. Before ARIN delegated statistics 2010-06-10, before the report: not issued source · retrieved
  3. After ARIN delegated statistics 2010-06-12, after the report: not issued source · retrieved
Classification history for this change (4 versions)
  1. : Unresolved change, observed only (classifier 1.3.0)
  2. : Unresolved change, observed only (classifier 1.3.1)
  3. : Unresolved change, observed only (classifier 1.3.2)
  4. : Unresolved change, observed only (classifier 1.4.0) current
2009-06-10 ARIN Not in ARIN-Issued Removed (return, revocation or reclamation not publicly distinguishable) Strong inference
Inventory
Possible future reissue candidate after hold
Hold estimate
Estimated hold end 2009-08-09. Possible reissue candidate after this date; not confirmed available.

Removed from active registration. ARIN-Issued didn't list this; the tracker found it by comparing ARIN's daily statistics. ARIN's statistics show it allocated (dated 2003-10-06) on 2009-06-09 and not issued on 2009-06-11. (Until 2013-03-05, ARIN's statistics list only what's issued.) Public sources do not distinguish a voluntary return, revocation, or reclamation. ARIN holds returned, revoked and reclaimed IPv4 space for 60 days before reissuing it, so the estimated hold end is 2009-08-09. This does not confirm availability.

Evidence (3) · classifier 1.4.0,
  1. Statistics Not listed in ARIN-Issued; found by comparing ARIN's daily statistics: 24.143.128.0 - 24.143.175.255 allocated on 2009-06-10, not listed on 2009-06-11 source · retrieved
  2. Before ARIN delegated statistics 2009-06-09, before the report: allocated (dated 2003-10-06) source · retrieved
  3. After ARIN delegated statistics 2009-06-11, after the report: not issued 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
2023-04-18ARIN24.143.160.0/19Transfer logMerger/acquisition
2015-01-12ARIN24.143.160.0/19+ AddApparent reissuance
2014-12-17ARIN24.143.128.0/19+ AddApparent reissuance

Transfer records (1)

Date (UTC)LogTypeRange movedFromTo
ARINMerger acquisition24.143.160.0/19 COGECO COMMUNICATIONS INC. ARINCogeco Connexion Inc. ARIN

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/24.143.128.0-24.143.175.255.json