rirtracker

IPv4 range · 4,096 addresses

202.10.112.0/20

Now

APNIC statistics
Allocated (dated 2015-11-21) (CN), in the latest file
Registry
APNIC
Holder
Not looked up
From
APNIC's latest statistics

Latest change

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

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

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.

2015-10-28 APNIC Released Released from hold (APNIC lists it as 'available') Strong inference
Statistics
202.10.112.0/20 reserved on 2015-10-28, available on 2015-10-29
Inventory
APNIC's statistics now list it as 'available'; reissue not confirmed

APNIC's statistics show it reserved on 2015-10-28 and available on 2015-10-29. APNIC moved it from its reserved (held) records to the status it calls 'available'. The tracker saw it removed from registration on 2012-04-12, 1294 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: 202.10.112.0/20 reserved on 2015-10-28, available on 2015-10-29 source · retrieved
  2. Before APNIC delegated statistics 2015-10-28, before the change: reserved source · retrieved
  3. After APNIC delegated statistics 2015-10-29, 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
2012-04-12 APNIC − Deregistered Removed (return, revocation or reclamation not publicly distinguishable) Strong inference
Statistics
202.10.112.0/20 allocated on 2012-04-12, reserved on 2012-04-13
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 allocated (dated 2003-12-16) on 2012-04-12 and reserved on 2012-04-13. 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: 202.10.112.0/20 allocated on 2012-04-12, reserved on 2012-04-13 source · retrieved
  2. Before APNIC delegated statistics 2012-04-12, before the change: allocated (dated 2003-12-16) source · retrieved
  3. After APNIC delegated statistics 2012-04-13, 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
2015-11-21APNIC202.10.112.0/22+ RegisteredApparent reissuance
2015-11-21APNIC202.10.116.0/22+ RegisteredApparent reissuance
2015-11-21APNIC202.10.120.0/22+ RegisteredApparent reissuance
2015-11-21APNIC202.10.124.0/22+ RegisteredApparent reissuance

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/202.10.112.0-202.10.127.255.json