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.
2018-05-01APNIC− DeregisteredRemoved (return, revocation or reclamation not publicly distinguishable)Strong inference
Statistics
AS10122-AS10123 allocated on 2018-05-01, available on 2018-05-02
Inventory
Possible future reissue candidate after hold
Hold estimate
Estimated hold end 2019-05-01. Possible reissue candidate after this date; not confirmed available.
Removed from active registration. The tracker found it by comparing APNIC's daily statistics. APNIC's statistics show it allocated (dated 2006-09-07) on 2018-05-01 and available on 2018-05-02. Public sources do not distinguish a voluntary return, revocation, or reclamation. APNIC publishes no hold period, but its statistics have released returned ASNs a year after the removal or later since 2014, so the tracker estimates the hold ends on 2019-05-01. That is what APNIC has done, not a rule it states. This does not confirm availability.
Evidence (3) · classifier 1.4.0,
StatisticsFound by comparing APNIC's daily statistics: AS10122-AS10123 allocated on 2018-05-01, available on 2018-05-02source · retrieved
BeforeAPNIC delegated statistics 2018-05-01, before the change: allocated (dated 2006-09-07)source · retrieved
AfterAPNIC delegated statistics 2018-05-02, after the change: availablesource · retrieved
Classification history for this change (4 versions)
: Removed (return, revocation or reclamation not publicly distinguishable), strong inference (classifier 1.3.0)
: Removed (return, revocation or reclamation not publicly distinguishable), strong inference (classifier 1.3.1)
: Removed (return, revocation or reclamation not publicly distinguishable), strong inference (classifier 1.3.2)
: Removed (return, revocation or reclamation not publicly distinguishable), strong inference (classifier 1.4.0) current
No transfer log has a transfer of any part of this ASN.
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.