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.
2021-09-10RIPE NCCTransfer logMerger/acquisition or reorganizationConfirmed
The RIPE NCC's transfer log records a merger, acquisition or reorganization from LCR Telecom NV (RIPE NCC) to LCR Telecom BV (RIPE NCC) on 2021-09-10 19:00 UTC. The registration changed hands; it is not a new allocation from the RIPE NCC.
Evidence (3) · classifier 1.4.0,
Transfer logTransfer log: MERGER_ACQUISITION on 2021-09-10 19:00 UTC, LCR Telecom NV (RIPE NCC) to LCR Telecom BV (RIPE NCC); resources moved: 89.41.44.0/22source · retrieved
BeforeRIPE NCC delegated statistics 2021-09-09 (produced 2021-09-09T21:59:00+00:00), before the change: allocated (dated 2005-11-29)source · retrieved
AfterRIPE NCC delegated statistics 2021-09-10 (produced 2021-09-10T21:59:00+00:00), after the change: allocated (dated 2005-11-29)source · retrieved
Classification history for this change (4 versions)
: Merger/acquisition or reorganization, confirmed (classifier 1.3.0)
: Merger/acquisition or reorganization, confirmed (classifier 1.3.1)
: Merger/acquisition or reorganization, confirmed (classifier 1.3.2)
: Merger/acquisition or reorganization, confirmed (classifier 1.4.0) current
Transfer: XT GLOBAL NETWORKS LTD. (RIPE NCC) to LCR Telecom NV (RIPE NCC)
From
XT GLOBAL NETWORKS LTD. RIPE NCC
To
LCR Telecom NV RIPE NCC
Inventory
No effect on RIPE NCC applicant inventory
The RIPE NCC's transfer log records a transfer from XT GLOBAL NETWORKS LTD. (RIPE NCC) to LCR Telecom NV (RIPE NCC) on 2017-05-04 19:00 UTC. The registration changed hands; it is not a new allocation from the RIPE NCC.
Evidence (3) · classifier 1.4.0,
Transfer logTransfer log: RESOURCE_TRANSFER on 2017-05-04 19:00 UTC, XT GLOBAL NETWORKS LTD. (RIPE NCC) to LCR Telecom NV (RIPE NCC); resources moved: 89.41.44.0/22source · retrieved
BeforeRIPE NCC delegated statistics 2017-05-03 (produced 2017-05-03T21:59:59+00:00), before the change: allocated (dated 2005-11-29)source · retrieved
AfterRIPE NCC delegated statistics 2017-05-04 (produced 2017-05-04T21:59:59+00:00), after the change: allocated (dated 2005-11-29)source · retrieved
Classification history for this change (4 versions)
Transfer: Jump Management SRL (RIPE NCC) to XT GLOBAL NETWORKS LTD. (RIPE NCC)
From
Jump Management SRL RIPE NCC
To
XT GLOBAL NETWORKS LTD. RIPE NCC
Piece of
89.32.0.0/12: the rest of the block stayed with the seller
Inventory
No effect on RIPE NCC applicant inventory
The RIPE NCC's transfer log records a transfer from Jump Management SRL (RIPE NCC) to XT GLOBAL NETWORKS LTD. (RIPE NCC) on 2015-03-17 19:00 UTC. The registration changed hands; it is not a new allocation from the RIPE NCC.
Evidence (3) · classifier 1.4.0,
Transfer logTransfer log: RESOURCE_TRANSFER on 2015-03-17 19:00 UTC, Jump Management SRL (RIPE NCC) to XT GLOBAL NETWORKS LTD. (RIPE NCC); resources moved: 89.41.44.0/22source · retrieved
BeforeRIPE NCC delegated statistics 2015-03-16 (produced 2015-03-16T22:59:59+00:00), before the change: allocated (dated 2005-11-29)source · retrieved
AfterRIPE NCC delegated statistics 2015-03-17 (produced 2015-03-17T22:59:59+00:00), after the change: allocated (dated 2005-11-29)source · retrieved
Classification history for this change (4 versions)
: Intra-RIPE NCC transfer, confirmed (classifier 1.4.0) current
Transfer records (3)
Date (UTC)
Log
Type
Range moved
From
To
RIPE NCC
Merger acquisition
89.41.44.0/22
LCR Telecom NV RIPE NCC
LCR Telecom BV RIPE NCC
RIPE NCC
Resource transfer
89.41.44.0/22
XT GLOBAL NETWORKS LTD. RIPE NCC
LCR Telecom NV RIPE NCC
RIPE NCC
Resource transfer
89.41.44.0/22
Jump Management SRL RIPE NCC
XT GLOBAL NETWORKS LTD. RIPE NCC
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.