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.
2026-10-22RIPE NCCTransfer logMerger/acquisition or reorganizationConfirmed
The RIPE NCC's transfer log records a merger, acquisition or reorganization from Regional TeleSystem Ltd (RIPE NCC) to BELRTS Ltd (RIPE NCC) on 2026-10-22 19:00 UTC. The registration changed hands; it is not a new allocation from the RIPE NCC.
Evidence (2) · classifier 1.4.0,
Transfer logTransfer log: MERGER_ACQUISITION on 2026-10-22 19:00 UTC, Regional TeleSystem Ltd (RIPE NCC) to BELRTS Ltd (RIPE NCC); resources moved: 2001:67c:1574::/48source · retrieved
BeforeRIPE NCC delegated statistics 2026-10-21 (produced 2026-10-21T21:59:59+00:00), before the change: assigned (dated 2013-04-08)source · retrieved
2025-07-29RIPE NCCTransfer logMerger/acquisition or reorganizationConfirmed
Transfer log
Merger/acquisition: AO "Sviaz Telecom" (RIPE NCC) to Regional TeleSystem Ltd (RIPE NCC)
From
AO "Sviaz Telecom" RIPE NCC
To
Regional TeleSystem Ltd RIPE NCC
Inventory
No effect on RIPE NCC applicant inventory
The RIPE NCC's transfer log records a merger, acquisition or reorganization from AO "Sviaz Telecom" (RIPE NCC) to Regional TeleSystem Ltd (RIPE NCC) on 2025-07-29 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 2025-07-29 19:00 UTC, AO "Sviaz Telecom" (RIPE NCC) to Regional TeleSystem Ltd (RIPE NCC); resources moved: 2001:67c:1574::/48source · retrieved
BeforeRIPE NCC delegated statistics 2025-07-28 (produced 2025-07-28T21:59:59+00:00), before the change: assigned (dated 2013-04-08)source · retrieved
AfterRIPE NCC delegated statistics 2025-07-29 (produced 2025-07-29T21:59:59+00:00), after the change: assigned (dated 2013-04-08)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
2013-04-08RIPE NCC+ RegisteredApparent new issuanceStrong inference
Statistics
2001:67c:1574::/48 available on 2013-04-07, assigned on 2013-04-08
Inventory
Likely issued from RIPE NCC-controlled inventory
No transfer record matches. The RIPE NCC's statistics show it available on 2013-04-07 and assigned (dated 2013-04-08) on 2013-04-08. It moved from the RIPE NCC's unissued pool to an active registration dated around that day, so it appears to be newly issued by the RIPE NCC.
Evidence (3) · classifier 1.4.0,
StatisticsFound by comparing the RIPE NCC's daily statistics: 2001:67c:1574::/48 available on 2013-04-07, assigned on 2013-04-08source · retrieved
BeforeRIPE NCC delegated statistics 2013-04-07 (produced 2013-04-07T21:59:59+00:00), before the change: availablesource · retrieved
AfterRIPE NCC delegated statistics 2013-04-08 (produced 2013-04-08T21:59:59+00:00), after the change: assigned (dated 2013-04-08)source · retrieved
Classification history for this change (4 versions)
: Apparent new issuance, strong inference (classifier 1.3.0)
: Apparent new issuance, strong inference (classifier 1.3.1)
: Apparent new issuance, strong inference (classifier 1.3.2)
: Apparent new issuance, strong inference (classifier 1.4.0) current
Every record in the ARIN, RIPE NCC, APNIC, LACNIC and AFRINIC transfer logs that moved any part of this IPv6 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
Looked up
Why
Registry
Handle
Organization
Status
Last changed
After 7 days
RIPE NCC
2001:67c:1574::/48
BELRTS-MNT
active
2026-10-22
After 24 hours
RIPE NCC
2001:67c:1574::/48
BELRTS-MNT
active
2026-10-22
First seen
RIPE NCC
2001:67c:1574::/48
BELRTS-MNT
active
2026-10-22
Organization-level details only; contact details are never kept. RDAP shows the registration when it was looked up, not in the past.