Transferred out of ARIN administration; not offered to ARIN applicants
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.
2020-01-13ARINNot in ARIN-IssuedInter-RIR transfer out of ARINConfirmed
Transferred out of ARIN administration; not offered to ARIN applicants
ARIN's transfer log records a transfer from Yahoo Japan Corporation (ARIN) to IDC Frontier Inc. (APNIC) on 2020-01-13 16:10 UTC: it left ARIN for APNIC. ARIN-Issued didn't list this change; it is not a new allocation and is not offered to ARIN applicants.
Evidence (4) · classifier 1.4.0,
StatisticsNot listed in ARIN-Issued; found by comparing ARIN's daily statistics: 216.255.224.0/20 allocated on 2020-01-13, not listed on 2020-01-14source · retrieved
Transfer logTransfer log: RESOURCE_TRANSFER on 2020-01-13 16:10 UTC, Yahoo Japan Corporation (ARIN) to IDC Frontier Inc. (APNIC); resources moved: 216.255.224.0/20source · retrieved
BeforeARIN delegated statistics 2020-01-12 (produced 2020-01-12T15:00:09+00:00), before the report: allocated (dated 2001-05-01)source · retrieved
AfterARIN delegated statistics 2020-01-14 (produced 2020-01-14T15:00:09+00:00), after the report: not listedsource · retrieved
Classification history for this change (4 versions)
: Inter-RIR transfer out of ARIN, confirmed (classifier 1.3.0)
: Inter-RIR transfer out of ARIN, confirmed (classifier 1.3.1)
: Inter-RIR transfer out of ARIN, confirmed (classifier 1.3.2)
: Inter-RIR transfer out of ARIN, confirmed (classifier 1.4.0) current
2020-01-13APNICTransfer logInter-RIR transfer into APNICConfirmed
Transfer log
Transfer: YAHOO-9 (ARIN) to Japan Network Information Center/IDCFNet (APNIC)
From
YAHOO-9 ARIN
To
Japan Network Information Center/IDCFNet APNIC
Same transfer
Also a change at ARIN, the sending registry: ARIN, 2020-01-13. Lists that cover every registry show it there.
Inventory
Transferred into APNIC administration; not a new issuance
APNIC's transfer log records a transfer from YAHOO-9 (ARIN) to Japan Network Information Center/IDCFNet (APNIC) on 2020-01-13 06:25 UTC: it came to APNIC from ARIN. It was already issued by another registry, so this is not a new issuance.
Evidence (3) · classifier 1.4.0,
Transfer logTransfer log: RESOURCE_TRANSFER on 2020-01-13 06:25 UTC, YAHOO-9 (ARIN) to Japan Network Information Center/IDCFNet (APNIC); resources moved: 64.56.160.0/19, 206.3.0.0/19, 216.255.224.0/20source · retrieved
BeforeAPNIC delegated statistics 2020-01-13, before the change: not listedsource · retrieved
AfterAPNIC delegated statistics 2020-01-14, after the change: allocated (dated 2000-03-21)source · retrieved
Classification history for this change (4 versions)
: Inter-RIR transfer into APNIC, confirmed (classifier 1.3.0)
: Inter-RIR transfer into APNIC, confirmed (classifier 1.3.1)
: Inter-RIR transfer into APNIC, confirmed (classifier 1.3.2)
: Inter-RIR transfer into APNIC, confirmed (classifier 1.4.0) current
Transfer records (2)
Date (UTC)
Log
Type
Range moved
From
To
ARIN
Resource transfer
216.255.224.0/20
Yahoo Japan Corporation ARIN
IDC Frontier Inc. APNIC
APNIC
Resource transfer
216.255.224.0/20
YAHOO-9 ARIN
Japan Network Information Center/IDCFNet 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.