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.
2015-02-19ARINTransfer logInter-RIR transfer out of ARINConfirmed
Transfer log
Transfer: HCL AMERICA INC (ARIN) to (no name) (APNIC)
192.8.0.0/16: the rest of the block stayed with the seller
Inventory
Transferred out of ARIN administration; not offered to ARIN applicants
ARIN's transfer log records a transfer from HCL AMERICA INC (ARIN) to an unnamed organization (APNIC) on 2015-02-19 22:34 UTC: it left ARIN for APNIC. It is not a new allocation and is not offered to ARIN applicants.
Evidence (3) · classifier 1.4.0,
Transfer logTransfer log: RESOURCE_TRANSFER on 2015-02-19 22:34 UTC, HCL AMERICA INC (ARIN) to (no name) (APNIC); resources moved: 192.8.180.0/24source · retrieved
BeforeARIN delegated statistics 2015-02-18 (produced 2015-02-18T06:05:27+00:00), before the report: assigned (dated 1990-03-26)source · retrieved
AfterARIN delegated statistics 2015-02-20 (produced 2015-02-20T06:05:08+00:00), after the report: not listedsource · retrieved
2015-02-16APNICTransfer logInter-RIR transfer into APNICConfirmed
Transfer log
Transfer: HA (ARIN) to HCL Technologies Ltd (APNIC)
From
HA ARIN
To
HCL Technologies Ltd APNIC
Same transfer
Also a change at ARIN, the sending registry: ARIN, 2015-02-19. 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 HA (ARIN) to HCL Technologies Ltd (APNIC) on 2015-02-16 05:47 UTC: it came to APNIC from ARIN. It was already issued by another registry, so this is not a new issuance.
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.