Transferred into APNIC administration; not a new issuance
Timeline (1)
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.
2019-10-03APNICTransfer logInter-RIR transfer into APNICConfirmed
Transfer log
Transfer: SERVI-123 (ARIN) to ServiceNow Software Development India Private Limited (APNIC)
From
SERVI-123 ARIN
To
ServiceNow Software Development India Private Limited APNIC
Same transfer
Also a change at ARIN, the sending registry: ARIN, 2019-10-03. 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 SERVI-123 (ARIN) to ServiceNow Software Development India Private Limited (APNIC) on 2019-10-03 07:45 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 2019-10-03 07:45 UTC, SERVI-123 (ARIN) to ServiceNow Software Development India Private Limited (APNIC); resources moved: 70.34.60.0/23, 70.34.62.0/24source · retrieved
BeforeAPNIC delegated statistics 2019-10-03, before the change: not listedsource · retrieved
AfterAPNIC delegated statistics 2019-10-04, after the change: allocated (dated 2015-03-12)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
ServiceNow Software Development India Private Limited 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.