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.
2017-04-27APNICReleasedReleased from hold (APNIC lists it as 'available')Strong inference
Statistics
202.179.128.0/19 reserved on 2017-04-27, available on 2017-04-28
Inventory
APNIC's statistics now list it as 'available'; reissue not confirmed
APNIC's statistics show it reserved on 2017-04-27 and available on 2017-04-28. APNIC moved it from its reserved (held) records to the status it calls 'available'. The tracker saw it removed from registration on 2010-03-16, 2599 days earlier. That is APNIC's own label: whether and when it is reissued is not confirmed.
Evidence (3) · classifier 1.4.0,
StatisticsFound by comparing APNIC's daily statistics: 202.179.128.0/19 reserved on 2017-04-27, available on 2017-04-28source · retrieved
BeforeAPNIC delegated statistics 2017-04-27, before the change: reservedsource · retrieved
AfterAPNIC delegated statistics 2017-04-28, after the change: availablesource · retrieved
Classification history for this change (4 versions)
: Released from hold (APNIC lists it as 'available'), strong inference (classifier 1.3.0)
: Released from hold (APNIC lists it as 'available'), strong inference (classifier 1.3.1)
: Released from hold (APNIC lists it as 'available'), strong inference (classifier 1.3.2)
: Released from hold (APNIC lists it as 'available'), strong inference (classifier 1.4.0) current
2010-03-16APNIC− DeregisteredRemoved (return, revocation or reclamation not publicly distinguishable)Observed only
Statistics
202.179.128.0/19 allocated on 2010-03-16, not listed on 2010-03-17
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 1999-06-21) on 2010-03-16 and not listed on 2010-03-17. 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,
StatisticsFound by comparing APNIC's daily statistics: 202.179.128.0/19 allocated on 2010-03-16, not listed on 2010-03-17source · retrieved
BeforeAPNIC delegated statistics 2010-03-16, before the change: allocated (dated 1999-06-21)source · retrieved
AfterAPNIC delegated statistics 2010-03-17, after the change: not listedsource · retrieved
Classification history for this change (4 versions)
: Removed (return, revocation or reclamation not publicly distinguishable), observed only (classifier 1.3.0)
: Removed (return, revocation or reclamation not publicly distinguishable), observed only (classifier 1.3.1)
: Removed (return, revocation or reclamation not publicly distinguishable), observed only (classifier 1.3.2)
: Removed (return, revocation or reclamation not publicly distinguishable), observed only (classifier 1.4.0) current
Korea Internet & Security Agency (KISA)/ABCLE APNIC
Korea Internet & Security Agency (KISA)/NHNCLOUD-NET APNIC
APNIC
Resource transfer
202.179.148.0/22
Korea Internet & Security Agency (KISA)/HYOSUNGCDN APNIC
Korea Internet & Security Agency (KISA)/ABCLE APNIC
APNIC
Resource transfer
202.179.140.0/22
Hilton Haulage Limited APNIC
VETTA TRADING LIMITED APNIC
APNIC
Resource transfer
202.179.144.0/22
Strategy Steps Pty Ltd APNIC
Field Solutions Group Pty Ltd APNIC
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.