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.
Transfer: Netbyte Technologies OU (RIPE NCC) to SONICBYTE TECHNOLOGIES, UNIPESSOAL LDA (RIPE NCC)
From
Netbyte Technologies OU RIPE NCC
To
SONICBYTE TECHNOLOGIES, UNIPESSOAL LDA RIPE NCC
Inventory
No effect on RIPE NCC applicant inventory
The RIPE NCC's transfer log records a transfer from Netbyte Technologies OU (RIPE NCC) to SONICBYTE TECHNOLOGIES, UNIPESSOAL LDA (RIPE NCC) on 2023-12-13 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 2023-12-13 19:00 UTC, Netbyte Technologies OU (RIPE NCC) to SONICBYTE TECHNOLOGIES, UNIPESSOAL LDA (RIPE NCC); resources moved: 2a0b:8400::/29source · retrieved
BeforeRIPE NCC delegated statistics 2023-12-12 (produced 2023-12-12T22:59:59+00:00), before the change: allocated (dated 2016-08-23)source · retrieved
AfterRIPE NCC delegated statistics 2023-12-13 (produced 2023-12-13T22:59:59+00:00), after the change: allocated (dated 2016-08-23)source · retrieved
Classification history for this change (4 versions)
Transfer: Netbyte Technologies B.V (RIPE NCC) to Netbyte Technologies OU (RIPE NCC)
From
Netbyte Technologies B.V RIPE NCC
To
Netbyte Technologies OU RIPE NCC
Inventory
No effect on RIPE NCC applicant inventory
The RIPE NCC's transfer log records a transfer from Netbyte Technologies B.V (RIPE NCC) to Netbyte Technologies OU (RIPE NCC) on 2018-10-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 2018-10-04 19:00 UTC, Netbyte Technologies B.V (RIPE NCC) to Netbyte Technologies OU (RIPE NCC); resources moved: 2a0b:8400::/29source · retrieved
BeforeRIPE NCC delegated statistics 2018-10-03 (produced 2018-10-03T21:59:59+00:00), before the change: allocated (dated 2016-08-23)source · retrieved
AfterRIPE NCC delegated statistics 2018-10-04 (produced 2018-10-04T21:59:59+00:00), after the change: allocated (dated 2016-08-23)source · retrieved
Classification history for this change (4 versions)
: Intra-RIPE NCC transfer, confirmed (classifier 1.4.0) current
2016-08-23RIPE NCC+ RegisteredApparent new issuanceStrong inference
Statistics
2a0b:8400::/29 available on 2016-08-22, allocated on 2016-08-23
Inventory
Likely issued from RIPE NCC-controlled inventory
No transfer record matches. The RIPE NCC's statistics show it available on 2016-08-22 and allocated (dated 2016-08-23) on 2016-08-23. 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: 2a0b:8400::/29 available on 2016-08-22, allocated on 2016-08-23source · retrieved
BeforeRIPE NCC delegated statistics 2016-08-22 (produced 2016-08-22T21:59:59+00:00), before the change: availablesource · retrieved
AfterRIPE NCC delegated statistics 2016-08-23 (produced 2016-08-23T21:59:59+00:00), after the change: allocated (dated 2016-08-23)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
Transfer records (2)
Date (UTC)
Log
Type
Range moved
From
To
RIPE NCC
Resource transfer
2a0b:8400::/29
Netbyte Technologies OU RIPE NCC
SONICBYTE TECHNOLOGIES, UNIPESSOAL LDA RIPE NCC
RIPE NCC
Resource transfer
2a0b:8400::/29
Netbyte Technologies B.V RIPE NCC
Netbyte Technologies OU RIPE NCC
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
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.