rirtracker

IPv4 range · 256 addresses

192.132.102.0/24

Now

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

Latest change

Released Released from hold (APNIC lists it as 'available')

Reported
2024-10-10 (APNIC)
Confidence
Strong inference
Inventory
APNIC's statistics now list it as 'available'; reissue not confirmed

Hold

Removed
2011-02-07 (APNIC)
Estimated hold end
Not estimated: APNIC's observed hold applies to removals from 2014-07-01 on, and this one came earlier
Released from hold
2024-10-10
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.

2024-10-10 APNIC Released Released from hold (APNIC lists it as 'available') Strong inference
Statistics
192.132.102.0/24 reserved on 2024-10-10, available on 2024-10-11
Inventory
APNIC's statistics now list it as 'available'; reissue not confirmed

APNIC's statistics show it reserved on 2024-10-10 and available on 2024-10-11. APNIC moved it from its reserved (held) records to the status it calls 'available'. The tracker saw it removed from registration on 2011-02-07, 4994 days earlier. That is APNIC's own label: whether and when it is reissued is not confirmed.

Evidence (3) · classifier 1.4.0,
  1. Statistics Found by comparing APNIC's daily statistics: 192.132.102.0/24 reserved on 2024-10-10, available on 2024-10-11 source · retrieved
  2. Before APNIC delegated statistics 2024-10-10, before the change: reserved source · retrieved
  3. After APNIC delegated statistics 2024-10-11, after the change: available source · retrieved
Classification history for this change (4 versions)
  1. : Released from hold (APNIC lists it as 'available'), strong inference (classifier 1.3.0)
  2. : Released from hold (APNIC lists it as 'available'), strong inference (classifier 1.3.1)
  3. : Released from hold (APNIC lists it as 'available'), strong inference (classifier 1.3.2)
  4. : Released from hold (APNIC lists it as 'available'), strong inference (classifier 1.4.0) current
2011-02-07 APNIC − Deregistered Removed (return, revocation or reclamation not publicly distinguishable) Observed only
Statistics
192.132.102.0/24 assigned on 2011-02-07, not listed on 2011-02-08
Inventory
Possible future reissue candidate after hold

Removed from active registration. The tracker found it by comparing APNIC's daily statistics. APNIC's statistics show it assigned (dated 1991-11-14) on 2011-02-07 and not listed on 2011-02-08. Being gone from APNIC's statistics entirely can also mean it moved to another registry. Public sources do not distinguish a voluntary return, revocation, or reclamation. APNIC publishes no hold period, and its statistics show a steady one (a year) only for removals from 2014-07-01 on; this one came earlier, so the tracker gives no estimate. This does not confirm availability.

Evidence (3) · classifier 1.4.0,
  1. Statistics Found by comparing APNIC's daily statistics: 192.132.102.0/24 assigned on 2011-02-07, not listed on 2011-02-08 source · retrieved
  2. Before APNIC delegated statistics 2011-02-07, before the change: assigned (dated 1991-11-14) source · retrieved
  3. After APNIC delegated statistics 2011-02-08, after the change: not listed source · retrieved
Classification history for this change (4 versions)
  1. : Removed (return, revocation or reclamation not publicly distinguishable), observed only (classifier 1.3.0)
  2. : Removed (return, revocation or reclamation not publicly distinguishable), observed only (classifier 1.3.1)
  3. : Removed (return, revocation or reclamation not publicly distinguishable), observed only (classifier 1.3.2)
  4. : Removed (return, revocation or reclamation not publicly distinguishable), observed only (classifier 1.4.0) current

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/192.132.102.0-192.132.102.255.json