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.
APNIC's transfer log records a transfer from Reliance Jio Infocomm Pte.Ltd (APNIC) to Reliance Jio Infocomm Limited (APNIC) on 2016-11-23 03:12 UTC. The registration changed hands; it is not a new allocation from APNIC.
Evidence (3) · classifier 1.4.0,
Transfer logTransfer log: RESOURCE_TRANSFER on 2016-11-23 03:12 UTC, Reliance Jio Infocomm Pte.Ltd (APNIC) to Reliance Jio Infocomm Limited (APNIC); resources moved: 130.26.0.0/16, 136.232.0.0/15source · retrieved
BeforeAPNIC delegated statistics 2016-11-23, before the change: allocated (dated 1988-04-28)source · retrieved
AfterAPNIC delegated statistics 2016-11-24, after the change: allocated (dated 1988-04-28)source · retrieved
Classification history for this change (4 versions)
Transferred out of RIPE NCC administration; not offered to RIPE NCC applicants
The RIPE NCC's transfer log records a transfer from Hewlett Packard Enterprise Company (RIPE NCC) to an unnamed organization (APNIC) on 2016-11-01 19:00 UTC: it left the RIPE NCC for APNIC. It is not a new allocation and is not offered to RIPE NCC applicants.
Evidence (3) · classifier 1.4.0,
Transfer logTransfer log: RESOURCE_TRANSFER on 2016-11-01 19:00 UTC, Hewlett Packard Enterprise Company (RIPE NCC) to (no name) (APNIC); resources moved: 130.26.0.0/16source · retrieved
BeforeRIPE NCC delegated statistics 2016-10-31 (produced 2016-10-31T22:59:59+00:00), before the change: assigned (dated 1988-04-28)source · retrieved
AfterRIPE NCC delegated statistics 2016-11-01 (produced 2016-11-01T22:59:59+00:00), after the change: not listedsource · retrieved
Classification history for this change (4 versions)
: Inter-RIR transfer out of the RIPE NCC, confirmed (classifier 1.3.0)
: Inter-RIR transfer out of the RIPE NCC, confirmed (classifier 1.3.1)
: Inter-RIR transfer out of the RIPE NCC, confirmed (classifier 1.3.2)
: Inter-RIR transfer out of the RIPE NCC, confirmed (classifier 1.4.0) current
2016-11-01APNICTransfer logInter-RIR transfer into APNICConfirmed
Transfer log
Transfer: HPE (RIPE NCC) to Reliance Jio Infocomm Pte.Ltd (APNIC)
From
HPE RIPE NCC
To
Reliance Jio Infocomm Pte.Ltd APNIC
Same transfer
Also a change at the RIPE NCC, the sending registry: RIPE NCC, 2016-11-01. 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 HPE (RIPE NCC) to Reliance Jio Infocomm Pte.Ltd (APNIC) on 2016-11-01 02:31 UTC: it came to APNIC from the RIPE NCC. 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 2016-11-01 02:31 UTC, HPE (RIPE NCC) to Reliance Jio Infocomm Pte.Ltd (APNIC); resources moved: 130.26.0.0/16source · retrieved
BeforeAPNIC delegated statistics 2016-11-01, before the change: not listedsource · retrieved
AfterAPNIC delegated statistics 2016-11-02, after the change: allocated (dated 1988-04-28)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 (3)
Date (UTC)
Log
Type
Range moved
From
To
APNIC
Resource transfer
130.26.0.0/16
Reliance Jio Infocomm Pte.Ltd APNIC
Reliance Jio Infocomm Limited APNIC
RIPE NCC
Resource transfer
130.26.0.0/16
Hewlett Packard Enterprise Company RIPE NCC
(no name given) APNIC
APNIC
Resource transfer
130.26.0.0/16
HPE RIPE NCC
Reliance Jio Infocomm Pte.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.